[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2382) Fix JBossWS deployers processing

[Alessio Soldano (JIRA)]

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

Alessio Soldano updated JBWS-2382:
----------------------------------

    Fix Version/s: jbossws-native-3.2.0
                   jbossws-cxf-3.2.0
                   jbossws-metro-3.2.0
                       (was:  jbossws-native-3.1.1)


> Fix JBossWS deployers processing
> --------------------------------
>
>                 Key: JBWS-2382
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2382
>             Project: JBoss Web Services
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-metro, jbossws-native
>    Affects Versions:  jbossws-cxf-3.0.3, jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4
>            Reporter: Richard Opalka
>            Assignee: Richard Opalka
>             Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0
>
>
> In general all your processing in the deployers should just be based on metadata
> available to deployers or configuration on the deployers.
> You shouldn't be looking at any services.
> e.g. suppose the war had a dependency on an ejb from some other application
> then its not going to be started until that ejb exists regardless of when jbossweb.sar
> gets started.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira