Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes Complexity: Medium Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/1035273 project_key: SOA A Smooks XSLT transformation which worked in SOA-P 4.3 is not applied in SOA-P 5, due to a performance optimization inside Smooks between version 1.0 and 1.2. From Tom Fennelly: ---- The only change to Smooks (wrt XSLT) in the last few releases had been the addition of support for bypassing the Smooks filter. This is a performance enhancement and what it means is that if the only configuration in the smooks config is a single XSLT targeted at the root fragment (whole document), then the Smooks fragment filter is bypassed and the XSLT is applied directly. To prevent this from happening, configure the resource to disable the filter bypass by adding a param setting "enableFilterBypass" to "false" (<param name="enableFilterBypass">false</param>). ---- Could we please get this documented? Good places would be: - Smooks Guide, Chapter 4.2.3 XSL Templates - Release Notes, Chapter 10. Possible Issues Migrating to 5.0
Candidate for SOA 5.1.0
Usability and customer sat is important, thus this is made a blocker for SOA 5.1.
Labels: Added: Smooks_Guide migration_issue release_notes Complexity: Added: Medium Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Writer: Added: Darrin
Added to Smooks Guide as an <important> admonition (5.2.3. XSL Templates) and also to the release notes
Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: In JBoss Enterprise SOA Platform 5.0.0 or greater, the fragment filter is bypassed when the Smooks configuration only contains a single XSLT that is applied to the root fragment. In this situation the XSLT is applied directly. This is done for performance reasons. This behavior can be disabled by adding a parameter called enableFilterBypass and setting it to false. <param name="enableFilterBypass">false</param>