Hi
glassfish_at_javadesktop.org wrote:
> The JBoss messaging queues have all these features like DLQ, Expiry Queue, Re-delivery,Clustering etc. Can you please elaborate?
The Connector architecture is the standard message-provider pluggability
mechanism in Java EE. [1].
JBoss Messaging (the MoM product) may provide a JMS library to connect
to their product. Standalone Java clients could also portably use the
JMS APIs, with the aid of the JMS library provided by JBoss Messaging,
to communicate with the message provider.
However, there is additional work to integrate a MoM product with an
application server and application components managed by that
application server (think transactions, security, connection management,
inbound message delivery etc).
Before Connectors 1.5, each J2EE application server had to provide
custom machinery to integrate with different MoM products. This resulted
in an m x n style integration problem with each AS vendor developing
custom integration solutions for every MoM product and vice-versa.
The Connectors 1.5 specification, through the outbound and the Message
Inflow system contracts, defined a standard message-provider
pluggability contract and enables a Java EE application server to
integrate with any MoM product through a resource adapter. You may
now use a resource-adapter provided by the MoM product vendor (like
JBoss Messaging) or use a generic resource adapter (such as Generic RA
for JMS) to integrate a MoM product with a J2EE appserver. Hope this
helps.
Thanks
--Siva.
[1]
http://java.sun.com/j2ee/connector/overview.html#4
>
> Thanks :)
> [Message sent by forum member 'rubycube' (rubycube)]
>
> http://forums.java.net/jive/thread.jspa?messageID=353864
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>