Which jsp jars do you have on the classpath? IIRC with jetty-9.2.x you
could choose between using glassfish jsp or apache jsp.


I don't think jetty sets the "keepgenerated" init param at all in
webdefault.xml - check to make sure you're not applying an override-web.xml
file or jetty-web.xml.

Jan

On 17 November 2015 at 19:54, erars+jonathan.cook <
[email protected]> wrote:

> Any further thoughts on this? I could patch the source I guess to print
> out what the values actually have?
>
> Thanks
>
>
>
> On 13.11.2015 20:46, Jonathan Cook wrote:
>
> Hi,
>
> Thanks for the reply. We aren't overriding this file in anyway so it
> should be what is inside the jar right which is used? f that is the case,
> fork has a value of false so why would we see invalid value being reported.
> Likewise keepgenerated isn't configured in that file so I would expect it
> to be null?
>
> Thanks for any more pointers.
>
> Jon
>
> On 13/11/2015 20:19, Joakim Erdfelt wrote:
>
> Those values arrive via the jsp servlet configuration.
> That's just a webdefault.xml file found configured in the
> WebAppContext.setDefaultsDescriptor()
> Example of the webdefault.xml ..
>
> https://github.com/eclipse/jetty.project/blob/jetty-9.2.12.v20150709/jetty-webapp/src/main/config/etc/webdefault.xml#L200-L308
>
> Joakim Erdfelt / [email protected]
>
> On Fri, Nov 13, 2015 at 9:47 AM, Jonathan Cook <
> [email protected]> wrote:
>
>> Hi,
>>
>> I'm using an embedded instance of Jetty Server with version 9.2.12 and
>> recently upgraded from an old version 6. Everything seems to be behaving as
>> expected but I see some warnings when starting the server:
>>
>> WARNING: Warning: Invalid value for the initParam keepgenerated. Will use 
>> the default value of "false"
>> WARNING: Warning: Invalid value for the initParam fork. Will use the default 
>> value of "true"
>>
>>
>> These can eventually be traced down to the class
>> EmbeddedServletOptions.java and the getBoolean method. But what is most
>> puzzling is that this method implies that the values have some value other
>> than null, true or false. If I set the init parameter values explicitly it
>> makes no difference and if I print out the contents of the params before
>> the server starts it either gives me the values I have specified (when set)
>> or null (when not set) which somehow must be lost or ignored later in the
>> chain.
>>
>> How can I make these warnings go away and ensure the parameters are
>> either set or not set.
>>
>> Thank you for any help.
>> Jonathan
>>
>>
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
>
> _______________________________________________
> jetty-users mailing [email protected]
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visithttps://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
>
>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>



-- 
Jan Bartel <[email protected]>
www.webtide.com
*Expert assistance from the creators of Jetty and CometD*
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to