8:16 a.m.
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.2.2.SP12, 2.5.0.SP3 (Flounder)
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
9:48 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1102:
-----------------------------
Attachment: jboss-remoting.jar
Attaching a jboss-remoting.jar (preview of 2.2.2.SP12) with the fix in place.
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.2.2.SP12, 2.5.0.SP3 (Flounder)
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
8:46 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
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
7:17 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal closed JBREM-1102.
----------------------------
Resolution: Done
Changes have also been committed to the 2.x branch. The servlet unit tests have been run
with AS 5.0.
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
7:42 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1102:
----------------------------------
The tests pass in Hudson.
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
12:02 a.m.
New subject: [JBoss JIRA] Reopened: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal reopened JBREM-1102:
------------------------------
This feature should be optional, and the original behavior should remain the default.
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.1 (Flounder), 2.2.3
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
6:17 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1102:
----------------------------------
Created a new parameter, org.jboss.remoting.Remoting.PASS_CONFIG_MAP_TO_MARSHAL_FACTORY
(actual value "passConfigMapToMarshalFactory"), which needs to be set to
"true" to have the configuration map passed to marshalFactory. Otherwise, the
original behavior holds.
Tests: Several methods are added to the existing tests to account for the three
circumstances: (1) there is no extra configuration; (2)
"passConfigMapToMarshalFactory" is set to "false"; (3)
"passConfigMapToMarshalFactory" is set to true.
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.1 (Flounder), 2.2.3
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
1:59 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1102:
----------------------------------
For servlet transport, org.jboss.test.remoting.transport.servlet.marshal is not broken
into org.jboss.test.remoting.transport.servlet.marshal.config and
org.jboss.test.remoting.transport.servlet.marshal.noconfig.
Remoting Guide updated.
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.1 (Flounder), 2.2.3
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
2:51 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1102:
-----------------------------
Fix Version/s: 2.5.2 (Flounder)
Affects Version/s: 2.5.1 (Flounder)
(was: 2.5.0.SP2 (Flounder) )
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.2.2.SP11, 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3, 2.5.2 (Flounder)
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
2:51 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1102:
-----------------------------
Fix Version/s: (was: 2.5.1 (Flounder))
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.2.2.SP11, 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3, 2.5.2 (Flounder)
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
2:51 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1102:
----------------------------------
Applied changes to 2.x branch.
waiting for results in hudson.
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.2.2.SP11, 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3, 2.5.2 (Flounder)
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
10:40 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-1102) Make configuration map available to MarshalFactory
[
https://jira.jboss.org/jira/browse/JBREM-1102?page=com.atlassian.jira.plu...
]
Ron Sigal closed JBREM-1102.
----------------------------
Resolution: Done
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.2.2.SP11, 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3, 2.5.2 (Flounder)
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
5462
days inactive
5549
days old
jboss-remoting-issues@lists.jboss.org
11 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)