So if I wanted ALL jsp pages in my webapp to be compiled when it is
deployed would I change this part of the webdefault.xml file:
jsp
org.apache.jasper.servlet.JspServlet
0
to this?:
jsp
org.apache.jasper.servlet.JspServlet
1
I tested this by creating a jsp page that does
) for a couple of
years.
http://www.javaworld.com/javaworld/jw-07-2003/jw-0725-morejsp.html
-Original Message-
From: Eric Jain [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 2:04 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Re: Jetty vs Tomcat
+1
Not being able to have J
I will integrate it for U ... what is it worth in savings for U then ?
...
xo
On Friday, Aug 8, 2003, at 01:38 Europe/Stockholm, Phil Shrimpton wrote:
On Thursday 07 August 2003 18:08, Rod Macpherson wrote:
Hi,
That's two (count 'em) votes for precompiled JSPs being integrated!
You can add a
+1
Not being able to have JSPs compiled at deploy time is currently a big
issue for me as well.
Precompiling outside of the server doesn't work for us, as we have all
requests mapped to a default servlet.
Retrieving every page after the application is deployed doesn't work
either, as we do not a
Create an RFE on sourceforge with the requirements so the issue is clear.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Rod Macpherson wrote:
From our perspective it's not the incremental builds but rather the high
frequency releases th
You can access the jasper configuration in Jetty via
the webdefault.xml in the jbossweb-jetty.sar
regards
JD Brennan wrote:
Do you have an example of what the web.xml mappings
would look like? I've checked the Tomcat docs, searched
the JBoss 3.2.1 source tree and even read the web.xml
DTD, but I
On Thursday 07 August 2003 18:08, Rod Macpherson wrote:
Hi,
> That's two (count 'em) votes for precompiled JSPs being integrated!
You can add another 1 to that. An MBean would be good.
> Definitely a big bonus in terms of speeding up the development cycle
> because we have hundreds of pages. I
Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 3:49 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Re: Jetty vs Tomcat
Not exactly what you are asking for but...
If you are doing incremental builds into an unpacked war
you can specify
You can simply set your own handler in the root context and
if it handles all requests, then a not found handler will never
be created or used.
You can also do this without jetty too much specific code simply by
creating a root webapp as part of the jetty configuratoin (call
addWebAppliction). Thi
I don't. Jetty has a RootNotFoundHandler but I don't know how
you configure it to do something other than the default
behaviour.
Regards,
Adrian
On Thu, 2003-08-07 at 14:33, Felipe Oliveira wrote:
> do you know how i can set a context without using a war file or a ear
> file?
> i want to have a d
do you know how i can set a context without using a war file or a ear
file?
i want to have a default "/" context that will be used when my "/" ear
file is being deployed.
tks!
Adrian Brock wrote:
Not exactly what you are asking for but...
If you are doing incremental builds into an unpack
Not exactly what you are asking for but...
If you are doing incremental builds into an unpacked war
you can specify for each application where to put the
class files.
Jasper respects the web-app's temp directory property.
As long as the class files have timestamps after the jsp
files they don't ne
12 matches
Mail list logo
