The JMS examples that weblogic ships with WLS 5.1 use the create to create
Destinations.
try {
queue = (Queue) ctx.lookup(queueName);
} catch (NamingException ne) {
queue = qsession.createQueue(queueName);
ctx.bind(queueName, queue);
}
But thats not the point I was trying to make. All I am saying is that just
as the JMS spec requires for nonTemporary Destinations to be
javax.naming.Referenceable and java.io.Serializable why cant temporary
Destinations also be required to be java.io.Serializble, so the EJB's can
use them through the ejbActivate-ejbPassivate cycle
Nitin
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nitin Sood
> Thanks for your reply. I did not use administered queues because I wanted
> the tempQueue to last as long as the stateful bean in there. The JMS spec
> **does not** have a delete method for non-temporary Destinations.
Nor does it specify how destinations are *created*. These are administrative
operations better left to, say, a JMX framework.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
