Bug 781101 (SOA-3593) - Make XsltAction handle org.w3c.dom.Node or Document
Summary: Make XsltAction handle org.w3c.dom.Node or Document
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: SOA-3593
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.2.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: CR1
: 5.3.0 GA
Assignee: tcunning
QA Contact: Jiri Pechanec
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-15 20:37 UTC by tcunning
Modified: 2014-10-15 17:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
XsltAction is unable to handle org.w3c.dom.Node or Document objects. This makes it difficult for users to chain XsltActions.
Clone Of:
Environment:
Last Closed: 2014-10-15 17:26:15 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)
Failing XSLT chaining (11.57 KB, application/zip)
2012-06-13 10:39 UTC, Jiri Pechanec 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-3708 0 Major Closed XsltAction cannot handle org.w3c.dom.Document 2013-02-21 02:27:08 UTC
Red Hat Issue Tracker SOA-3593 0 Major Closed Make XsltAction handle org.w3c.dom.Node or Document 2013-02-21 02:27:08 UTC

Description tcunning 2011-11-15 20:37:47 UTC 
project_key: SOA

XsltAction cannot handle Document or Node, making it hard to chain XsltActions.   See related but JBESB-3708.
Comment 1 tcunning 2011-11-15 20:38:01 UTC 
Link: Added: This issue is related to JBESB-3708
Comment 2 Suz 2012-06-13 03:01:49 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
XsltAction is unable to handle org.w3c.dom.Node or Document objects. This makes it difficult for users to chain XsltActions.
Comment 3 Jiri Pechanec 2012-06-13 10:38:15 UTC 
The code is not wokring properly - see attached example. If STRING is used between actions then it works as expected. If DOM is used, the second transformation is not properly applied.
Comment 4 Jiri Pechanec 2012-06-13 10:39:27 UTC 
Created attachment 591435 [details]
Failing XSLT chaining
Comment 5 Jiri Pechanec 2012-07-12 08:29:50 UTC 
The chaining is still failing
Comment 6 JBoss JIRA Server 2012-07-13 16:15:04 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3708 to Resolved
Comment 7 JBoss JIRA Server 2012-07-13 16:15:04 UTC 
Tom Cunningham <tcunning> made a comment on jira JBESB-3708

bananastand:rosetta tcunning$ svn commit
Sending        rosetta/src/org/jboss/soa/esb/actions/transformation/xslt/ResultFactory.java
Sending        rosetta/src/org/jboss/soa/esb/actions/transformation/xslt/SourceFactory.java
Transmitting file data ..
Committed revision 38139.
bananastand:rosetta tcunning$
Comment 8 JBoss JIRA Server 2012-07-13 16:15:10 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3708 to Closed
Comment 9 JBoss JIRA Server 2012-07-13 16:15:34 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3708 to Reopened
Comment 10 JBoss JIRA Server 2012-07-13 16:15:53 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3708 to Resolved
Comment 11 JBoss JIRA Server 2012-07-13 16:15:56 UTC 
Tom Cunningham <tcunning> updated the status of jira JBESB-3708 to Closed
Comment 12 Ryan Zhang 2012-07-20 06:35:07 UTC 
Please verify this issue on 5.3.0 CR1.
Comment 13 Jiri Pechanec 2012-07-23 11:17:32 UTC 
Verified in CR1
Note You need to log in before you can comment on or make changes to this bug.