Re: [servlet-dev] @Priority for ServletContainerInitializer

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

On Tue, May 19, 2020 at 2:59 AM Stuart Douglas <sdouglas@xxxxxxxxxx> wrote:

Do you have a specific use case in mind for this?

In general I've come across the need multiple times over the year, but as a (very) specific use case I have an initialiser that runs before the Weld one and sets up data used by Soteria:

https://github.com/piranhacloud/piranha/blob/master/security/jakarta/src/main/java/cloud/piranha/security/jakarta/JakartaSecurityAllInitializer.java#L62

When the CDI extension provided by Soteria is executed following the Weld init, this data is used:

https://github.com/eclipse-ee4j/soteria/blob/master/impl/src/main/java/org/glassfish/soteria/cdi/CdiExtension.java#L202

Of course this specific example only works when you know CDI is being initialised by a ServletContainerInitializer, but it helps for environments where this is indeed the case.

Kind regards,

Arjan Tijms

 

Stuart

On Tue, 19 May 2020 at 01:29, 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