Greetings!
A few questions on lifecycle extentions:
1. Can Extentions (ie- something that extends AbstractCreator) implement
lifecycle methods themselves?
2. Is there anyway to get a handle on the component's meta-data as it's
being passed through the lifecycle extention?
Reasoning:
I want to create a MessageDrivenService lifecycle extention. It would allow
any service to be a JMS Message Listener and the equivalent to an Avalon
Message Driven Bean. The MessageDrivenService lifecycle would look
something like this (_very_ roughly):
public interface MessageDrivenService
extends MessageListener
{
public void session(Session jmsSession);
// and onMessage(Message jmsMessage) from MessageListener
}
The Lifecycle extention itself would need a way to be configured, establish
topic and queue connections and also need a way to know what destination the
MessageDrivenService wants to listen to. One way to do that would be to
specify the information in the service's meta-info, but the lifecycle
extention would need a way to retrieve that since I believe all it gets is
the object (service) and the context.
Any suggestions?
J. Aaron Farr
� SONY ELECTRONICS
� DDP-CIM
� (724) 696-7653
�
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
