[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1102) Make configuration map available to MarshalFactory

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458707#action_12458707 ] 

Ron Sigal commented on JBREM-1102:
----------------------------------

New methods have been added to MarshalFactory:

   public static Marshaller getMarshaller(InvokerLocator locator, ClassLoader classLoader, Map config)

and

   public static UnMarshaller getUnMarshaller(InvokerLocator locator, ClassLoader classLoader, Map config)

and all references to the original versions have been changed to refer to these new methods.

Unit tests:

  org.jboss.test.remoting.marshall.config.BisocketConfigurationMapTestCase
  org.jboss.test.remoting.marshall.config.HttpConfigurationMapTestCase
  org.jboss.test.remoting.marshall.config.RMIConfigurationMapTestCase
  org.jboss.test.remoting.marshall.config.SocketConfigurationMapTestCase
  org.jboss.test.remoting.transport.servlet.marshal.ServletConfigurationMapTestClient

The latter has been tested with EAP 4.3.0.GA_CP03.

These changes have been applied to the 2.2 branch.

> Make configuration map available to MarshalFactory
> --------------------------------------------------
>
>                 Key: JBREM-1102
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1102
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12
>
>         Attachments: jboss-remoting.jar
>
>
> The methods
>       public static Marshaller getMarshaller(InvokerLocator locator, ClassLoader classLoader)
> and
>       public static UnMarshaller getUnMarshaller(InvokerLocator locator, ClassLoader classLoader)
> in org.jboss.remoting.marshal.MarshalFactory get a marshaller or unmarshaller, respectively, from either a "datatype" parameter or from fully qualified names of the marshaller and unmarshaller classes.  However, they don't have access to parameters configured by way of the configuration map.
> This is a problem for JBossESB, in particular, org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener, which creates an org.jboss.remoting.transport.Connector from parameters configured in a jboss-esb.xml file.

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