DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36643>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36643 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-17 14:33 ------- (In reply to comment #3) Gary, after you have confirmed that we had an crossover, I will answer your question. > I'm not sure that I agree with you on that. Don't we have a similar > situation in JSP 2.0 where ${ something } is implicitly assumed to be an > expression. Or, the expression <%= something %> has implied meaning. I don't > think it's wrong to make an assumption that #{ something } would have > implicit meaning within a clay template document. There is one big difference. For JSP, the implicit meaning is part of the spec and every developer should know it. If the developer does not know what he does, he must learn it on the hard way. For HTML, no such implicit behaviour exist and therefore the designers are possibly not aware of the restriction. And to make things worse, the tools they use are not aware of the restriction too. So it is possible that every time you save your file, you have to change it back manually to character references. And at last, we don't need it. Instead of <title>#{msgs['usecases.rolodex2']}</title> which also impairs the WYSIWYG capabilities of the template, we can already use <title> <span jsfid="verbatim" value="#{msgs['usecases.rolodex2']}">Mock Title</span> </title> And if you don't like the <span> we may implement something like this in the future: <title jsfid="@Insert" value="msgs:usecases.rolodex2">Mock Title</title> Currently I leave the bug as resolved, since it is not necessary to solve this discussion for an first developer release. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
