I do not have problems with JBoss 3.2.3 on Windows 2000 with EARs containing WARS. I never tried 3.2.1.
I recommend testing access to http://localhost:8080/jmx-console or http://localhost:8080/web-console if these applications are still installed. If they fail in 3.2.1, then try 3.2.3. They should run out of the box.
This helps to eliminate possibilities. If these apps don't run, then the problem probably isn't in your ear. If they do run, then you can start to compare differences.
The jmx-console apps work fine on both systems. I'm wondering if the xml files for ejbs are in the wrong place and it can't ffind the path to them.? In fact this has worked before so also wondering whether something has happened to jboss !?
Does anyone know the proper construction of the .ear file?
Here is the EAR jar construction of an app that works on both Linux and Windows and in JBoss 3.2.3:
The application.xml is probably critical to solving your problem. Note that the META-INF folder must be in upper case.
Remove the ! from the beginning of taqs in XML here, are only inserted to ensure the XML displays in the forum. The contents of application.xml:
<?xml version="1.0" encoding="ISO-8859-1"?> <!application> <!display-name>JoshuaBranch AS<!/display-name> <!description>JoshuaBranch AS<!/description> <!module> <!web> <!web-uri>JBAS.war<!/web-uri> <!context-root>/jbas<!/context-root> <!/web> <!/module> <!module> <!ejb>JBAS.jar<!/ejb> <!/module> <!/application>
The application.xml both tells it the name of the war, which is presumed to be in the root of the ear, and it maps it to a context root. In the above example the web module will be accessible from http://localhost:8080/jbas
The files in the lib folder of the ear are utility jars, not modules, so they are referenced by the ejb jar's manifest. But that's a bit off topic for your issue.
Hopefully this helps.
Actually I've discovered since that the ear file isn't depoloying under the default server - under jboss but works under the all - server part ? !
If i swith to run -c all it loads it all up . So therefore the problem is not with the ear file but something in the default setup that causes it not to deploy .