While I agree with you in spirit here my opinion. Sending not well formed XML to any web client is a bad idea and if you do it even by accident you are just asking for hours of grief. Using CDATA to work around this when needed is a small price to pay. Being able to use existing parsers is just icing on the cake.
As far as supporting this out of the box I'd say it does a pretty good job there also. While I had to write a component it's only about 20 lines of code, easily reusable and hardly a workaround. The success of a framework should be judged on how easily is supports new features not by what's supported in the core. So others may disagree but I'd say valid XML .tml files is a feature that I would not be willing to give up and components were designed to solve exactly the problem you are having and do it quite well. BTW: thanks for posting this problem so I finally got around to solving mine. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-and-inline-Handlebars-js-tp5660756p5664686.html Sent from the Tapestry - User 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
