REQUIREMENT engine.persistence |
Type | NEW |
Priority | MEDIUM |
Status | CLOSED |
Topic | XmlBlaster provides a plugin possibility for its persistence layer |
Des cription |
To store messages from xmlBlaster and to restore them again after a new startup of the server or after a server crash there is are two interfaces, called I_Map and I_Queue, available.
Currently we provide plugins to store messages to Postgres or Oracle. Writing an own persistence layer is straight forward:
We provide a cache implementation for I_Map and for I_Queue which can usually directly use your new persistence plugin. The current cache plugin stores persistent messages and swaps transient messages if you want to handle huge message amounts in xmlBlaster which don't fit to RAM anymore. |
Configure |
NOTE: Configuration parameters are specified on command line (-someValue 17) or in the
xmlBlaster.properties file (someValue=17). See requirement "util.property" for details. |
See API | org.xmlBlaster.util.plugin.I_Plugin |
See API | org.xmlBlaster.engine.msgstore.I_Map |
See API | org.xmlBlaster.engine.msgstore.cache.PersistenceCachePlugin |
See API | org.xmlBlaster.util.queue.I_Queue |
See API | org.xmlBlaster.util.queue.jdbc.JdbcQueuePlugin |
See API | org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin |
See REQ | queue.jdbc.commontable |
See TEST | org.xmlBlaster.test.classtest.queue.I_QueueTest |
See TEST | org.xmlBlaster.test.classtest.msgstore.I_MapTest |
This page is generated from the requirement XML file xmlBlaster/doc/requirements/engine.persistence.xml