[jboss-jira] [JBoss JIRA] Commented: (JBMETA-311) Remove ServiceReferenceHandler & VirtualFileAdaptor from jboss-metadata-common once switchboard is in place

[Richard Opalka (JIRA)]

    [ https://jira.jboss.org/browse/JBMETA-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568547#comment-12568547 ] 

Richard Opalka commented on JBMETA-311:
---------------------------------------

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.


> Remove ServiceReferenceHandler & VirtualFileAdaptor from jboss-metadata-common once switchboard is in place
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBMETA-311
>                 URL: https://jira.jboss.org/browse/JBMETA-311
>             Project: JBoss Metadata
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: common
>            Reporter: Richard Opalka
>            Assignee: Richard Opalka
>             Fix For: jboss-metadata-common-2.0.0-alpha-23
>
>


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