Bug 780828 (SOA-3278) - Riftsaw dynpartner quickstart sample not using dynamically assigned endpoint reference
Summary: Riftsaw dynpartner quickstart sample not using dynamically assigned endpoint ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3278
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Examples
Version: 5.2.0.ER2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER4
Assignee: Gary Brown
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-18 12:10 UTC by Gary Brown
Modified: 2011-10-07 09:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-07 09:25:46 UTC
Type: Bug

Attachments (Terms of Use)
soa3278.patch (1.61 KB, text/plain)
2011-08-18 12:13 UTC, Gary Brown 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RIFTSAW-422 0 None None None Never
Red Hat Issue Tracker SOA-3278 0 None None None Never

Description Gary Brown 2011-08-18 12:10:01 UTC 
project_key: SOA

The dynpartner quickstart example currently uses the peer to peer comms between the processes, and therefore does not reference the assigned EPR on the partnerlink.

When the peer to peer comms is disabled, so that it invokes the 'responder' process through the WS stack, it shows up that one of the assigned references was not specified correctly.
Comment 1 Gary Brown 2011-08-18 12:10:56 UTC 
Link: Added: This issue relates to RIFTSAW-422
Comment 2 Gary Brown 2011-08-18 12:13:29 UTC 
Attachment: Added: soa3278.patch
Comment 3 Gary Brown 2011-08-18 12:50:31 UTC 
Has been fixed in riftsaw 2.3.x branch so awaiting inclusion in next SOA-P build.
Comment 4 David Le Sage 2011-08-25 23:13:07 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Comment 5 Marek Baluch 2011-10-07 09:25:46 UTC 
Verified in ER4.
Note You need to log in before you can comment on or make changes to this bug.