[
https://issues.apache.org/jira/browse/TAP5-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729518#action_12729518
]
Tatu Saloranta edited comment on TAP5-713 at 7/9/09 9:57 PM:
-------------------------------------------------------------
Woodstox does not use FactoryFinder for anything. Only thing that does is the
Stax API itself.
Nothing to do with Woodstox; same would apply to JDK6-bundled Stax
implementation (Sun Sjsxp). Ditto for OSGi: Stax/SAX/JAXP all use introspection
mechanism that does not work well with OSGi. This is the same for all
implementations.
One thought regarding nature of dependency: maybe it'd be good to make stax
implementation a "provided" dependency: provided by platform or added by users.
That way it could use whichever implementation user chose; either the best, or
one that container or JDK provides.
And finally -- if and when there are concerns about Woodstox, would it kill you
to maybe quickly contact Woodstox project team? Who knows, that could even help
resolve issues.
It is rather frustrating to find that there's enough time to complain, and hack
around things, but apparently not enough time to collaborate. Most open source
packages have competent and friendly maintainers, who can be concated to help
resolve issues (or point out that issues are elsewhere as the case may be); or
at least would be interested in learning of such issues.
was (Author: cowtowncoder):
Huh? Woodstox does not use FactoryFinder for anything. Only thing I think
does is the Stax API. Nothing to do with Woodstox; same would apply to
JDK6-bundled Stax implementation (Sun Sjsxp). Ditto for OSGi: Stax/SAX/JAXP all
use introspection mechanism that does not work well with OSGi. This is the same
for all implementations.
Also -- if and when there are concerns about Woodstox, would it kill you to
maybe contact Woodstox project team?
It is rather frustrating to find that many have enough time to complain, whine,
and hack around things, but not enough to actually take time to try to resolve
problems. Most open source packages have competent and friendly maintainers,
who can be concated to help resolve issues (or point out that issues are
elsewhere as the case may be).
Finally: maybe it'd be good to make stax implementation a "provided"
dependency: provided by platform or added by users. That way it could use
whichever implementation user chose; either the best, or one that container or
JDK provides.
> Change template parser to not use STAX, as it is not (yet) compatible with
> Google App Engine
> --------------------------------------------------------------------------------------------
>
> Key: TAP5-713
> URL: https://issues.apache.org/jira/browse/TAP5-713
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Howard M. Lewis Ship
>
> The StAX APIs are not on the GAE "white list".
> Should be reasonable ot change the code, by using a SAX parser that parses
> the template into a list of tokens, and then iterate down the token list as
> we do today using StAX. End result will be fewer dependencies to boot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
