[#JBPAPP-353] Upgrade JBoss Remoting version to 2.2.2.SP4

Description

Several issues are currently scheduled for Remoting 2.2.2.GA_CP01:

~~JBREM-811~~: Privileged Block to create Class Loader
    Designated a BLOCKER by Clebert Suconic

~~JBREM-813~~ ServletServerInvoker should return an exception instead of just an error message
    Arose in support case 18171 (https://na1.salesforce.com/50030000003iBdA)

JBREM-814 Logger in HTTPClientInvoker should be static (CLONE of ~~JBREM-750~~)
    Arose in support case 17553 (https://na1.salesforce.com/50030000003Prcj?srPos=0&srKp=500). This was supposed to go out in Remoting 2.2.2.GA, which ships with EAP 4.2.0.GA_CP01, but I accidentally left it out.

~~JBREM-815~~ allow user to set content-type for http responses (CLONE of ~~JBREM-653~~)
    Considered a possible BLOCKER by ESB group.

[ Permlink | « Hide ]

Rajesh Rajasekaran [22/Oct/07 03:15 PM]

Ron, i see that the version of remoting has been upgraded to 2.2.2.SP1.patch01-brew for 4.2.0.GA_CP02 and 4.3.0.GA EAP.
Is that the version you mean by "2.2.2.GA_CP01" above?

[ Permlink | « Hide ]

Ron Sigal [22/Oct/07 08:44 PM]

Actually, the plan has been to maintain two branches for the Remoting 2.2 releases.

Branch remoting_2_2_0_GA has given birth to the descendants of Remoting 2.2.0.GA, including 2.2.2.GA, which, I believe, shipped with EAP 4.2.0.GA_CP01, 2.2.2.SP1, which just shipped with AS 4.2.2.GA, and 2.2.2.SP2, which is targeted for AS 4.2.3 and 5.0.0.Beta. Other than going into EAP 4.2.0.GA_CP01, which was a special case, this branch is targeted for community AS releases.

A number of changes went into 2.2.2.GA, so I consider it the new "root" release for EAP 4.2.0. Accordingly, I created branch remoting_2_2_2_GA_CP for future CP releases for EAP 4.2.0 CP releases. The JBREM issues listed above have been applied to remoting_2_2_2_GA_CP.

Now, in the course of running some tests, the issue described in ~~JBREM-811~~ came up, and it was considered a BLOCKER, so Fernando created a patch release, 2.2.2.SP1.patch01-brew, as, I believe, a temporary measure. I still intend to tag the remoting_2_2_2_GA_CP branch as version remoting_2_2_2_GA_CP01, but I've been leaving it open in case any new issues come in before the freeze date. That's what I'm thinking of as Remoting 2.2.2.GA_CP01.

I understand that EAP 4.3.0 will be derived from EAP 4.2.0.GA_CP01, which includes Remoting 2.2.2.GA, but I would hope that at least Remoting 2.2.2.GA_CP01 could go into EAP 4.3.0, to get the fixes listed above.

I hope all this clarifies, rather than confuses.

[ Permlink | « Hide ]

Ron Sigal [22/Oct/07 08:47 PM]

By the way, what are the current freeze dates for EAP 4.3.0.GA and 4.2.0.GA_CP02?

[ Permlink | « Hide ]

Fernando Nasser [07/Nov/07 10:48 AM]

CP branch upgraded as well