Jan Luehe wrote:
>
>
> Scott Oaks wrote On 03/23/06 11:23,:
>
>> You can configure the appserver so that it compiles JSPs in process:
>>
>> Edit your domain's default-web.xml and
>> add a "fork" init param with a value of "false" to your JspServlet, as
>> follows:
>>
>> <servlet>
>> <servlet-name>jsp</servlet-name>
>> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
>> <init-param>
>> <param-name>xpoweredBy</param-name>
>> <param-value>true</param-value>
>> </init-param>
>> <init-param>
>> <param-name>fork</param-name>
>> <param-value>false</param-value>
>> </init-param>
>> <load-on-startup>3</load-on-startup>
>> </servlet>
>>
>> I continue to advocate that this should be the default.
>
Interesting. I can't comment on making this default behavior for appserver.
However it would take all of 5 seconds for me enable this add this as a
default property for NetBeans 5.5 developed web applications.
Would this setting this aid or hinder development of web applications?
It would seem that it would speed things up. I just want to make sure
that it would not also obfuscate possible error messages at the same
time because that would be undesirable.
-Peter
>>
>>
>
> Just for the record: The preferred way of customizing your
> JSP compiler in a more portable way is by specifying the init
> params supported by the org.apache.jasper.servlet.JspServlet
> as properties of the <jsp-config> element in your sun-web.xml,
> e.g., instead of referencing the org.apache.jasper.servlet.JspServlet
> and the init params you wish to override in your web.xml, like this:
>
> <servlet>
> <servlet-name>jsp</servlet-name>
> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
> <init-param>
> <param-name>xpoweredBy</param-name>
> <param-value>false</param-value>
> </init-param>
> </servlet>
>
> add this to your sun-web.xml:
>
> <sun-web-app>
> <jsp-config>
> <property name="xpoweredBy" value="false" />
> </jsp-config>
> </sun-web-app>
>
>
> Jan
>
>
>> -Scott
>>
>> On Thu, 2006-03-23 at 14:15, Kohsuke Kawaguchi wrote:
>>
>>
>>> I was deploying a new appliation to Glassfish this morning with
>>> Dinesh, and we noticed that it seems to be compiling JSPs by
>>> launching an external javac (more over, it seems to be doing so for
>>> each tag file.)
>>>
>>> This made it unbearably slow to see the web pages. Why is it doing
>>> so? Can't we just load javac in the AppServer JVM?
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>