Component ids shouldn't have to be valid java identifiers
---------------------------------------------------------
Key: TAPESTRY-1996
URL: https://issues.apache.org/jira/browse/TAPESTRY-1996
Project: Tapestry
Issue Type: Bug
Reporter: Chris Lewis
Priority: Minor
Fix For: 5.0, 5.0.7
When I ran through some tests on the latest svn (r606399), I ran into what I
believe is a bug. Until this release I have been happily able to use w3c valid
identifiers as component ids. I feel this is natural as this id ultimately ends
up as the element id. However this morning I got a nasty
org.apache.tapestry.ioc.internal.util.TapestryException, telling me that
"Component id 'ss-test' is not valid; component ids must be valid Java
identifiers: start with a letter, and consist of letters, numbers and
underscores."
I assume this was deliberate as up until this revision, I've not seen it. My
question is why should component ids be forced to comply with java identifier
naming conventions? It's just a string value, and I personally prefer using "-"
as a separator to "_". Will this be reverted? I don't understand why my
application shouldn't run when I am using a (w3c) valid id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
