Red Hat Bugzilla – Bug 779149
Backwards incompatibility with HttpResponse
Last modified: 2010-03-01 00:13:26 EST
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-10-23 11:12:16
Link: Added: This issue depends JBESB-2903
The compatibility issue is the result of a deliberate decision, taken when implementing the new HTTP features. We were allowed leeway in this as it was feeding in to a new SOA 5 stream.
Ok. In that case, this should be documented in some paper on migrating from SOA-P 4 to 5.
Needs to be mentioned in any upgrade docs
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]
Can you please tell us what has changed as we are preparing the release documents now?
Link: Added: This issue depends JBESB-2953
Looks like nothing needs to be documented as the issue was later fixed in a separate issue, JBESB-2953.
Correction, the signature of the message has been fixed but the implementation is incorrect.
Link: Added: This issue is related to JBESB-3164
The documentation should contain something like the following
All references to org.jboss.soa.esb.actions.routing.http.HttpResponse and org.jboss.soa.esb.actions.routing.http.HttpHeader must be changed to refer to the new implementations, org.jboss.soa.esb.http.HttpResponse and org.jboss.soa.esb.http.HttpHeader. In addition invocations of the HttpResponse.getHeaders() method should be replaced with invocations of HttpResponse.getHttpHeaders().
I have drafted this for the Migration section of the Release Notes:
Change all references to org.jboss.soa.esb.actions.routing.http.HttpResponse
and org.jboss.soa.esb.actions.routing.http.HttpHeader to refer to
org.jboss.soa.esb.http.HttpResponse and org.jboss.soa.esb.http.HttpHeader,
respectively. Also, replace invocations of the HttpResponse.getHeaders() method with
Can you please provide a little bit more detail about this issue for the release notes. I documented it as per the above but we really need a bit more information:
1. What has changed and where
2. The impact/result of these changes.
Sorry this took so long to reply.
SOA 5 introduced a new HTTP gateway based around servlets rather than JBoss Remoting and, as part of this work, we decided to consolidate the use of Http information across those classes which produced and/or consumed it. Previously this had involved the HttpRouter class, producing this information using the classes within its local package. In order to consolidate these classes they were moved into a more appropriate package, however the intention had been to make this change backwardly compatible and then deprecate those classes within org.jboss.soa.esb.actions.routing.http. Unfortunately this was not successful, leading to the creation of JBESB-3164.
Is this sufficient background for your purpose?
Updated Migration issue in SOA 5.0.0 Release Notes
HttpResponse is not backwards compatible
The HttpResponse class in 5.0 is not backwards compatible with previous versions because of changes made to unify the ESB HTTP classes. This was done as a part of the new servlet-based HTTP gateway.
Applications and services that use HttpResponse will have to be updated before they can be deployed on JBoss Enterprise SOA Platform 5.0. The changes required are summarized in the table below.
Pre-5.0.0 code 5.0.0 code