-
1. Re: ContextPath
jules Aug 21, 2002 8:36 PM (in response to gummy)do you get a line in your log like this:
00:18:09,312 WARN [jbossweb] WARNING: pathSpec should start with '/' or '*' : WithoutLeadingSlashTest
???
What webcontainer do you normally use that allows you a context of '' ?
Jules -
2. Re: ContextPath
gummy Aug 21, 2002 8:56 PM (in response to gummy)Just for the note:
my application was used to run in websphere. but now I try to deploy the application to jboss.
in websphere, the previous coders code the paths in jsp as:
<%=request.getContextPath() + "/someservlet"%>
in webshpere, the setup to an empty rootcontext is okay, but now with jetty, it looks like by default it is "/".
David.
I am just wondering if there is a way to set teh jetty to not default the contextpath as "/". -
3. Re: ContextPath -> Change to 3.0.1
tbfmicke Aug 22, 2002 4:35 AM (in response to gummy)This seems to happen when the request is first
sent to a sevlet that forwards to a jsp.
(Theres a similar problem when using struts)
The good news is that it works on 3.0.1 so
change to that and you will be rewarded :-)
Regards -
4. Re: ContextPath -> Change to 3.0.1
gummy Aug 23, 2002 6:09 PM (in response to gummy)yep, that works in 3.0.0. Eventhough it took me a while to install 3.0.1 because of the missing jetty required packages. But it work at last, and that problem is fixed.
Thanks for the hints. You guys are great.
David Li.
Thx again and have nice weekend. -
5. Re: ContextPath -> Change to 3.0.1
jules Aug 24, 2002 9:01 PM (in response to gummy)what "missing jetty required packages" ?
If you let me know the problem, I will fix it....
Jules -
6. Re: ContextPath -> Change to 3.0.1
gummy Aug 29, 2002 5:36 PM (in response to gummy)Jules, the packages missing are:
javax.servlet.jar under the
jboss-3.0.1\server\default\deploy\jbossweb.sar
and
com.sun.net.ssl.jar under the
jboss-3.0.1\server\default\ext
note: ext have to be created.
Hope that will help.
David Li. -
7. Re: ContextPath -> Change to 3.0.1
jules Aug 29, 2002 6:35 PM (in response to gummy)servlet.jar is not shipped inside the Jetty plugin as it contains the servlet and JSP APIs, which are considered part of the J2EE 1.3 platform (not it's implementation) and thus shipped in /lib.
The ssl jar is not shipped as this fn-ality is not enabled for any of the configurations, you can get it elsewhere (if you want to enable it) and I haven't investigated the legalities of shipping it with JBoss.
I'll put the ssl.jar on my TODO list for consideration.
So - they are not "missing" or "required" - but present or (currently considered) optional.
Jules -
8. Re: ContextPath -> Change to 3.0.1
gummy Aug 29, 2002 7:23 PM (in response to gummy)Okay, the reason I say it is missing is when I start up JBoss with Jetty, there are two warning messages regards to the referrences of the two packages I mentioned is missing, and i just follow those messages and put these two jars into the correct directories. I know the servlet package is there, and I got the ssl package from the jetty package i downloaded from apache.
Thank you Jules for the consideration of ssl.jar.
David Li.
ps. for my application, it is required ssl.jar because of the extra security I put in. -
9. Re: ContextPath -> Change to 3.0.1
jules Aug 30, 2002 8:51 PM (in response to gummy)The warnings were from a Jetty MANIFEST.MF which needed updating (now fixed in CVS) and were harmless.
Glad to hear you have SSL working - did you have any problems ?
Care to write a brief paragraph for my FAQ ?
If you do - I'll put the SSL jar into the distro - can't say fairer than that !
Jules