Bug 780693 (SOA-3142) - WSDL sequencer does not sequence document correctly.
Summary: WSDL sequencer does not sequence document correctly.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3142
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-30 16:15 UTC by Boris Belovic
Modified: 2011-10-04 09:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-04 09:27:49 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 Issue Tracker SOA-3142 0 Major Closed WSDL sequencer does not sequence document correctly. 2013-01-03 21:30:41 UTC

Description Boris Belovic 2011-06-30 16:15:32 UTC 
project_key: SOA

This affect version SOA-P 5.2.0 DEV1, not yet added to JIRA, so I left Affect version field blank. For details see MODE-1207.
Comment 1 Boris Belovic 2011-06-30 16:15:53 UTC 
Link: Added: This issue is related to MODE-1207
Comment 2 Randall Hauch 2011-07-27 16:07:44 UTC 
Some additional logging messages were added to ModeShape (both 'master' and '2.5.x' branches) to hopefully capture the problems with the sequencer. The problematic file works in our integration and unit tests, so it has something to do with running within the SOA kit. Perhaps there are problems resolving XSDs within the SOA environment that we don't have within our environment? Or, perhaps there's a clash of library versions in this sequencer's dependencies?

Anyway, it needs to be retested with the next dev build.
Comment 4 David Le Sage 2011-08-31 05:28:51 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Comment 5 Boris Belovic 2011-10-04 09:27:49 UTC 
This issue has been verified with ER4 build.

For verification I used my own reproducer (see MODE-1207), the issue is fixed now and WSDL sequencer is working correctly.
Note You need to log in before you can comment on or make changes to this bug.