As Jetty deploys it, it will print out the context to which it is deployed.


There are three ways in which you may have specified the context:

in ear/META-INF/application.xml
by deploying a naked war - for foo.war the context /foo will be used
in war/WEB-INF/jboss-web.xml

probably in that order...

You're getting the 404 because there is nothing at the context that you 
are hitting....

An excerpt from you log you help resolve this.

Jules


bryan hansen wrote:
> I had a basic servlet that was deploying just fine on
> Tomcat and JBoss 2.4.4. I tried to deploy the app on
> Jetty and JBoss 3.0.0 and it deploys fine, but I am
> unable to find where the page was deployed to. Is
> there a different url pattern for Jetty? I don't even
> get a splash page to come up for the webserver. I just
> get a 404 not found error.
> 
> I can remember that on 2.4.4 you had to do something
> like http://localhost:8080/jboss/index.html. I have
> the context set in the application.xml file and I
> setup a Servlet map hoping to alleviate this, but I
> still can't find the servlet?
> 
> Any help would be appreciated.
> Thanks,
> 
> Bryan
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas - 
>http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> 
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user




_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to