PhoenixJMS may end up being absorbed into OpenJMS. If that happens, I'll try to move PhoenixMDS to here, which would give us the jms container facility.
+1
That is exactly how I see the JMS facility in merlin panning out. The PhoenixJMS component is really just a wrapper component to start an instance of a JMS server. But the MDS stuff is the real kicker.
Steve has been pioneering the process with the http stuff as the first cut of a merlin facility. Getting a Jetty web server up and running is only a small piece. The real power comes when you have an avalon component that is also a J2EE servlet and you have framework in place that specifies a routing of requests on a application path to you servlet-as-component instance.
Same concept with your message-driven-service. Some framework stuff that routes messages on some queue/subscriber to some message-driven-component.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
