I've messed around a little with Jetty and JSPs :
These are things I would try :
1. Update to the latest JBoss-Jetty - Scott will be putting it on the
binaries page soon - if you are in a hurry try :
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/jboss/binaries/JBoss-2.4.0BETA_Jetty-3.1.RC5-1.tgz?rev=1.1
If the problem persists...
We need to see a log of what happens when you hit the URL and know what
version and make of JVM you are running and on what platform.
We need to see your web.xml.
Jetty should load a webdefault.xml file with each WebApp - this is
configured in jboss/conf/jetty/jboss.jcml, thus :
<mbean code="org.jboss.jetty.JettyService"
name="DefaultDomain:service=Jetty">
<attribute name="JettyHome">../../jetty</attribute>
<attribute
name="Configuration">file:../conf/jetty/jetty.xml</attribute>
<attribute name="WebDefault">../../jetty/etc/webdefault.xml</attribute>
<attribute name="UnpackWars">true</attribute>
<attribute name="PublishMBeans">true</attribute>
</mbean>
This file gives default mappings for all webapps. You should have the
following mapping in this file:
<servlet-mapping>
<servlet-name>JSP</servlet-name>
<url-pattern>*.jsp,*.jsP,*.jSp,*.jSP,*.Jsp,*.JsP,*.JSp,*.JSP</url-pattern>
</servlet-mapping>
try adding the admin servlet to your jboss/conf/jetty/jboss.jcml, by
pasting the following in :
<Call name="addContext">
<Arg>/admin</Arg>
<Call name="addServlet">
<Arg>Admin</Arg>
<Arg>/</Arg>
<Arg>com.mortbay.Servlet.AdminServlet</Arg>
</Call>
</Call>
just before the final </Configure> - then restart and hit e.g.
localhost:8080/admin.
You should see exactly what Servlets Jetty is running. The Contexts in
which they are running, and their mappings.
Confirm that there is a JSP mapping for the context of the webapp your
are deploying.
Start with that and we'll see where we get to.
Good Luck,
Jules
[EMAIL PROTECTED] wrote:
> I am having great trouble getting JBoss/Jetty to treat my JSPs as
> JSPs/Servlets. It just treats them as if they were petty HTML pages.
>
> I put the JSPs inside a WAR in the EAR, stick in an application.xml in
> the EAR, and put the whole shebang into the jboss/deploy directory. It
> sort of deploys and the pages are available on port 8080, but get
> treated as pure HTML. Do I need to do anything more than this to get
> Jetty to treat my JSPs with the respect they deserve? Do I need to
> specify in any of the deployment descriptors that there are JSPs in
> the WAR? I would have though this is obvious from the file names, but
> apparantly not.
>
> My EAR includes
> META-INF/
> META-INF/MANIFEST.MF
> account.war
> META-INF/application.xml
>
> and the WAR includes
> META-INF/
> META-INF/MANIFEST.MF
> WEB-INF/
> WEB-INF/web.xml
> signup.jsp
>
> I use JBoss-2.2.2_Jetty-3.1.RC5.
>
> Is this easier to do with Tomcat?
>
> Cheers
> Bent D
> --
> Bent Dalager - [EMAIL PROTECTED] - http://www.pvv.org/~bcd
> powered by emacs
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
