Hi Marc.
W/o that entry, and no ejb-jar.xml file, the exception (duplicate JNDI name) still
occurs.
With an empty ejb-jar.xml file (no data in the tags), this Jar file deploys normally,
and I only have stacktraces for a datasource defined for JBoss, and the
Ear itself (attached).
I am verifyi
lto:[EMAIL PROTECTED]]
|Sent: Thursday, February 28, 2002 8:25 AM
|To: marc fleury
|Cc: jboss-development
|Subject: Re: [JBoss-dev] "Empty Jars" Break EJBDeployer?
|
|
|Hi Marc.
|
|W/o that entry, and no ejb-jar.xml file, the exception (duplicate
|JNDI name) still occurs.
|With an empty
|is attempting to be deployed. HRXCommon.jar is in the MANIFEST.MF
|classpath for HRXExporter.jar.
remove that entry
|Have I found another strange test case to mess up the classloaders?
no, the classloader used here is the straight URLClassLoader as I showed in
the code. You are not using Uni
Hi Marc.
Triple checked jar file (at 12K, I figured small enough to attach).
No ejb-jar.xml file (or I am blind - if so, you are allowed to laugh at me ;) )
No Classpath set up so not that.
It does appear to be the ejb-jar.xml file from HRXCommon.jar that is attempting to be
deployed. HRXCommo
|I have a jar with some classes in it which will eventually have
|EJBs. At its current stage of development, it does not have any
|EJBs, and no ejb-jar.xml file
|(or any other xml files). Yet when JBoss tries to deploy my
|application, it is behaving as if the the jar file in question has
|EJBs
Greetings.
I have a jar with some classes in it which will eventually have EJBs. At its current
stage of development, it does not have any EJBs, and no ejb-jar.xml file
(or any other xml files). Yet when JBoss tries to deploy my application, it is
behaving as if the the jar file in question
