[ https://issues.apache.org/jira/browse/TAP5-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720085#action_12720085 ]
Thiago H. de Paula Figueiredo commented on TAP5-745: ---------------------------------------------------- I didn't notice the patch and the solution to TAP5-713 will solve this issue, so I thought I could close this one as a duplicate. You're right about saying that a solution for TAP5-713 will take some time. I'm sorry. > Remove Woodstox-specific Stax implementation usage > -------------------------------------------------- > > Key: TAP5-745 > URL: https://issues.apache.org/jira/browse/TAP5-745 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core > Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1 > Reporter: Christian Köberl > Priority: Critical > Attachments: TAP5-745-5.1.0.5.patch > > > Tapestry uses some special extensions to StaX (out of Woodstox) in the > template parser. This leads to the problem that Tapestry will usually not run > on any application server because the appservers will use their own > implementation of Stax. > There is a workaround but a main stream web application framework should run > on JEE compatible web and application servers without tweaking. > The main problem is in > org.apache.tapestry5.internal.services.TemplateParserImpl.<init>(TemplateParserImpl.java:44). > Here, XMLInputFactory2 is asked for an instance - but XMLInputFactory2 does > not implement the method newInstance. This is delegated to XMLInputFactory. > So, the original XMLInputFactory is used - which returns the platform > implementation of Stax. > Workaround: > Add the system property below to Application Server (either via startup > script or admin console): > -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.