On Wed, 07 May 2014 03:51:12 -0300, mailingl...@j-b-s.de
<mailingl...@j-b-s.de> wrote:
It looks like the library mapping name is causing this effect: in case
the name begins with a digit as first character like "1st" component
rendering fails. Using "first" instead fixes the problem and everything
works as expected.
To me it looks like bug, but if it is expected behaviour I would prefer
an "Illegal libray mapping name" exception. What do you think?
As far as I can see, Tapestry couldn't even provide a good error message
because the exception occurs inside the XML parser. Of course, Tapestry
could throw an exception when you add the library mapping itself. JIRA
please?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org