[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2338) Review our SPI abstractions and interfaces

[Richard Opalka (JIRA)]

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

Richard Opalka updated JBWS-2338:
---------------------------------

    Description: 
We need to review our SPI classes/interfaces and provide proper integration layer for EJB and other potential consumers of our JBossWS  API.
There are many classes/interfaces, that shouldn't be visible to other JBossWS API consumers in JBossWS SPI.

  was:
Terminology:

DA = Deployment Aspect

Issues:

 * WSFRuntime isn't good abstraction and should be removed from our SPI because it doesn't integrate with JBossAS deployers architecture very well
   (it's issue is it depends on web container runtime which can be unavailable at AS start time (e.g. there can be multiple webservice archives in deploy directory that are started before web container is available)
 * We moved some servlet dependent DAs to servlet lifecycle init()/destroy() methods. The problem of it is it executes DAs for whole deployment, not just particular deployed endpoint.
   (IOW we execute the same DAs multiple times if there are more than one webservice endpoints in deployment. This need SPI review and repair)



> Review our SPI abstractions and interfaces
> ------------------------------------------
>
>                 Key: JBWS-2338
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2338
>             Project: JBoss Web Services
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-metro, jbossws-native
>    Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4
>            Reporter: Richard Opalka
>            Assignee: Richard Opalka
>             Fix For: jbossws-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3
>
>
> We need to review our SPI classes/interfaces and provide proper integration layer for EJB and other potential consumers of our JBossWS  API.
> There are many classes/interfaces, that shouldn't be visible to other JBossWS API consumers in JBossWS SPI.

-- 
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