Eric,
JMS is the standard API for accessing messaging systems via Java. Just
like JNDI is the standard way to access name and directory systems via
Java. Whether your particular system is IBM MQ Series, TIBCO Rendezvous,
some implementation of the CORBA Notification Service, etc, if you are
accessing it from Java you should use JMS.
JMS is designed to work smoothly with the non-Java clients of a JMS
provider. For instance, creating a new JMS client that exchanges
messages with an existing C client on an IBM MQ system is very
practical.
Some messaging vendors supportg JMS today. Most will be supporting it
within the next 9 to 12 months.
-- Mark
Eric Hughes wrote:
>
> We've given some thought (haven't built much) to this.
> Either the Event Service or the Asynchronous Messaging from
> CORBA seem more appealing if there's a possibility of clients
> that aren't Java.
> We've also used some research-ware to manage subscriptions,
> profiles and the like; see http://www.cda.mews.org/ or
> drop me a line if you're interested.
>
> Eric Hughes
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
