Looks like j2ee.jar comes with a CORBA-specific jndi.properties resource (or at least, your jar meta-inf classpath combined with your jboss-startup path extends the environment as to primarily point to such a resource). You need to ensure that the jboss jndi.properties (conf/<confname>/jndi.properties) is taken with preference in order to contact the JNP/RMIoverJRMP naming service correctly ... Best, CGJ -----Ursprüngliche Nachricht----- Von: Yaniv_Shaya [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 23. Januar 2001 12:50 An: 'jBoss' Betreff: [jBoss-User] jBoss conflicting with j2ee.jar Hi, I have an EJB that uses a class which is in a JAR, and the Metainf classpath there refers to j2ee.jar. When I add that jar to jBoss CLASSPATH, (without even deploying my component) this causes jBoss to generate lots of exceptions (attached) while initializing. Not only that, it changes the conf\default\jboss.jcml file to be unusable from that on, so even when I remove the jar from the CLASSPATH it doesn't work anymore until I bring back the old file. Why is that happening ? Is there a workaround other than removing the J2EE from being reference inside the Metainf in the jar ? Thanks, Yaniv. -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
