The JMS spec has nothing to say about JNDI namespace conventions for administered objects, so add support for this. There is an assumption of a flat namespace under queue and topic that needs to be generalized.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Budworth" <[EMAIL PROTECTED]> To: "Hiram Chirino" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, November 27, 2001 12:55 PM Subject: Re: [JBoss-dev] JMS issues re: stopservice, jndi names > Does anyone know if it's actually legal for JMS topics/queues to have > structure? > > I was making the change for binding subcontexts automatically (using > org.jboss.naming.Util). And it deploys fine. > > But, if I kill jboss and restart it (without my sar that defines the > queue in deploy), it throws exceptions because it finds a directory in > the db/messaging/QUEUE.mycompany/myqueue > > The queue was "mycompany/myqueue", which was created correctly as > db/messaging/QUEUE.mycompany/myqueue/ > > I can only assume that the queue restoration only looks one level deep. > And attempts to restore a queue (even though the queue is not in any DD > anymore) > > I'm just trying to understand what all should be fixed. > > So, questions of the day are : > > 1) Can a queuename have depth? > 2) Should all queues be restored at jboss startup regardless of if they > are needed anymore? > 2a) Or when the MBEAN descriptor is located? > > -David > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
