> > 2. Is there anyway to get a handle on the component's meta-data as it's
> > being passed through the lifecycle extention?
> Looks like that's a no.
>
> Extensions only get the component object itself and the context. I suppose
> it's possible one could hook the meta-info into the context somehow, but
> that seems ugly. Is it unreasonable to ask that extensions have access to
> this information? I would say yes, but unfortunately there's no standard
> meta-info API between containers.
>
> One hack would be to supply the component's configuration information to the
> extension, but it doesn't seem like that sort of thing should belong there.
> Instead, this sort of meta-data probably goes along with Merlin's appliance
> attributes (so I suppose there's almost a solution for Merlin).
>
> These sorts of features could really enhance the lifecycle extension API.
> It would allow users to extend containers without having to actually extend
> the container class and, perhaps more importantly, do so in a container
> agnostic way.
>
> 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.
> jaaron
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------
Marge, you're my wife and I love you very much. But you're living in a
world of makebelieve. With flowers and bells and leprechauns. And magic
frogs with funny little hats...
-- Homer Simpson
Blood Feud
---------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
