Hi
All,
I am developing a Message Driven Bean, to
be deployed on the BEA WebLogic 7.0 Server,
for this I referred to the examples provided with the Evaluation copy of the same.
for this I referred to the examples provided with the Evaluation copy of the same.
In the Examples Server of BEA WebLogic 7.0
Server in the following
path
samples_home\server\src\examples\jms\queue\QueueReceive.java
there is source for the QueueReceive.java program.
This program is the Bean class for the example of Message Driven Beans.
According to the EJB 2.0 Specification, a Message Driven Bean class
must implement both "MessageDrivenBean" and "MessageListener" interface.
But in the example program QueueReceive.java provided with the Examples
Server of BEA WebLogic 7.0 Server, only MessageListener interface is implemented.
samples_home\server\src\examples\jms\queue\QueueReceive.java
there is source for the QueueReceive.java program.
This program is the Bean class for the example of Message Driven Beans.
According to the EJB 2.0 Specification, a Message Driven Bean class
must implement both "MessageDrivenBean" and "MessageListener" interface.
But in the example program QueueReceive.java provided with the Examples
Server of BEA WebLogic 7.0 Server, only MessageListener interface is implemented.
IOW what does it mean when an MDB
implementation does not implement the MessageDrivenBean
interface, as mandated by the EJB spec. Is this a violation of the spec? Is there any
specific reason for doing this? How does it alter the behaviour ( response, actually!)
of the MDB.
interface, as mandated by the EJB spec. Is this a violation of the spec? Is there any
specific reason for doing this? How does it alter the behaviour ( response, actually!)
of the MDB.
Please let me know if you need any more
information on the same.
Regards,
Rohit Parik
Rohit Parik
