If I set a cookie to "b'c" and then read it, I get "bc". I used the servlet API in jetty 5.1.10. Jetty should encode single quotes when setting a cookie.
Sorry for the accidental premature posting. --- Having a problem with an app that works under Tomcat, but not under Jetty. We have a problem between 2 particular JSP pages. The first is a full JSP page; the 2nd is more of a "partial" page - a header that gets included into several of the other JSP pages. It looks something like this: Full page (ApplicationUnavailable.jsp): <% <at> page session="false" %> <% <at> page contentType="text/html; charset=UTF-8" %> <% <at> taglib prefix="c" uri="http://java.sun.com/jstl/core" %> <% <at> taglib prefix="html" uri="/tags/struts-html" %> <% <at> taglib prefix="bean" uri="/tags/struts-bean" %> <% <at> taglib prefix="logic" uri="/tags/struts-logic" %> <html:html xhtml="true"> <head> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> <title><bean:message key="app.name"/>: Application Unavailable</title> <% <at> include file="stylesheets.jsp" %> </head> <body> <div> <% <at> include file="headershort.jsp" %> </div> etc. Partial page (headershort.jsp): <% <at> taglib prefix="c" uri="http://java.sun.com/jstl/core" %> <% String someProperty = (String)session.getAttribute("somePropertyKey"); etc. The problem I'm having is that Jetty is dying when compiling headershort.jsp: org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: 10 in the jsp file: /pages/headershort.jsp Generated servlet error: C:\DOCUME~1\drosenst\LOCALS~1\Temp\Jetty__8080_127_0_0_1_aweb\org\apache\jsp\pages\ApplicationUnavailable_jsp.java:120: cannot resolve symbol symbol : variable session location: class org.apache.jsp.pages.ApplicationUnavailable_jsp session.getAttribute("somePropertyKey"); ^ I'm a bit puzzled by this, though. I'm not sure why Jetty should be trying to compile headershort.jsp at all. It's never referenced directly; only as an include from another JSP page. If Jetty were processing the include as intended, this should all work fine, as ApplicationUnavailable.jsp - with the other page included - will compile correctly. Anyone know a workaround for this in Jetty? I'd much prefer to use Jetty for this development work instead of Tomcat. Thanks, DR ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Jetty-support mailing list Jetty-support <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jetty-support
Having a problem with an app that works under Tomcat, but not under Jetty. We have 2 particular JSP pages that are causing a problem. The first is a full JSP page; the 2nd is more of a "partial" page - a header that gets included into several of the other JSP pages. It looks something like this: Full page: <% <at> page session="false" %> <% <at> page contentType="text/html; charset=UTF-8" %> <% <at> taglib prefix="c" uri="http://java.sun.com/jstl/core" %> <% <at> taglib prefix="html" uri="/tags/struts-html" %> <% <at> taglib prefix="bean" uri="/tags/struts-bean" %> <% <at> taglib prefix="logic" uri="/tags/struts-logic" %> <html:html xhtml="true"> <head> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> <title><bean:message key="app.name"/>: Application Unavailable</title> <% <at> include file="stylesheets.jsp" %> </head> <body> <div> <% <at> include file="headershort.jsp" %> </div> etc. Partial page: e ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Jetty-support mailing list Jetty-support <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jetty-support
David, Which version of Jetty are you using? Also, which version of Tomcat are you using? Jetty uses the same jsp engine as Tomcat called Jasper. The most recent 5.x and 6.x versions of Jetty use jasper 5.5.12. It may be that the Tomcat version you're using has a different version. Knowing the various versions involved will help isolate the problem. cheers Jan Rosenstrauch, David wrote: > Sorry for the accidental premature posting. > > --- > > Having a problem with an app that works under Tomcat, but not under Jetty. > > We have a problem between 2 particular JSP pages. The first is a full JSP page; the 2nd is more of a "partial" page - a header that gets included into several of the other JSP pages. It looks something like this: > > Full page (ApplicationUnavailable.jsp): > > <% <at> page session="false" %> > <% <at> page contentType="text/html; charset=UTF-8" %> > <% <at> taglib prefix="c" uri="http://java.sun.com/jstl/core" %> > <% <at> taglib prefix="html" uri="/tags/struts-html" %> > <% <at> taglib prefix="bean" uri="/tags/struts-bean" %> > <% <at> taglib prefix="logic" uri="/tags/struts-logic" %> > <html:html xhtml="true"> > <head> > <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> > <META HTTP-EQUIV="Expires" CONTENT="-1"> > <title><bean:message key="app.name"/>: Application Unavailable</title> > <% <at> include file="stylesheets.jsp" %> > </head> > <body> > <div> > <% <at> include file="headershort.jsp" %> > </div> > > etc. > > > Partial page (headershort.jsp): > > <% <at> taglib prefix="c" uri="http://java.sun.com/jstl/core" %> > <% > String someProperty = (String)session.getAttribute("somePropertyKey"); > > etc. > > > The problem I'm having is that Jetty is dying when compiling headershort.jsp: > > org.apache.jasper.JasperException: Unable to compile class for JSP > > An error occurred at line: 10 in the jsp file: /pages/headershort.jsp > Generated servlet error: > C:\DOCUME~1\drosenst\LOCALS~1\Temp\Jetty__8080_127_0_0_1_aweb\org\apache\jsp\pages\ApplicationUnavailable_jsp.java:120: cannot resolve symbol > symbol : variable session > location: class org.apache.jsp.pages.ApplicationUnavailable_jsp > session.getAttribute("somePropertyKey"); > ^ > > > I'm a bit puzzled by this, though. I'm not sure why Jetty should be trying to compile headershort.jsp at all. It's never referenced directly; only as an include from another JSP page. If Jetty were processing the include as intended, this should all work fine, as ApplicationUnavailable.jsp - with the other page included - will compile correctly. > > Anyone know a workaround for this in Jetty? I'd much prefer to use Jetty for this development work instead of Tomcat. > > Thanks, > > DR > > > ============================================================================== > Please access the attached hyperlink for an important electronic communications disclaimer: > > http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html > ============================================================================== > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Jetty-support mailing list > Jetty-support <at> lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jetty-support > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Jetty-support mailing list Jetty-support <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jetty-support
> David, > > Which version of Jetty are you using? 5.1.6 > Also, which version of Tomcat are you using? 5.5.12 > Jetty uses > the same jsp engine as Tomcat called Jasper. The most recent > 5.x and 6.x versions of Jetty use jasper 5.5.12. It may be > that the Tomcat version you're using has a different version. > Knowing the various versions involved will help isolate the problem. > > cheers > Jan Sounds like a reasonable explanation. Although I can see the jasper-compiler.jar files bundled with both servers, I can't tell which versions they're using. Do you think I ought to be using a newer version of Jetty? Thanks, DR ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Jetty-support mailing list Jetty-support <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jetty-support
Hi David, The most recent version of Jetty 5.x is 5.10. I think you should upgrade and you will get the most recent jasper jars, along with some bug fixesI just noticed the Jetty site is a bit out of date with the Version information. I will update it asap. cheers Jan Rosenstrauch, David wrote: > >>David, >> >>Which version of Jetty are you using? > > > > 5.1.6 > > > >>Also, which version of Tomcat are you using? > > > > 5.5.12 > > > >>Jetty uses >>the same jsp engine as Tomcat called Jasper. The most recent >>5.x and 6.x versions of Jetty use jasper 5.5.12. It may be >>that the Tomcat version you're using has a different version. >>Knowing the various versions involved will help isolate the problem. >> >>cheers >>Jan > > > > Sounds like a reasonable explanation. Although I can see the jasper-compiler.jar files bundled with both servers, I can't tell which versions they're using. > > Do you think I ought to be using a newer version of Jetty? > > Thanks, > > DR > > ============================================================================== > Please access the attached hyperlink for an important electronic communications disclaimer: > > http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html > ============================================================================== > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Jetty-support mailing list > Jetty-support <at> lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jetty-support > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Jetty-support mailing list Jetty-support <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jetty-support
I'll give that a shot and report back. Thanks, DR > -----Original Message----- > From: jetty-support-admin <at> lists.sourceforge.net > [mailto:jetty-support-admin <at> lists.sourceforge.net]On Behalf Of Jan > Bartel > Sent: Wednesday, February 01, 2006 1:15 PM > To: jetty-support <at> lists.sourceforge.net > Subject: [Jetty-support] Re: problem compiling jsp include > > > Hi David, > > The most recent version of Jetty 5.x is 5.10. I think you should > upgrade and you will get the most recent jasper jars, along with > some bug fixes
No dice. Now I've got a new problem. It can't seem to initialize logging correctly for our app with these new
jars. (Stack trace below.)
Any ideas how to fix this?
Thanks,
DR
---
15:04:10.819 INFO [main] org.mortbay.util.Container.start(Container.java:74) >15> Started org.mortbay.jetty.servlet.WebApplicationHandler <at> 56860b
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.mortbay.start.Main.invokeMain(Main.java:151)
at org.mortbay.start.Main.start(Main.java:476)
at org.mortbay.start.Main.main(Main.java:94)
Caused by: java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:199)
at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:240)
at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:446)
at org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:321)
at org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:509)
at org.mortbay.util.Container.start(Container.java:72)
at org.mortbay.http.HttpServer.doStart(HttpServer.java:708)
at org.mortbay.util.Container.start(Container.java:72)
at org.mortbay.jetty.Server.main(Server.java:460)
... 7 more
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lan
g.Class; <at> 185572a for org.apache.commons.logging.impl.Log4JLogger (Caused by
java.lang.NoClassDefFoundError: org/apache/log4j/Category) (Caused by org.apache.
commons.logging.LogConfigurationException: No suitable Log constructor
[Ljava.lang.Class; <at> 185572a for org.apache.commons.logging.impl.Log4JLogger (Caused by
java.lang.NoClassDefFoundError: org/apache/log4j/Category))
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at org.apache.struts.action.ActionServlet.<clinit>(ActionServlet.java:375)
... 22 more
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor
[Ljava.lang.Class; <at> 185572a for org.apache.commons.logging.impl.L
og4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:413)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
... 26 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1610)
at java.lang.Class.getConstructor0(Class.java:1922)
at java.lang.Class.getConstructor(Class.java:1019)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:410)
... 27 more
> -----Original Message-----
> From: jetty-support-admin <at> lists.sourceforge.net
> [mailto:jetty-support-admin <at> lists.sourceforge.net]On Behalf Of
> Rosenstrauch, David
> Sent: Wednesday, February 01, 2006 2:45 PM
> To: 'jetty-support <at> lists.sourceforge.net'
> Subject: RE: [Jetty-support] Re: problem compiling jsp include
>
>
> I'll give that a shot and report back.
>
> Thanks,
>
> DR
>
> > -----Original Message-----
> > From: jetty-support-admin <at> lists.sourceforge.net
> > [mailto:jetty-support-admin <at> lists.sourceforge.net]On Behalf Of Jan
> > Bartel
> > Sent: Wednesday, February 01, 2006 1:15 PM
> > To: jetty-support <at> lists.sourceforge.net
> > Subject: [Jetty-support] Re: problem compiling jsp include
> >
> >
> > Hi David,
> >
> > The most recent version of Jetty 5.x is 5.10. I think you should
> > upgrade and you will get the most recent jasper jars, along with
> > some bug fixes
> >
> > I just noticed the Jetty site is a bit out of date with the
> > Version information. I will update it asap.
> >
> > cheers
> > Jan
==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support
Hi, I have been working quite heavily with the m2 plugin lately (*great* piece of work btw - and enormous productivity boost during development!!). I have a few remarks that might even further improve it's useability : - It would be nice if one could disable automatic scanning and somehow explicitly trigger a reload of the webapp. I'm in a situation where, during longer hacking sessions, jetty keeps reloading until it reaches OOM errors (typically after 10-15 reloads). Ideally i'ld like to keep the webapp in a "sane" state during development until i tell it to reload. Setting the scanning interval to a higher interval is ofcourse possible, but annoying when you want to test something and you've just missed the last scanning interval. - Showing some sort of timestamp after the reload is done makes it easier to see if the code changes made it in the last reload. Regards and thanks again for such a great plugin! Jorg Heymans ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Jetty-support mailing list Jetty-support <at> lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jetty-support
Never mind. Did some googling, and found that I need to put a copy of log4j into ext. DR > -----Original Message----- > From: jetty-support-admin <at> lists.sourceforge.net > [mailto:jetty-support-admin <at> lists.sourceforge.net]On Behalf Of > Rosenstrauch, David > Sent: Wednesday, February 01, 2006 3:10 PM > To: 'jetty-support <at> lists.sourceforge.net' > Subject: RE: [Jetty-support] Re: problem compiling jsp include > > > No dice. Now I've got a new problem. It can't seem to > initialize logging correctly for our app with these new jars. > (Stack trace below.) > > Any ideas how to fix this? > > Thanks, > > DR > > --- > > 15:04:10.819 INFO [main] > org.mortbay.util.Container.start(Container.java:74) >15> > Started org.mortbay.jetty.servlet.WebApplicationHandler <at> 56860b > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > orImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.mortbay.start.Main.invokeMain(Main.java:151) > at org.mortbay.start.Main.start(Main.java:476) > at org.mortbay.start.Main.main(Main.java:94) > Caused by: java.lang.ExceptionInInitializerError > at > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCo > nstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Dele gatingConstructorAccessorImpl.java:27) > at > java.lang.reflect.Constructor.newInstance(Constructor.java:274) > at java.lang.Class.newInstance0(Class.java:308) > at java.lang.Class.newInstance(Class.java:261) > at > org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:199) > at > org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:240) > at > org.mortbay.jetty.servlet.ServletHandler.initializeServlets(Se > rvletHandler.java:446) > at > org.mortbay.jetty.servlet.WebApplicationHandler.initializeServ > lets(WebApplicationHandler.java:321) > at > org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApp > licationContext.java:509) > at org.mortbay.util.Container.start(Container.java:72) > at org.mortbay.http.HttpServer.doStart(HttpServer.java:708) > at org.mortbay.util.Container.start(Container.java:72) > at org.mortbay.jetty.Server.main(Server.java:460) > ... 7 more > Caused by: > org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: No > suitable Log constructor [Ljava.lan > g.Class; <at> 185572a for > org.apache.commons.logging.impl.Log4JLogger (Caused by > java.lang.NoClassDefFoundError: org/apache/log4j/Category) > (Caused by org.apache. > commons.logging.LogConfigurationException: No suitable Log > constructor [Ljava.lang.Class; <at> 185572a for > org.apache.commons.logging.impl.Log4JLogger (Caused by > java.lang.NoClassDefFoundError: org/apache/log4j/Category)) > at > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log > FactoryImpl.java:543) > at > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(Log > FactoryImpl.java:235) > at > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(Log > FactoryImpl.java:209) > at > org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) > at > org.apache.struts.action.ActionServlet.<clinit>(ActionServlet. > java:375) > ... 22 more > Caused by: > org.apache.commons.logging.LogConfigurationException: No > suitable Log constructor [Ljava.lang.Class; <at> 185572a for > org.apache.commons.logging.impl.L > og4JLogger (Caused by java.lang.NoClassDefFoundError: > org/apache/log4j/Category) > at > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstruct > or(LogFactoryImpl.java:413) > at > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log > FactoryImpl.java:529) > ... 26 more > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category > at java.lang.Class.getDeclaredConstructors0(Native Method) > at > java.lang.Class.privateGetDeclaredConstructors(Class.java:1610) > at java.lang.Class.getConstructor0(Class.java:1922) > at java.lang.Class.getConstructor(Class.java:1019) > at > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstruct > or(LogFactoryImpl.java:410) > ... 27 more > > > > -----Original Message----- > > From: jetty-support-admin <at> lists.sourceforge.net > > [mailto:jetty-support-admin <at> lists.sourceforge.net]On Behalf Of > > Rosenstrauch, David > > Sent: Wednesday, February 01, 2006 2:45 PM > > To: 'jetty-support <at> lists.sourceforge.net' > > Subject: RE: [Jetty-support] Re: problem compiling jsp include > > > > > > I'll give that a shot and report back. > > > > Thanks, > > > > DR > > > > > -----Original Message----- > > > From: jetty-support-admin <at> lists.sourceforge.net > > > [mailto:jetty-support-admin <at> lists.sourceforge.net]On Behalf Of Jan > > > Bartel > > > Sent: Wednesday, February 01, 2006 1:15 PM > > > To: jetty-support <at> lists.sourceforge.net > > > Subject: [Jetty-support] Re: problem compiling jsp include > > > > > > > > > Hi David, > > > > > > The most recent version of Jetty 5.x is 5.10. I think you should > > > upgrade and you will get the most recent jasper jars, along with > > > some bug fixes
RSS Feed1 | |
|---|---|
9 | |
15 | |
13 | |
4 | |
5 | |
15 | |
5 | |
4 | |
4 | |
11 | |
11 | |
11 | |
5 | |
46 | |
25 | |
14 | |
8 | |
21 | |
10 | |
15 | |
16 | |
19 | |
23 | |
19 | |
31 | |
14 | |
39 | |
21 | |
13 | |
32 | |
40 | |
32 | |
35 | |
26 | |
43 | |
71 | |
50 | |
82 | |
65 | |
48 | |
111 | |
98 | |
99 | |
67 | |
102 | |
95 | |
73 | |
74 | |
88 | |
62 | |
58 | |
82 | |
105 | |
91 | |
99 | |
82 | |
95 | |
87 | |
100 | |
103 | |
157 | |
129 | |
104 | |
113 | |
69 | |
130 | |
106 | |
141 | |
152 | |
171 | |
114 | |
108 | |
123 | |
110 | |
148 | |
243 | |
136 | |
312 | |
132 | |
197 | |
180 | |
193 | |
200 | |
190 | |
142 | |
194 | |
141 | |
160 | |
107 | |
116 | |
111 | |
66 | |
118 | |
75 | |
106 | |
96 | |
108 | |
91 | |
139 | |
104 | |
122 | |
145 | |
114 | |
144 | |
210 | |
142 | |
126 | |
155 | |
281 | |
167 | |
212 | |
115 | |
116 | |
136 | |
115 | |
152 | |
114 | |
302 | |
224 | |
223 | |
230 | |
201 | |
151 | |
328 | |
189 | |
301 | |
242 | |
244 | |
225 | |
262 | |
170 | |
138 | |
242 | |
76 |
