dnet-notification-service (0.9.3) unstable; urgency=low * r14424: Fixed bug in notification result filtering * r14421: Fixed bugs in notification result filtering and typos -- Antonis Lempesis Fri, 07 Jun 2012 20:16:19 +0200 dnet-notification-service (0.9.2) unstable; urgency=low * r14031: - fixed mock notification dao - removed executeQuery.jsp * r13981: - Fixed appearance issues and typos in JSPs * r13901: Reimplemented notification and alert service to improve their temporal performance: - internal communication is no longer based on atom but on JAXWS - paging is available for any collection of objects, both internally and externally - instead of an atom broker as hub each notification service can now contact multiple alert services and vice versa - instead of plain JDBC, now Apache DBCP and spring transactions are used for persistance - alert formatting is not any more XSLT-based, it uses just plain text - notification events are not transported as a whole, alert service fetches only the results for which it has subscriptions - alert pull topics are no more supported - primary and secondary queries are stored seperately and secondary queries are only executed upon demand -- Antonis Lempesis Wed, 02 May 2012 15:16:19 +0200 dnet-notification-service (0.9.1) unstable; urgency=low * r13548: Added a name and a description to alert topics and set default character encoding and storage engine in CREATE statements of DAOs -- Antonis Lempesis Thu, 01 Feb 2012 14:16:19 +0200 dnet-notification-service (0.9) unstable; urgency=low * initial packaging -- Antonis Lempesis Thu, 01 Dec 2011 19:16:19 +0200