After taking a shot at implementing this, by way of making the QueueManager and TopicManager's startService() function do the validation and throw if it fails, I find that the MBean get's stuck in the JMX tree.
Is this a MBeanServer bug? (where a bean doesn't go away when an exception is thrown by start())? I've seen this before. So I think it is. But I don't want to commit my code just in case it's my bug. (since it requires a jboss restart to make it go away). -David On Thu, 29 Nov 2001, David Budworth wrote: > Ok, now that we have the ability to set the JNDI name on a queue/topic, > I would like to fix the bug (that I put in) in regards to deep queue > names. > > For simplicities sake, I'll just revert the file PM back to the way it > was. > > But, since there was (and will be when I revert) a bug there that if > you create a queue/topic with depth (ie: mycompany/queues/q1) > > The File PM will fail at next startup. > > So, I'd like to add some name validation. > > Is anyone uncomfortable if I enforce the queue names to be alpha-numeric > only? (via, Character.isLetterOrDigit()) > JBoss (as it ships), doesn't define any topics/queues that would violate > that rule right now. > > Opinions? > > -David > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
