Bug 1045499 - XSLT transformation ignores xml tags
Summary: XSLT transformation ignores xml tags
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
Target Milestone: CR1
: ---
Assignee: Keith Babo
QA Contact: Jiri Pechanec
Depends On:
TreeView+ depends on / blocked
Reported: 2013-12-20 15:24 UTC by Jochen Cordes
Modified: 2014-06-16 23:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Example application (12.52 KB, application/zip)
2013-12-20 15:24 UTC, Jochen Cordes
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-1920 0 Major Closed SOAP MessageComposer creates DOMSource without Document element 2014-06-30 13:43:37 UTC

Description Jochen Cordes 2013-12-20 15:24:51 UTC
Created attachment 839624 [details]
Example application

Description of problem:

It seems that the camel xslt processor ignores the transformation and is just outputting the input, minus the xml tags..

The camel route and transformation works fine when deployed on SY 0.7.0. I also tested on vanilla camel and also here the transformation works as expected.

See hereunder for the route definition, xsl stylesheet, input xml and expected and obtained result. Attached also a sy project that can be deployed on FSW. It also contains a soapui project file to test this.

Is this a known issue? Any workaround? 

Version-Release number of selected component (if applicable):

JBoss Fuse 6 Beta (ER 6)

How reproducible:


Steps to Reproduce:

Actual results:

Expected results:

Additional info:

The proposed workaround is the following:

            .log("Received message for 'ActivationPortType' : ${body}")
            .log("After transformation : ${body}");

The convertBodyTo above will take the DOM issue out of the equation and allows the XSLT component to both parse and translate using XML libraries available to it.

Comment 2 Keith Babo 2013-12-20 18:17:59 UTC
Thanks for filing the BZ. This issue appears to be limited to Camel routing services which are coupled with a SOAP binding.  There is a workaround for the issue: simply convert the payload on entry to the Camel route to something that will have to be re-parsed within the route, e.g.

           .log("Before transformation : ${body}")
           .log("After transformation : ${body}");

Comment 3 Keith Babo 2013-12-20 23:28:53 UTC
I confirmed that this issue is still present in the ER8 build and is also present in the community 1.1.0.Final build, so it's not something introduced as a part of productization.

Comment 4 Jiri Pechanec 2014-01-15 09:57:12 UTC
Verified in CR1

Comment 5 JBoss JIRA Server 2014-06-16 23:53:27 UTC
Keith Babo <kbabo@redhat.com> updated the status of jira SWITCHYARD-1920 to Closed

Note You need to log in before you can comment on or make changes to this bug.