11:56 a.m.
Wire version should be configurable per client or server
--------------------------------------------------------
Key: JBREM-764
URL: http://jira.jboss.com/jira/browse/JBREM-764
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Currently org.jboss.remoting.Version looks to the system property
"jboss.remoting.version" to determine the value to return for
Version.getDefaultVersion(), and the transports refer to Version.getDefaultVersion().
This means that all clients and servers in a JVM use the same version.
It would be preferable to allow the wire version to configurable as a parameter to each
client and server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-764) Wire version should be configurable per client or server
[ http://jira.jboss.com/jira/browse/JBREM-764?page=all ]
Ron Sigal updated JBREM-764:
----------------------------
Fix Version/s: 2.4.0.CR1 (Pinto)
(was: 2.4.0.Beta1 (Pinto))
Wire version should be configurable per client or server
--------------------------------------------------------
Key: JBREM-764
URL: http://jira.jboss.com/jira/browse/JBREM-764
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.CR1 (Pinto)
Currently org.jboss.remoting.Version looks to the system property
"jboss.remoting.version" to determine the value to return for
Version.getDefaultVersion(), and the transports refer to Version.getDefaultVersion().
This means that all clients and servers in a JVM use the same version.
It would be preferable to allow the wire version to configurable as a parameter to each
client and server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-764) Wire version should be configurable per client or server
[ http://jira.jboss.com/jira/browse/JBREM-764?page=comments#action_12401532 ]
Ron Sigal commented on JBREM-764:
---------------------------------
1. Added REMOTING_VERSION (actual value "remotingVersion") to
org.jboss.remoting.Remoting
2. Added version variable to org.jboss.remoting.AbstractInvoker. Constructor looks first
in configuration map for value of Remoting.REMOTING_VERSION, and if
Remoting.REMOTING_VERSION is not present, it gets
org.jboss.remoting.Version.getDefaultVersion().
3. The transports now call AbstractInvoker.getVersion() instead of
Version.getDefaultVersion().
Unit tests:
* org.jboss.test.remoting.version.BisocketConfigurableVersionTestCase
* org.jboss.test.remoting.version.HttpConfigurableVersionTestCase
* org.jboss.test.remoting.version.RMIConfigurableVersionTestCase
* org.jboss.test.remoting.version.SocketConfigurableVersionTestCase
Waiting for results in hudson.
Wire version should be configurable per client or server
--------------------------------------------------------
Key: JBREM-764
URL: http://jira.jboss.com/jira/browse/JBREM-764
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.CR1 (Pinto)
Currently org.jboss.remoting.Version looks to the system property
"jboss.remoting.version" to determine the value to return for
Version.getDefaultVersion(), and the transports refer to Version.getDefaultVersion().
This means that all clients and servers in a JVM use the same version.
It would be preferable to allow the wire version to configurable as a parameter to each
client and server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-764) Wire version should be configurable per client or server
[ http://jira.jboss.com/jira/browse/JBREM-764?page=all ]
Ron Sigal closed JBREM-764.
---------------------------
Resolution: Done
Tests passing in hudson.
Wire version should be configurable per client or server
--------------------------------------------------------
Key: JBREM-764
URL: http://jira.jboss.com/jira/browse/JBREM-764
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.CR1 (Pinto)
Currently org.jboss.remoting.Version looks to the system property
"jboss.remoting.version" to determine the value to return for
Version.getDefaultVersion(), and the transports refer to Version.getDefaultVersion().
This means that all clients and servers in a JVM use the same version.
It would be preferable to allow the wire version to configurable as a parameter to each
client and server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6154
days inactive
6403
days old
3 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)