| Summary: | EBWS WS-Addressing does not work | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jiri Pechanec <jpechane> | |
| Component: | JBossESB | Assignee: | Mark Little <mark.little> | |
| Status: | CLOSED NEXTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.3 IR4 | |||
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | http://jira.jboss.org/jira/browse/SOA-771 | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 778273 (view as bug list) | Environment: | ||
| Last Closed: | 2010-02-04 07:00:19 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
|
Description
Jiri Pechanec
2008-09-11 11:52:11 UTC
Link: Added: This issue depends JBESB-2025 This involves changes to the jbossesb schema so I would suggest that it be included in the FP rather than CP release Link: Added: This issue depends JBESB-2443 Link: Removed: This issue depends JBESB-2025 Link: Removed: This issue depends JBESB-2443 Link: Added: This issue depends JBESB-2025 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. This sounds like a slightly different issue, can we have a second JIRA with example/logs attached? Link: Added: This issue depends SOA-1847 Link: Removed: This issue depends SOA-1847 Link: Added: This issue is related to SOA-1847 Verified in ER8 |