[ https://jira.jboss.org/browse/JBMETA-311?page=com.atlassian.jira.plugin.s... ] Richard Opalka updated JBMETA-311: ---------------------------------- Fix Version/s: jboss-metadata-common-2.0.0-alpha-21 (was: jboss-metadata-common-2.0.0-alpha-20) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBMETA-311?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated JBMETA-311: -------------------------------- Fix Version/s: jboss-metadata-common-2.0.0-alpha-23 (was: jboss-metadata-common-2.0.0-alpha-22) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBMETA-311?page=com.atlassian.jira.plugin.s... ] Richard Opalka edited comment on JBMETA-311 at 12/8/10 8:57 AM: ---------------------------------------------------------------- This is not easy task to do now. EJB3 client still uses these classes. There's the following dependency: --- In EJB3 client (as6/trunk/ejb3/src/main/java/org/jboss/ejb3/clientmodule/ClientENCInjectionContainer.java), there's registered org.jboss.injection.WebServiceRefHandler handler that delegates to AS metadata common to ServiceReferenceHandler that does AS MD -> WS UMDM -> Object factory translation. We need to get rid of this ugly dependency, but in order to do so, we need to provide some hook via JBossWS SPI for EJB3 project. This hook should be generic one, because AS MD cannot be referenced from JBossWS SPI. We should provide something like (first shoot): ObjectFactoryProvider<X> with the following method: ObjectFactory provide(URL vfsRoot, ClassLoader loader, X); This should be discussed inside JBossWS team and we should come with some good abstraction. was (Author: richard.opalka(a)jboss.com): This is not easy task to do no. EJB3 client still uses these classes. There's the following dependency: --- In EJB3 client (as6/trunk/ejb3/src/main/java/org/jboss/ejb3/clientmodule/ClientENCInjectionContainer.java), there's registered org.jboss.injection.WebServiceRefHandler handler that delegates to AS metadata common to ServiceReferenceHandler that does AS MD -> WS UMDM -> Object factory translation. We need to get rid of this ugly dependency, but in order to do so, we need to provide some hook via JBossWS SPI for EJB3 project. This hook should be generic one, because AS MD cannot be referenced from JBossWS SPI. We should provide something like (first shoot): ObjectFactoryProvider<X> with the following method: ObjectFactory provide(URL vfsRoot, ClassLoader loader, X); This should be discussed inside JBossWS team and we should come with some good abstraction. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira