First of all, thanks for your responses. I will try to gather all this information up.
I think the motivation for changing it to an EAR file is related to ‘corporate decisions’ and maybe someone who doesn’t want to write the context whenever he installs some application in the server, although I am no one in the company to challenge this. My bad.
They are also still using Java EE 1.5.
I installed Glasshfish 2.1 and the Glassfish 2.1 connector to my eclipse Galileo. I think it manages fairly easy between the eclipse conector, the console and the web administration. I eventually find someplace where I can do any action. It’s very big compared to Tomcat and I feel a somehow lost, but I try to take it slowly.
In my EAR file there is not much, the WAR file, and inside the META-INF directory there are my application.xml and manifest.mf. My application.xml reads:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
id="Application_ID" version="5">
<display-name>foo</display-name>
<module>
<web>
<web-uri>FOO.war</web-uri>
<context-root>foo</context-root>
</web>
</module>
</application>
I access the url via http://localhost:8080/foo the server.log shows (in Spanish, I will translate it the best I can manage), by the way I use the web service to administrate the glassfish and not the win console.
[#|2010-04-29T09:46:59.722+0200|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=26;_ThreadName=Thread-419;|deployed with moduleid = foo|#]
[#|2010-04-29T09:46:59.909+0200|SEVERE|sun-appserver2.1|org.apache.catalina.core.StandardContext|_ThreadID=27;_ThreadName=Thread-418;_RequestID=9bff8714-d870-4f30-8a7a-22dca0375b6b;|PWC1300: Error while initialization of the resources in the context /foo|#]
[#|2010-04-29T09:46:59.909+0200|SEVERE|sun-appserver2.1|org.apache.catalina.core.StandardContext|_ThreadID=27;_ThreadName=Thread-418;_RequestID=9bff8714-d870-4f30-8a7a-22dca0375b6b;|PWC4430: The document base C:\Sun\SDK\jdk\glassfish\domains\domain1\docroot\FOO does not exist or it is a directory that can’t be read|#]
[#|2010-04-29T09:46:59.925+0200|SEVERE|sun-appserver2.1|org.apache.catalina.core.StandardContext|_ThreadID=27;_ThreadName=Thread-418;_RequestID=9bff8714-d870-4f30-8a7a-22dca0375b6b;|PWC1306: The start-up of the context /foo has failed because previous errors|#]
[#|2010-04-29T09:46:59.925+0200|INFO|sun-appserver2.1|org.apache.catalina.core.StandardContext|_ThreadID=27;_ThreadName=Thread-418;|PWC1240: The WebModule[/foo] container hasn’t been started|#]
As I said, I also tried to use the WAR directly and it also didn’t work. I deployed it well (or so it says) and then it has a pretty button (in the action column) to start the web service, the server gives me http://localhost:4848/applications/webApplicationLinks.jsf?appID=FOO&contextRoot=/FOO (the ear is foo while the war is FOO), and redirects me to a page telling me that if the server or the listener are not running it is possible that the links will not work. The below links are http://localhost:8080/FOO and http://localhost:8181/FOO (neither work, AKA http-404 in 8080 and blank page in 8181). By the way, this start button is not available in the ear, I don’t like that.
As for other interesting things on the server.log it doesn’t seem to say much more but I could be wrong since I am really very new in the server world.