Bug 780192 (SOA-2571) - XML sequencer doesn't work correctly
Summary: XML sequencer doesn't work correctly
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2571
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0.ER5
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 14:23 UTC by Boris Belovic
Modified: 2010-12-20 14:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-20 14:20:22 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-2571 0 None None None Never

Description Boris Belovic 2010-11-11 14:23:17 UTC 
project_key: SOA

Sequencing of XML files results in creation of two nodes under sequenced/xml node, but only one node should have been created.

Example:

publishing XML file into: /files/test.xml results in sequenced/xml/test.xml and sequenced/xml/test.xml[2] , but only sequenced/xml/test.xml is expected.
Comment 1 Boris Belovic 2010-11-11 14:23:37 UTC 
Link: Added: This issue is related to MODE-1013
Comment 2 Randall Hauch 2010-12-02 18:55:16 UTC 
I just marked MODE-1013 as 'resolved', since there's no other work to be done and the test cases (which had duplicated the problem) now show that the sequencer works correctly. If this change did not fix the problem for SOA-P, please reopen MODE-1013 or log a new issue.
Comment 3 Van Halbert 2010-12-02 19:02:00 UTC 
Changes have been committed to the 2.2.x product branch.   This fix should be in the ER5 release (as of 12/2 the build hasn't been started).
Comment 4 Boris Belovic 2010-12-20 14:20:22 UTC 
Verified in SOA-P ER5 build. XMLSequencer now produces only one node with jcr:primaryType property set to modexml:document.
Note You need to log in before you can comment on or make changes to this bug.