Re: [jetty-dev] maven jetty 8 slow startup

[Jan Bartel <janb@xxxxxxxxxxx>]

Hi Federico,

Ah. That's because we supported the ability to force scanning to happen by the
WebAppContext.setConfigurationDiscovered(boolean) method - its actually set to
"true" by default. It's true by default because its a reasonable default with
servlet 3.0 (which has a lot of support for annotations etc). However, it DOES
lead to some unexpected results like you experienced.

I shall have to have a think about the best way to take the surprise out.

thanks
Jan

On 9 September 2011 19:12, Federico Fissore <federico@xxxxxxxxxxx> wrote:
> Jan Bartel, il 09/09/2011 07:34, ha scritto:
>>
>> Federico,
>>
>> If I understand correctly, you think you declared your web.xml to be
>> 2.5 and metadata complete,
>> yet you think that annotation scanning still occurred with jetty-8 maven
>> plugin?
>
>
> I'm sorry, no, I was referring to the previous situation
>
> Now, with an updated web.xml spec declaring version 2.5 and
> metadata-complete=true (as the webdefault.xml does) everything is working
> correctly ( = as before, since we are not using any new servlet feature)
>
> My point was about the previous state of our web.xml. It was declared 2.4
> and my expectation (now that I know of the metadata-complete attr) was that
> is some class scanning is useful since a version of the spec, webapps
> declared belonging to a previous version should not scan any class
>
> best regards
>
> federico
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>