[
https://issues.apache.org/jira/browse/TAPESTRY-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592109#action_12592109
]
Howard M. Lewis Ship commented on TAPESTRY-2385:
------------------------------------------------
This seems highly unlikely. Deployment does not change the case sensitivity.
The only cause I can think of is the one area where case matters: the template
for a component must match the case of the class name. Thus if the component
is MyComponent.java, the template must be MyComponent.tml (not
mycomponent.tml). That's just about the only place in T5 where case matters.
Please provide a test case for this bug.
> Case Sensitivity on Nested Components Within Grid
> -------------------------------------------------
>
> Key: TAPESTRY-2385
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2385
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.11
> Environment: windows vista business, eclipse 3.3, tomcat 6, run jetty
> run, maven 2
> Reporter: Evan M Rawson
> Priority: Minor
>
> this bug only appears when packaging project application into war file for
> deployment. Reproduced this bug on jetty 6 and tomcat, so its not the
> servlet. bug is not apparent when developing and using auto class reloading
> within eclipse and run jetty run.
> i have a component i nest within the grid component. everything works fine
> locally. when i go to deploy on production, the component is not rendered,
> and no exception is thrown. the cause of this error is that the first letter
> of my component name in this case searchResult is lower case, when changed to
> uppercase the bug disappears. I had another component which was not nested
> inside grid startinfg with a lower case letter and it was rendered okay.
> there should be an exception that is thrown in the case of this. all file
> names should begin with uppercase to represent objects
--
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]
