I'm not sure about everyone else, but for me this is a BIG issue and is one of the reasons holding me back from moving my app to the 5.1 beta. Most likely I'll hold off on upgrading to 5.1 final if it doesn't support GAE.
Howard was asking earlier about any showstoppers preventing 5.1 from moving forward - this is one for me. Maybe this would be a good feature for 5.2, who knows. Is anyone else holding off on taking up 5.1 for this reason ? Other reasons ? Cheers, Alex Kotchnev On Thu, Apr 16, 2009 at 3:44 PM, Christian Köberl <tapestry.christian.koeb...@gmail.com> wrote: > > > I grepped over the tapestry-core sources for "javax.xml.stream" and only > found them imported in TemplateParser and StaxTemplateParser. > Would it then be sufficient to just contribute another TemplateParser which > isn't using Woodstox (maybe the one from 5.0.1.8)? > > > I just tried to eliminate Woodstox and to use "pure" Stax API for template > parsing. This wasn't that difficult (see > http://derkoe.wordpress.com/2009/04/16/tapestry-51-woodstox/). > > With plain Stax I still get the same error in TemplateParser. Maybe I will > try to switch back to the 5.0.18 one when I have time. > > Cheers, > Chris > -- > View this message in context: > http://n2.nabble.com/Java-support-added-to-Google-AppEngine-tp2605876p2643391.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
