Last updated 2006-01-11

XmlBlaster Programmers Reference Overview


Requirement - ID Status Info Topic
admin CLOSED >> Remote administration of xmlBlaster
admin.checkpoint CLOSED >> Trace the message flow at pre-defined checkpoints
admin.commands CLOSED >> Description of the available commands for remote administration of xmlBlaster
admin.deploy CLOSED >> You can automatically generate an xmlBlaster server distribution for easy deployment
admin.errorcodes CLOSED >> XmlBlaster supports well defined error codes
admin.errorcodes.listing CLOSED >> XmlBlaster error code reference
admin.errorHandling CLOSED >> XmlBlaster supports specific error handling and dead messages
admin.events CLOSED >> A event plugin which catches for example logging errors and dispatches them to a given email address or another sink.
admin.http CLOSED >> XmlBlaster provides a HTML/HTTP plugin interface for your own HTML monitoring pages
admin.jmx CLOSED >> XmlBlaster provides an JMX-Interface for monitoring and controlling
admin.logging CLOSED >> XmlBlaster uses the JDK 1.4 logging framework
admin.messages CLOSED >> You can administer XmlBlaster sending messages
admin.momClient OPEN >> You can administer XmlBlaster clients by sending PtP messages
admin.snmp INWORK >> You can administer XmlBlaster using an snmp MIB with xmlBlasters SNMP subagent
admin.start.asService CLOSED >> Setting up xmlBlaster to start as a service
admin.startupTasks CLOSED >> On xmlBlaster startup you can execute a script for administrative tasks
admin.telnet CLOSED >> You can administer XmlBlaster using a telnet client
admin.testament OPEN >> XmlBlaster supports client testaments
client.activex DEPRECATED >> XmlBlaster provides access from C# and VisualBasic with ActiveX.
client.browser CLOSED >> XmlBlaster provides a framework to callback browsers (push mode) using a never closing HTTP connection.
client.c.queue CLOSED >> XmlBlaster provides a persistent queue implementation for ANSI C
client.c.socket CLOSED >> XmlBlaster provides a client library written in ANSI C
client.c.windowsCE CLOSED >> Windows CE based xmlBlaster clients (C, C++, C#).
client.cache CLOSED >> Allows Java clients to poll synchronously for messages with the getCached() method, and access the up to date message high performing from a local cache.
client.callback.authenticate CLOSED >> The callback server, instantiated from clients, needs to authenticate xmlBlaster
client.configuration CLOSED >> Description of the available client side configuration
client.cpp CLOSED >> XmlBlaster provides a complete client library written in c++.
client.cpp.compile CLOSED >> In order to build and run c++ clients, several preconditions need to be fulfilled.
client.cpp.failsafe CLOSED >> The c++ client library supports failsafe reconnect where published messages are queued as long as the communication to xmlBlaster is broken.
client.cpp.logging CLOSED >> C++ client logging configuration
client.cpp.mico CLOSED >> C++ clients can access xmlBlaster with the MICO Corba library
client.cpp.omniorb CLOSED >> C++ clients can access xmlBlaster with the omniORB Corba library
client.cpp.orbix CLOSED >> C++ clients can access xmlBlaster with the ORBIX Corba library
client.cpp.protocol CLOSED >> The cpp client library handles the communication to xmlBlaster transparently.
client.cpp.queue CLOSED >> XmlBlaster provides a persistent queue implementation for C++ clients
client.cpp.socket CLOSED >> C++ clients can access xmlBlaster with the native SOCKET protocol
client.cpp.tao CLOSED >> C++ client can access xmlBlaster with the TAO Corba library
client.csharp CLOSED >> XmlBlaster provides full access from C#.
client.failsafe CLOSED >> I_XmlBlasterAccess is the Java client side interface to xmlBlaster which supports polling for xmlBlaster and record/playback of messages during lost connections.
client.failsafe.ping CLOSED >> Allows Java clients to ping xmlBlaster, to test reliable the connection.
client.filepoller DEPRECATED >> You can publish messages by putting files on a certain location in the file system.
client.flash CLOSED >> XmlBlaster provides access from Flash (Macromedia Flash Player).
client.j2me CLOSED >> XmlBlaster provides a tiny java client library for j2me MIDlets
client.java.applet CLOSED >> XmlBlaster provides a tiny java client library for applets
client.javascript.rhino CLOSED >> XmlBlaster can be easly implemented in javascript code making use of the LiveConnect feature of the Rhino javascript interpreter (embedding of java code into javascript). The advantage of using this technology is that you can use which protocol you whish to communicate with xmlBlaster.
client.perl CLOSED >> XmlBlaster provides a simple client library written in Perl using XmlRpc.
client.php CLOSED >> XmlBlaster provides access from PHP.
client.python CLOSED >> XmlBlaster provides a client library written in Python.
client.python.corba CLOSED >> XmlBlaster provides a client library written in Python using Corba.
client.python.xmlrpc CLOSED >> XmlBlaster provides a client library written in Python using XmlRpc.
client.script CLOSED >> Invocations to the xmlBlaster server can be done with an xml script.
client.subscribe.dispatch CLOSED >> I_XmlBlasterAccess is the Java client side interface to xmlBlaster which supports a subscribe variant, allowing to dispatch callback messages to dedicated update methods.
cluster CLOSED >> Multiple xmlBlaster instances can build a cluster following the master/slave paradigm
cluster.dirtyRead CLOSED >> A cluster slave node can directly cache published messages
cluster.PtP CLOSED >> Point to point (PtP) routing of messages in a cluster environment
contrib.dbwatcher CLOSED >> DbWatcher polls a database for changes and publishes those to xmlBlaster.
contrib.dbwriter CLOSED >> DbWriter writes to a Database entries received as XmlBlaster Messages. It is the ideal sink for its counterpart DbWatcher.
contrib.filewatcher CLOSED >> You can publish messages by putting files on a certain location in the file system.
contrib.filewriter CLOSED >> You can receive messages published by the filewatcher and store them at a certain location on the filesystem.
contrib.replication CLOSED >> Replication is a plugin framework used to replicate data between database (RDBMS) sources and sinks.
contrib.scheduler CLOSED >> You can receive messages published by the filewatcher and store them at a certain location on the filesystem.
dispatch.control.plugin CLOSED >> XmlBlaster has a plugin interface which allows to control the message dispatch
dispatch.plugin.priorizedDispatch CLOSED >> XmlBlaster provides a plugin to control message delivery to remote destinations
eclipse CLOSED >> Develop/debug xmlBlaster core with eclipse
engine.callback CLOSED >> XmlBlaster has a sophisticated client callback framework
engine.get.no CLOSED >> Accessing an unknown message in xmlBlaster with the synchronous get() method throws an Exception
engine.LoginLogoutEvent DEPRECATED >> Clients can be notified about other clients login or logout events. Deprecated: Please use events as described in requirement admin.events
engine.message CLOSED >> XmlBlaster uses a well defined message format
engine.message.lifecycle CLOSED >> State charts and configuration of message and topic lifecycles
engine.persistence CLOSED >> XmlBlaster provides a plugin possibility for its persistence layer
engine.persistence.FileDriver DEPRECATED >> XmlBlaster provides a simple file based persistence layer to store messages marked with <persistent/>
engine.persistence.session CLOSED >> XmlBlaster supports sessions and subscriptions which persist a server crash.
engine.persistence.subscription CLOSED >> XmlBlaster supports sessions and subscriptions which persist a server crash.
engine.persistence.xmldb DEPRECATED >> XmlBlaster provides a XML:DB-API based persistence layer to store messages marked with <persistent/>
engine.persistence.xmldb.xindice DEPRECATED >> XmlBlaster provides proxy for the native xmldb Xindice.
engine.qos.clientProperty CLOSED >> A generic qos subtag permitting to pass client specific parameters to other clients or to plugins
engine.qos.login.callback CLOSED >> Clients of XmlBlaster can specify their desired callbacks during login
engine.qos.login.session CLOSED >> Clients of XmlBlaster can use configurable session parameters on login
engine.qos.publish.destination.ForceQueuing CLOSED >> Published messages in PtP mode can be queued by xmlBlaster if the receiver is not logged in
engine.qos.publish.destination.offline CLOSED >> If the receiver of a PtP message is offline or has no callback the behavior is configurable
engine.qos.publish.destination.PtP CLOSED >> PtP (Point to Point) messages are routed using the qos-destination tag
engine.qos.publish.destination.PtX OPEN >> PtX (Point to XPath) messages are routed using the qos-destination tag
engine.qos.publish.forceUpdate CLOSED >> XmlBlaster can suppress to route identical messages in Publish/Subcribe mode
engine.qos.publish.isVolatile CLOSED >> XmlBlaster allows to mark messages as volatile
engine.qos.publish.persistent CLOSED >> XmlBlaster allows store messages in a persistent store
engine.qos.publish.priority CLOSED >> XmlBlaster supports message priorities
engine.qos.publish.PubSub CLOSED >> Published messages without a qos <destination> tag are published in Publish/Subscribe mode
engine.qos.publish.readonly CLOSED >> XmlBlaster allows to qualify messages as read only
engine.qos.queryspec CLOSED >> XmlBlaster has a plugin interface to generically specify a query
engine.qos.queryspec.QueueQuery CLOSED >> XmlBlaster has a plugin which is used to query message entries on arbitrary queues
engine.qos.subscribe.duplicate CLOSED >> On connection a client can specify to not receive duplicate messages even when he has subscribed multiple times.
engine.qos.subscribe.id CLOSED >> On subscribe you can force your own subscription id.
engine.qos.subscribe.initialUpdate CLOSED >> On subscribe you can prevent the initial message update for existing messages.
engine.qos.subscribe.multiSubscribe CLOSED >> On multiple subscription on the same topic a client can specify to receive this message only once.
engine.qos.update.queue CLOSED >> XmlBlaster delivers some queue informations of a message in the qos argument
engine.qos.update.rcvTimestamp CLOSED >> XmlBlaster sends the creation date of a message in the qos arguments of an update
engine.qos.update.sender CLOSED >> XmlBlaster delivers the sender name of a message in the qos argument
engine.qos.update.state CLOSED >> XmlBlaster sends the state of a message in the qos argument of an update
engine.qos.update.subscriptionId CLOSED >> XmlBlaster sends the subscription id in the qos arguments of an update
engine.queue CLOSED >> XmlBlaster has a sophisticated message queueing engine
engine.runlevel CLOSED >> XmlBlaster supports different run levels
engine.runlevel.howto CLOSED >> How to write a native client plugin for xmlBlaster
engine.service.rdbms CLOSED >> XmlBlaster provides a framework to send SQL statements to arbitrary databases simultaneously and receive query results xml encoded (JDK 1.5 or higher only)
engine.service.rdbms.jdbcpool CLOSED >> XmlBlaster provides a 'named' JDBC connection pool for optimized performance of database access.
engine.transaction OPEN >> XmlBlaster supports transactions built on the CORBA OTS/JTS service
interface CLOSED >> XmlBlaster supports a small number of generic methods for remote access
interface.connect CLOSED >> Connecting to xmlBlaster
interface.disconnect CLOSED >> Disconnecting from xmlBlaster
interface.erase CLOSED >> Messages are deleted with the erase() method
interface.get CLOSED >> Synchronous message access with the get() method
interface.publish CLOSED >> All messages sent to xmlBlaster use the publish method
interface.subscribe CLOSED >> Messages are asynchronous accessed with the subscribe() method
interface.unSubscribe CLOSED >> Message subscriptions are canceled with the unSubscribe() method
interface.update CLOSED >> Clients receive asynchronous messages with the update() method
j2ee.jmx CLOSED >> JMX MBean version of XmlBlaster server.
j2ee.k2 CLOSED >> Java Connector Architecture compaible resource adapter.
jms INWORK >> xmlBlaster provides an implementation of the JMS API.
mime.plugin.access.regex CLOSED >> XmlBlaster allows to access messages filtered with regular expressions
mime.plugin.access.sql92 CLOSED >> XmlBlaster allows to access messages filtered with statements conform to the search conditions of defined in sql92.
mime.plugin.access.xpath CLOSED >> XmlBlaster allows to access message instances filtered with XPath expressions
mime.plugin.accessfilter CLOSED >> XmlBlaster has a MIME based plugin interface to filter message access
mime.plugin.accessfilter.howto CLOSED >> XmlBlaster supports to plugin your own access message filters
mime.plugin.publishfilter CLOSED >> XmlBlaster has a MIME based plugin interface to filter, check or manipulate published messages
mime.plugin.publishfilter.howto CLOSED >> XmlBlaster supports to plugin your own publish message filters
mom.publishsubscribe CLOSED >> XmlBlaster supports the publish/subscribe paradigm
msgDistributor.plugin CLOSED >> XmlBlaster has a plugin interface which allows to control the distribution of published messages to subscribers
msgDistributor.plugin.ConsumableQueue CLOSED >> XmlBlaster has a plugin which tells a topic to behave like a queue, i.e. that every message update is delivered and consumed only once.
protocol CLOSED >> XmlBlaster provides a framework to plugin drivers for new protocols to access xmlBlaster, and for drivers to callback to clients.
protocol.corba.JacORB CLOSED >> xmlBlaster supports a CORBA protocol plugin based on JacORB
protocol.corba.NameService CLOSED >> Multiple xmlBlaster server instances can register themselves in a CORBA NameService
protocol.corba.orbacus CLOSED >> The XmlBlaster server can be compiled and run with ORBacus. The same is true for java- and c++ clients.
protocol.email CLOSED >> XmlBlaster has a protocol plugin to support access via email
protocol.jms OPEN >> XmlBlaster supports JMS (Java message service) inter operability.
protocol.local CLOSED >> XmlBlaster supports native client server communication in the same JVM
protocol.rmi CLOSED >> xmlBlaster supports a RMI protocol plugin
protocol.soap INWORK >> XmlBlaster has a protocol plugin to support access via SOAP
protocol.socket CLOSED >> XmlBlaster supports a bidirectional native communication protocol using exactly one socket connection
protocol.stomp CLOSED >> XmlBlaster supports the bidirectional STOMP communication protocol
protocol.xmlrpc CLOSED >> XmlBlaster supports XmlRpc
queue CLOSED >> Within XmlBlaster there is a complete queue framework offering generic plugin based storage. The queues can be persistent or transient.
queue.cache CLOSED >> XmlBlaster provides a generic cache plugin for storing queue entries on a database and at the same offer caching facility for better performance.
queue.jdbc CLOSED >> Describes xmlBlaster persistence layer since v2.0 (2008-11-20).
queue.jdbc.commontable DEPRECATED >> JDBC Plugin which stores all queues on a common table.
queue.jdbc.db2 INWORK >> XmlBlaster queuing facility with DB2 backend store.
queue.jdbc.firebird CLOSED >> XmlBlaster has an advanced queuing facility. Among others one tested persistence layer is offered by communicating with a Firebird database.
queue.jdbc.hsqldb CLOSED >> XmlBlaster has an advanced queuing facility. As the default persistence layer HSQLDB is used as an embedded java database.
queue.jdbc.ldbc INWORK >> The common table plugin supports using the Liberty Database Connectivity Abstraction Layer.
queue.jdbc.mysql INWORK >> XmlBlaster has an advanced queuing facility. Among others, one tested persistence layer is offered by communicating with a MySQL database.
queue.jdbc.oracle CLOSED >> XmlBlaster has an advanced queuing facility. Among others one tested persistence layer is offered by communicating with an oracle database.
queue.jdbc.postgres CLOSED >> XmlBlaster has an advanced queuing facility. Among others one tested persistence layer is offered by communicating with a postgres database.
queue.jdbc.sqlserver CLOSED >> XmlBlaster has an advanced queuing facility. Among others one tested persistence layer is offered by communicating with Microsoft SQL Server 2000 and 2005 database.
queue.ram CLOSED >> XmlBlaster provides a plugin for a memory based queue called RamQueuePlugin which implements the I_Queue and I_Plugin interface.
security.development.serverPlugin.howto CLOSED >> HOWTO: Development of a Server Side Security Plugin
security.htpasswd CLOSED >> XmlBlaster provides a crypt password based authentication plugin
security.introduction CLOSED >> HOWTO: xmlBlaster Security Introduction
security.ldap CLOSED >> XmlBlaster provides a LDAP based authentication plugin
util.classloader.ClassLoaderFactory CLOSED >> XmlBlaster provides a pluggable ClassLoaderFactory to create instances of xmlBlaster specific classloaders.
util.classloader.PluginClassLoader CLOSED >> XmlBlaster provides an own classloader for its plugins.
util.classloader.XmlBlasterClassLoader CLOSED >> XmlBlaster provides an own ClassLoder.
util.property CLOSED >> XmlBlaster provides a property file to allow a simple configuration
util.property.env INWORK >> The xmlBlaster.properties file and command line configuration
util.recorder.returnvalues DEPRECATED >> The InvocationRecorder should allow to record the return values of method invocations as well. Not supported!

This page is generated from the requirement XML files in the xmlBlaster/doc/requirements directory of the distribution