Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [servlet-dev] @Priority for ServletContainerInitializer
Hi,

Obviously there should be a convention for non-annotated ServletContainerInitializers. 

Interceptors has defined ranges for the priorities, which could be used as a base. 


Assuming the container is able to distinguish between discovering its own provided ServletContainerInitializers and those of 3rd parties (typically, those in WEB-INF/lib), the container's own ServletContainerInitializers can be placed conceptually at a priority between PLATFORM_BEFORE up until LIBRARY_BEFORE, while third party non-annotated would be assigned priority PLATFORM_AFTER.

Explicitly annotated ServletContainerInitializers would execute at their given priority.

Kind regards,
Arjan Tijms





On Mon, May 18, 2020 at 5:33 PM Joakim Erdfelt <joakim.erdfelt@xxxxxxxxx> wrote:
How does this work when there are container provided ServletContainerInitializers and even 3rd party ServletContainerInitializers?
How do you ensure a @Priority annotated SCI gets executed before (or after) one of those other SCIs?

- Joakim

On Mon, May 18, 2020 at 10:20 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

Just wondering, what about supporting the @Priority annotation on a ServletContainerInitializer class to help ordering the execution order of these?

Thoughts?

Kind regards,
Arjan Tijms
_______________________________________________
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev
_______________________________________________
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev

Back to the top