Bug 778272 (SOA-771) - EBWS WS-Addressing does not work
Summary: EBWS WS-Addressing does not work
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-771
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 IR4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-11 11:52 UTC by Jiri Pechanec
Modified: 2010-02-04 07:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 778273 (view as bug list)
Environment:
Last Closed: 2010-02-04 07:00:19 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779462 0 high CLOSED OneWay EBWS with WS-Addressing support enabled throws exception on invocation 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-771 0 None None None Never

Internal Links: 779462

Description Jiri Pechanec 2008-09-11 11:52:11 UTC 
Date of First Response: 2009-01-30 05:23:14
project_key: SOA

See JBESB-2025
Comment 1 Kevin Conner 2008-09-11 14:24:07 UTC 
Link: Added: This issue depends JBESB-2025
Comment 2 Kevin Conner 2009-01-30 10:23:14 UTC 
This involves changes to the jbossesb schema so I would suggest that it be included in the FP rather than CP release
Comment 3 Tom Fennelly 2009-02-24 17:00:14 UTC 
Link: Added: This issue depends JBESB-2443
Comment 4 Tom Fennelly 2009-02-24 17:00:54 UTC 
Link: Removed: This issue depends JBESB-2025
Comment 5 Kevin Conner 2009-05-21 10:46:50 UTC 
Link: Removed: This issue depends JBESB-2443
Comment 6 Kevin Conner 2009-05-21 10:47:04 UTC 
Link: Added: This issue depends JBESB-2025
Comment 7 Jiri Pechanec 2009-12-21 08:42:45 UTC 
I tried to verify the issue and it is only partially fixed 
If I have two-way EBWS (both inXsd and outXsd present) then the invocation passes but If I one-way EBWS (only inXsd present) then the issue and exception reappears. 

The warning is present in both cases.
Comment 8 Kevin Conner 2010-01-13 15:28:03 UTC 
This sounds like a slightly different issue, can we have a second JIRA with example/logs attached?
Comment 9 Len DiMaggio 2010-01-22 16:39:51 UTC 
Link: Added: This issue depends SOA-1847
Comment 10 Kevin Conner 2010-02-03 10:48:18 UTC 
Link: Removed: This issue depends SOA-1847
Comment 11 Kevin Conner 2010-02-03 10:48:38 UTC 
Link: Added: This issue is related to SOA-1847
Comment 12 Jiri Pechanec 2010-02-04 07:00:19 UTC 
Verified in ER8
Note You need to log in before you can comment on or make changes to this bug.