Bug 779195 (SOA-1589)

Summary:	Document there are no guarantees that the format on contents of EPR will remain the same
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Taro Yasuma <tyasuma>
Component:	Documentation	Assignee:	David Le Sage <dlesage>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP02	CC:	dlesage
Target Milestone:	---
Target Release:	4.3 CP04 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1589
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-26 18:12:24 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Deadline:	2010-03-08

Description Taro Yasuma 2009-11-11 10:49:32 UTC

Date of First Response: 2010-02-25 14:05:27
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/356581
project_key: SOA

message.getHeader().getCall().getTo().getAddr().getAddress()
returns a different format after CP02 release

For example)
GA, CP01:
jms://soa01:1200/queue/myRequestQueue
CP02:
jms:soa01:1200#queue/myRequestQueue

While the API is public, the contents of the EPR are implementation 
dependent and should be treated as opaque.  
There are no guarantees that the format will remain the same.

This is a request to describe above notice on ESB documentation.

Comment 1 Taro Yasuma 2009-11-11 10:53:58 UTC

Link: Added: This issue depends JBESB-2971

Comment 2 Taro Yasuma 2009-11-11 10:54:30 UTC

Link: Added: This issue related JBESB-2502

Comment 3 Anne-Louise Tangring 2010-02-25 19:05:27 UTC

Approved for SOA 4.3 CP03.

Comment 4 David Le Sage 2010-02-26 00:26:40 UTC

Please review the following draft text that I have added to the Migration section of the Release Notes:


2.2.1. Format of End Point Reference Contents Has Changed

The contents of message.getHeader().getCall().getTo().getAddr().getAddress() are
now returned in a different format than that in the 4.3GA and 4.3.CP01 releases. Previously, the format
was:

jms://soa01:1200/queue/myRequestQueue

but now it is:

jms:soa01:1200#queue/myRequestQueue

Note that, whilst the API is public, the contents of the end-point reference are implementation-specific.
Always regard them as opaque because there is no guarantee the format will remain the same.

Comment 5 David Le Sage 2010-03-16 22:14:21 UTC

Taro, I have actually reworded it slightly in order to make it read better.  The new wording is below but can you also please give a little information about who was modifying the format and why?  Was it a particular customer?  Many thanks.





2.2.1. Format of End Point Reference Contents Has Changed 

The contents of message.getHeader().getCall().getTo().getAddr().getAddress() are 
now returned in a different format than that in the 4.3GA and 4.3.CP01 releases. Previously, the format 
was in the form of: 

jms://soa01:1200/queue/myRequestQueue 

but now it is: 

jms:soa01:1200#queue/myRequestQueue 

Users should not modify End-Point Reference formats directly 
    because they are specific to implementations of the API. There is no
    guarantee the format will remain the same for them.

Comment 6 Taro Yasuma 2010-03-18 01:02:00 UTC

David, the fix on JBESB-2502 affected the behavior and per Kevin, this is as a consequence of the fix and is necessary to support different JMS providers. So not for a particular customer.

Comment 7 David Le Sage 2010-03-18 01:06:34 UTC

Thanks for clarifying that for me, Taro.  Much appreciated.