tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Köberl (JIRA) <j...@apache.org>
Subject [jira] Commented: (TAP5-745) Remove Woodstox-specific Stax implementation usage
Date Sat, 04 Jul 2009 14:42:47 GMT

    [ https://issues.apache.org/jira/browse/TAP5-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727243#action_12727243
] 

Christian Köberl commented on TAP5-745:
---------------------------------------

I'm sorry - i tried my patch only on Java6/Win (where it works - including tests).

I'm also investigating on this - this Stax stuff seems to be a real mess! The RI is not supporting
stuff that is defined in the standard (i.e XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES
set to true). 

I saw that Howard was already trying the same stuff:
http://jira.codehaus.org/browse/STAX-54

Hmm - let's see how this can be fixed.

Chris

> 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
>            Assignee: Robert Zeigler
>            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.


Mime
View raw message