[ https://jira.jboss.org/jira/browse/JBREM-904?page=com.atlassian.jira.plug... ]
David Lloyd updated JBREM-904:
------------------------------
Fix Version/s: 3.1.0.GA
(was: 3.0.0.Beta1)
> Remoting 1/2 protocol compatibility
> -----------------------------------
>
> Key: JBREM-904
> URL: https://jira.jboss.org/jira/browse/JBREM-904
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: David Lloyd
> Fix For: 3.1.0.GA
>
>
> A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered.
> Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports.
--
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
Assure version compatibility with earlier versions of Remoting
---------------------------------------------------------------
Key: JBREM-1034
URL: https://jira.jboss.org/jira/browse/JBREM-1034
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.0.GA (Flounder)
--
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
Upgrade jars to versions in JBossAS 5.0.0.CR2
---------------------------------------------
Key: JBREM-1033
URL: https://jira.jboss.org/jira/browse/JBREM-1033
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.4.0.SP2
As JBREM-1032 "Upgrade to the latest jboss-common-core 2.2.8.GA", Remoting unit tests should run with the jars that will ship with JBossAS 5.0.0. The following jars need to be upgraded:
* dom4j.jar
* jnpserver.jar
* jboss-jmx.jar
* jbossweb.jar
* concurrent.jar
* servlet-api.jar
Also, jboss-j2se.jar needs to be added since some classes have been removed from jboss-jmx.jar.
--
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
Upgrade to the latest jboss-common-core 2.2.8.GA
------------------------------------------------
Key: JBREM-1032
URL: https://jira.jboss.org/jira/browse/JBREM-1032
Project: JBoss Remoting
Issue Type: Thirdparty Change
Security Level: Public (Everyone can see)
Reporter: Dimitris Andreadis
Fix For: 2.4.0.SP2
See the discussion in the jboss-dev list
--
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
JavaSerializationManager should clear ObjectOutputStream internal tables
------------------------------------------------------------------------
Key: JBREM-1028
URL: https://jira.jboss.org/jira/browse/JBREM-1028
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.SP1 (Pinto)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.4.0.SP2
In changing from socket transport wire format 1 to wire format 2 (and 22), we eliminated the last call to ObjectOutputStream.flush(). It turns out that the internal ObjectOutputSteam tables can hold onto objects and cause leaks. See EJBTHREE-1442 "Ejb3ClassloaderLeakUnitTestCase failures in AS testsuite" and the related forum discussion for more information.
--
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
[ https://jira.jboss.org/jira/browse/JBREM-904?page=com.atlassian.jira.plug... ]
David Lloyd updated JBREM-904:
------------------------------
Fix Version/s: 3.0.0.Beta1
(was: 3.0.0-M3)
> Remoting 1/2 protocol compatibility
> -----------------------------------
>
> Key: JBREM-904
> URL: https://jira.jboss.org/jira/browse/JBREM-904
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: David Lloyd
> Fix For: 3.0.0.Beta1
>
>
> A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered.
> Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports.
--
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