[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2728) Review JBossWS EJB integration

[Alessio Soldano (JIRA)]

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

Alessio Soldano updated JBWS-2728:
----------------------------------

    Fix Version/s: jbossws-cxf-4.0.0.Beta1
                   jbossws-native-4.0.0.Beta1
                       (was: jbossws-native-4.0)
                       (was:  jbossws-cxf-4.0)


> Review JBossWS EJB  integration
> -------------------------------
>
>                 Key: JBWS-2728
>                 URL: https://issues.jboss.org/browse/JBWS-2728
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-integration
>            Reporter: Richard Opalka
>            Assignee: Richard Opalka
>             Fix For: jbossws-cxf-4.0.0.Beta1, jbossws-native-4.0.0.Beta1
>
>
> We're depending on EJB real deployers.
> We need to investigate whether we really
> need to depend on these EJB deployers.
> Maybe using JBoss meta data would be sufficient?
> Some time ago also Adrian Brock wrote (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4059197#4059197):
> ---
> Even after this, there are lots of issues about whether webservices should be
> depending on things like ejb3 at all. It should certainly have access to its metadata for
> deployment purposes, which is one of the reasons we have started a
> "metadata" project so projects can share each others models. 
> ---
> The only possible problem that comes to my mind is
> whether we're able to implement JBossWS injections
> without depending on EJB real deployers?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira