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. HRXCommon.jar is in the MANIFEST.MF classpath for HRXExporter.jar.
Have I found another strange test case to mess up the classloaders?
Btw, HRXCommon.jar has the base classes for HRXExporter, and the classes in question
are used in (currently) 12 - 15 other jar files, all of which have EJBs.
-Steve
marc fleury wrote:
> |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 and tries to deploy them,
> |using a descriptor file from another jar.
>
> no,
>
> the actual lines of code are
>
> EJBDeployer.java ca 255
>
> try
> {
>
> URL dd = di.localCl.getResource("META-INF/ejb-jar.xml");
>
> .. if it there we cool and say Ok we deploy this
>
> and localCL is just a STRAIGHT URLClassloader. So you have a
> META-INF/ejb-jar.xml floating around, either in your jar file (double check)
> or on your SYSTEM classpath
>
> marcf
>
> |
> |Help, please?
> |
> |-Steve
> |
[snip to save bandwidth]
--
Stephen Davidson
Java Consultant
Delphi Consultants, LLC
http://www.delphis.com
Phone: 214-696-6224 x208
HRXExporter.jar
Description: Binary data
