[ https://jira.jboss.org/jira/browse/JBWS-2728?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2728: --------------------------------- Description: 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#...): --- 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? was: 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 will could sufficient? Some time ago also Adrian Brock wrote (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=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. - 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

[ https://jira.jboss.org/jira/browse/JBWS-2728?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2728: --------------------------------- Fix Version/s: jbossws-native-3.3.1 jbossws-metro-3.3.1 jbossws-cxf-3.3.1 (was: jbossws-cxf-3.3.0) (was: jbossws-metro-3.3.0) (was: jbossws-native-3.3.0) -- 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

[ https://issues.jboss.org/browse/JBWS-2728?page=com.atlassian.jira.plugin.... ] 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) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-2728?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-2728: --------------------------------------- Richard, if you have a minute, consider updating the description for this jira, which would be considered out-of-date judging on that. This jira can of course stay to collect changes we're going to need as soon as the AS7 EJB integration is completely and you can go on with the EJB3-WS work. Thanks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira