JNDIView should not depend on anything other than the naming serivce. It needs a mechanism to query for the ObjectNames of the deployers from which it attempts to obtain the deployed application info from, or this needs to be available in a different manner.
----- Original Message ----- From: "Adrian Brock" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 05, 2002 7:03 PM Subject: [JBoss-dev] JNDI View > JNDI View is broken due to the JMX Domain changes. > > The container factory is now registered in domain > "jboss.j2ee" but ContainerFactoryMBean has no domain > so the default "jboss" is used. > > Two points: > 1) Shouldn't it be possible to run jboss without > j2ee, so why does it barf when it can't find this > service? One line saying j2ee is not present would > be better. The log can contain the full exception > trace as a warning. > 2) If it really does depend on this service, this > could be configured with a > <depends optional-attribute-name="J2EEContainerFactory">jboss.j2ee:service=ContainerF actory</depends> > > Regards, > Adrian > ______________________________________________________________________ > View this jboss-dev thread in the online forums: > http://jboss.org/forums/thread.jsp?forum=66&thread=6719 > > _______________________________________________ > 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
