Hm. Google App Engine vs. HTML5 (woodstox is not compatible with GAE). Perhaps the right solution is in the middle: a streamlined XML/HTML5 parser without all the bells and whistles, but passes entity references and the like through unchanged. The actual XML parser in Tapestry is really, really well compartmentalized right now, this is doable.
XML parsing is really easy as long as you don't do validation or support external entities or embedded DTD. Could it be faster than an XML parser? Probably not, but it still could be fast. It might even be something that could be done using ANTLR. On Thu, Jun 17, 2010 at 12:11 AM, Robin Komiwes <[email protected]> wrote: > Hi, > > HTML 5 is awesome, there is so much possibilities of making rich web > applications... It's a web technology that you already can't avoid if > you do iPhone/iPad/Android web development. > Unfortunately it is not possible to do full compliant HTML5 with > Tapestry 5 actually. > > I worked theses lasts days on trying to provide a patch and I may be > wrong but I don't see a way to make it work with the actual > SAXParser. All the problem is related to the doctype declaration > <!DOCTYPE html> and the use of entities. > > Basically you can't do: > > <!doctype html> > <html> > <head> > </head> > <body> > > </body> > </html> > > You will have this kind of error message: The entity "nbsp" was > referenced, but not declared. > > The SAXParser don't know how to handle entities since there is no dtd. > > I gave a try to JSF 2 (Mojarra), I inspected the source code and ran a > few tests. The XML parsing is done in the same way than Tapestry 5. > Understand that they have the same HTML5 incompatibility issue. We > could take some advance here. How? By rollbacking to woodstox. > > We had the same issue in Tapestry 5.1, but I had provided a patch [1] > (which has unfortunately never been integrated). > This patch adds the declaration of the > "IS_REPLACING_ENTITY_REFERENCES" property [2]. All entities are > simply reported as characters. And I find that's great! Imho, the > actual system, which consists of replacing characters entities by > their numerical equivalent is not good because you can't easily read > the generated source. > > Today I'm asking if there is a possibility to consider a rollback to > woodstox parser, in order to unleash the power of HTML5 with Tapestry5. > > Woodstox was removed from Tapestry 5.1 because of Google App Engine > incompatibility problems, actually this problems seems to be fixed > [3], so why not rollbacking? > > [1] https://issues.apache.org/jira/browse/TAP5-840 > [2] > http://java.sun.com/javase/6/docs/api/javax/xml/stream/XMLInputFactory.html#IS_REPLACING_ENTITY_REFERENCES > [3] http://code.google.com/p/googleappengine/issues/detail?id=1277 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
