> This would make my MessageDrivenService idea very simple (see original email
> on users list). The JMS onMessage() is really a lifecycle method and it'd
> would be nice to find a way to include it without having to customize
> Fortress, Phoenix, and Merlin in case I want to swap containers (which I
> do). Of course I could always write a custom block or service, but
> lifecycle extensions seem like a more elegant solution.
>
> I'm forwarding this to the dev list to see if I get more of a response.
I work with Creator/Accessor of Merlin to extend lifecycle with JMX
(un)registration. And I also work (a little) with JMS under Avalon
(Phoenix); and instead of usage of exention I define a service
QueueFactory (implements/wrap jms.QueueConnectionFactory) and my
"MessageDrivenService" declare a dependecy to this service (in
service(...) and use it (in initialize()) to create session(s) (session
must be SingleThreaded). Configuration (queue name,...) are set in the
configuration of the "MessageDrivenService" (each instance use a
differente queue (name) as input or output.
--
--------------------------------------------------------------
David "Dwayne" Bernard Freelance Developer (Java)
mailto:[EMAIL PROTECTED]
\|/ http://dwayne.java-fan.com
--o0O @.@ O0o-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
