Why is it not 100% JMS (Java Message Service) based?
• JMS is not CORBA based. Trying to access JMS from Perl, Tcl, C/C++ or any other CORBA aware language will give you some major headache. But the world is and will ever be heterogeneous, so there is no place for narrow minded Java centric approaches. • JMS is not XML based. XML allows professional modeling of every day problems with free modification at runtime. So basing a middleware on the XML descriptive possibilities and allowing the query with a XML query language is a major advantage over key-value based approaches. • JMS API is split. xmlBlaster has only very few communication methods to allow the whole spectrum of MOM (Message orientated middleware) communication paradigms. Extending the xmlBlaster CORBA API once it is published as release 1.0 is very unlike. Adding new MOM features in future releases of xmlBlaster is mainly adding backward compatible XML tags. • JMS has a mixed HEADER section. Some header fields in JMS address the message content and some other the message rou
