[jboss-jira] [JBoss JIRA] (WFLY-3353) Multiple instance of the same ServletContainerInitializer can execute on single deployment

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved WFLY-3353.
----------------------------------

    Resolution: Rejected


If you include a SCI services entry in your deployment twice then it is a problem with the deployment. I don't think it is worth doing any checking for this, imho this is the expected behaviour.

> Multiple instance of the same ServletContainerInitializer can execute on single deployment
> ------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3353
>                 URL: https://issues.jboss.org/browse/WFLY-3353
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.1.0.CR2
>            Reporter: Bartosz Baranowski
>            Assignee: Stuart Douglas
>            Priority: Minor
>             Fix For: Awaiting Volunteers
>
>
> Not sure if this is a bug or requirement - though SCI JDOC does not mention anything that would justify same SCI class to execute more than once( neither does it deny it).
> Depending on AS version ServletContainerInitializers are handled bit differently( 7.x adds WsSci by default if jboss-web.xml has boolean flag for instance ), however all version allow to spawn SCI via jar services mechanism. Trick is that there is check on what and how is spawned. It is possible to spawn the same SCI twice and both will have a go. In case SCI does not behave or depends on servletContext.xxx methods return value, this can either make AS misbehave or throw NPE(from SCI) or other nasty exception. Example [1]
> [1] https://issues.jboss.org/browse/JBWEB-298



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)