dev@glassfish.java.net

Re: JSP debugging issues with V2 b33

From: Jan Luehe <Jan.Luehe_at_Sun.COM>
Date: Wed, 31 Jan 2007 09:16:44 -0800

Peter,

Peter Williams wrote On 01/31/07 08:48 AM,:

> The default is false? That means that all development projects will
> have to manually know about this and turn it on (or the IDE will have
> to be smart enough to figure it out).


See Kin-Man's earlier reply: Netbeans is going to set both "keepgenerated"
(which will write out the generated .java) and "saveByteCode" (which
will write
out the generated .class) to true when running on Java 6.

>
> Any reason why the default cannot be true?


Because that would defeat the purpose of in-memory compilation.

> Is the global default easy to change?


It can be changed (globally) in default-web.xml.

>
> What will happen if this property is set in a WAR deployed to prior
> versions that do not support it?


It will be ignored.


Jan


>
> -Peter
>
> Jan Luehe wrote:
>
>> The property's name is "saveBytecode".
>>
>> It is documented in the domain's default-web.xml, and will be added
>> to the table of <jsp-config> properties in sun-web.xml in the
>> "Application
>> Deployment Guide" for 9.1 beta (review comments already sent to June
>> Parks),
>> as follows:
>>
>> Property: saveBytecode
>> Default: false, true for jspc
>> Description: Should generated byte code be saved to .class files?
>> This option is meaningful only when the Java compiler API, JSR 199
>> (available with, and used as the default on Java 6) is used for javac
>> compilations.
>>
>>
>> Jan
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>