-
1. Re: Deployment problems with JBoss 3.0.0/3.0.2 (Classpath/Cl
petertje Sep 24, 2002 2:15 PM (in response to steffen)Steffen,
I've seen that exception before: in my case it was caused by the fact that my ejb jars were not deployed in the correct order (there were some dependencies between them). Setting classpath entries in the manifest does not help in this case; what does help is to package the ejb-jars inside each other; then they are deployed in inside-out order.
Furthermore, i'd advise you to put your library jars in the lib directory, or some other dir configured as classpath (see user-service.xml).
Hope this helps,
Peter. -
2. Re: Deployment problems with JBoss 3.0.0/3.0.2 (Classpath/Cl
adrian.brock Sep 25, 2002 8:58 AM (in response to steffen)This sounds like a bug.
Looks like it is trying to deploy the ejb twice.
Can you show the jar -tf for the ear
The application.xml
and the MANIFEST.MFs from the jars.
Regards,
Adrian -
3. Re: Deployment problems with JBoss 3.0.0/3.0.2 (Classpath/Cl
steffen Sep 26, 2002 9:12 AM (in response to steffen)Here's the additional information you reqested:
output of 'jar -tf EaiTestApp.ear':
----------------------------------------------------
META-INF/
META-INF/MANIFEST.MF
eai-test-beans.jar
rsc-bol.jar
trend-eai.jar
trend-ejb-bridge.jar
trend-message-dispatcher.jar
trend-standard-business-service.jar
META-INF/application.xml
----------------------------------------------------
application.xml:
----------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN" "http://java.sun.com/j2ee/dtds/application_1_2.dtd">
<display-name>EaiTestApp</display-name>
trend-message-dispatcher.jar
trend-ejb-bridge.jar
trend-standard-business-service.jar
eai-test-beans.jar
----------------------------------------------------
eai-test-beans.jar contains this MANIFEST.MF:
----------------------------------------------------
Manifest-Version: 1.0
Created-By: Ant 1.4.1
Class-Path: trend-eai.jar rsc-bol.jar
----------------------------------------------------
The other JARs have no classpath set, they all have this MANIFEST.MF:
----------------------------------------------------
Manifest-Version: 1.0
Created-By: Ant 1.4.1
----------------------------------------------------
When deploying the application on other servers (WebLogic/WebSphere) we do set the classpath in the other MANIFEST.MF files, but as I explained in my first posting, this doesn't work for JBoss.
May it be a problem that the EJB classes (remote interface, home interface and implementation) are in some cases not contained in the EJB-jar-file itself, but in a library (trend-eai.jar)?
Steffen -
4. Re: Deployment problems with JBoss 3.0.0/3.0.2 (Classpath/Cl
adrian.brock Sep 26, 2002 11:49 AM (in response to steffen)Yes, this is definitly a bug.
trend-eai.jar gets deployed twice or at least it
tries.
Regards,
Adrian -
5. Re: Deployment problems with JBoss 3.0.0/3.0.2 (Classpath/Cl
andistuttgart Oct 9, 2002 5:42 AM (in response to steffen)Hi,
i have exactly the same problem.
But when a copy/remove the ear several times, the deployment suddenly works !!???
Any ideas ???
Regards,
Andi -
6. Re: Deployment problems with JBoss 3.0.0/3.0.2 (Classpath/Cl
andistuttgart Oct 9, 2002 5:56 AM (in response to steffen)Hi ,
i have exactly the same problem.
But when i remove/copy the ear to the deploy directory for several times, it suddenly works.
Any ideas ??
Regards,
Andi