Hello! There seems to be something wrong with java:comp naming context as seen from within Jetty in the latest CVS sources.
That's what a servlet sees when the app is run in a JBoss/Jetty from a couple of days ago: +- jaas +- TransactionPropagationContextImporter +- JmsXA +- MinervaSharedLocalCMFactory +- DefaultDS +- StdJMSPool +- MinervaXACMFactory +- TransactionManager +- TransactionPropagationContextExporter +- ConnectionFactory +- DefaultJMSProvider +- XAConnectionFactory +- Mail +- NoTransDS +- SecurityProxyFactory +- comp | +- UserTransaction[link -> UserTransaction] | +- env | | +- ejb | | | +- CustomersSessionRemote[link -> CustomersSessionBean] | | +- security | | | +- realmMapping | | | +- securityMgr +- MinervaNoTransCMFactory +- Sybase_J2EETEST And that's the same app run in todays build: +- jaas +- TransactionPropagationContextImporter +- JmsXA +- MinervaSharedLocalCMFactory +- DefaultDS +- StdJMSPool +- MinervaXACMFactory +- TransactionManager +- TransactionPropagationContextExporter +- ConnectionFactory +- DefaultJMSProvider +- XAConnectionFactory +- Mail +- NoTransDS +- SecurityProxyFactory +- comp +- MinervaNoTransCMFactory +- Sybase_J2EETEST Notice that java:comp context is empty. Has anybody else noticed that? Peter _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
