Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by DanielJue: http://wiki.apache.org/tapestry/Tapestry5Caveats The comment on the change is: Added some caveats from an email. ------------------------------------------------------------------------------ Here, 'something' is some element in your application. ==== Cause & Solution ==== + Per HLS: You'll see an explanation in the console. I suspect you are using a slightly older Tapestry preview release; more recently, this situation @@ -27, +28 @@ This also applies when you are subclassing components. Even though Inheritance will let you access public/private variables in the superclass, you will need to make the variables private and use getters/setters instead. + == Underscores in Prefixes for Fields, but not in Accessors == + Use of underscore prefixes for fields, but not in accessors + Some people just grew into doing it this way. By default, Eclipse's + getter/setter autogeneration keeps the underscore. + + ==== Cause & Solution ==== + + Josh says: + This is configurable in Eclipse. Under Window | Preferences look at Java | + Code Style there is a "Conventions for variable names" section where you can + tell eclipse what your prefix/suffix preferences are... Then it will make + nice getter/setter names for you. + + + + == Non case sensitivity of page names in URL == + + This is just a nice feature in Tapestry, documented in the code + + == URL Shortening of page names under a similarly named directory == + + A documented feature intended to make things nice for users. + For example: + + A page named "Report" under a directory named "Report" will not resolve. + + A page named "StatusReport" under a directory named "Report" will resolve to "Status" (i.e. report/status in the url) + + A page named "ReportStatus" under a directory named "Report" will resolve to "Status" (i.e. report/status in the url) + + A page named "StatusReport1" under a directory named "Report" will resolve to "StatusReport1" (i.e. report/statusreport1 in the url) + + ==== Cause & Solution ==== + + For now, just pay attention to how you want your site laid out. If you get a Tapestry error telling you it can't find the page or component you specified, it may be because the URL is being shortened. + + + == Case sensitivity for @OnEvent and similar annotations == + + This is just a Java case sensitivity rule. Those unfamiliar with + annotations before working with Tapestry (as I was) may forget that + case matters in annotations! @onEvent is not the same, and your IDE + should tell you this. + + Non case sensitive for value of OnEvent + {{{ + @OnEvent(value="SUBMIT") + void doSomething(){} + + // is the same as + + @OnEvent(value="submit") + void doSomething(){} + }}} + + + == Case sensitivity for event method names == + + Form event methods without annotations: + + Besides typos in the name of the method, there is a case sensitivity + issue to be aware of: the "on" prefix must be lower case. i.e. + "OnSubmit" will not get called, but "onSubmit" will. T5's extensive + case insensitivity can cause us to be lazy sometimes. + + + == DTD Case Sensitivity == + + Tapestry XML DTD's and their keys are case sensitive + + + == Injected Asset Case Sensitivity == + + Injected Assets are case sensitive. + + This is a Servlet API /Java runtime rule. + + + == Property File Case Sensitivity == + + Names of *.properties files are case sensitive. + + Names of properties inside the *.properties files are not case sensitive + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
