Re: CamelCase page names/URLs in Tapestry

2007-01-04 Thread Howard Lewis Ship
I know I have one potential client, The Name Withheld Corporation, that's interested in Tapestry but needs the URLs to be case-insensitive. Back in the Tapestry 2.x days, this wouldn't be so difficult. You started with the application specification, which matched each possible page name to a spe

RE: CamelCase page names/URLs in Tapestry

2007-01-03 Thread Marcus.Schulte
> In AppFuse 2.0, we're requiring JDK 5 and using annotations > where it seems appropriate. AFAIK, we can eliminate .page > files if we use annotations instead. Is that true? If so, Yes that's true. > how do you define how a @TextField works (displayName, > validation rules, etc.)? Do you

Re: CamelCase page names/URLs in Tapestry

2006-12-29 Thread mraible
Martin, Thanks for the link to show this is possible. I like your advice of going with the flow though. ;-) Matt Martin Strand-4 wrote: > > Matt, > it's *possible* to make the first character lower case in all page urls > without changing any *.page files or classes. You could do this with

RE: CamelCase page names/URLs in Tapestry

2006-12-29 Thread mraible
In AppFuse 2.0, we're requiring JDK 5 and using annotations where it seems appropriate. AFAIK, we can eliminate .page files if we use annotations instead. Is that true? If so, how do you define how a @TextField works (displayName, validation rules, etc.)? Do you use annotations on your model o

Re: CamelCase page names/URLs in Tapestry

2006-12-29 Thread Martin Strand
Matt, it's *possible* to make the first character lower case in all page urls without changing any *.page files or classes. You could do this with a custom service encoder, but it's probably just easier to go with the flow and leave them as they are. :) See "encoder" at the bottom: http://

RE: CamelCase page names/URLs in Tapestry

2006-12-29 Thread Marcus.Schulte
You'd have to map between .page- and template-file-name and the Java class name if you don't want to break the convention for Java class names. Since Tap-4 I don't have .page files anymore. So non-CamelCase page names would simply not be an option for me - even if I found them aesthetically more

Re: CamelCase page names/URLs in Tapestry

2006-12-29 Thread Jesse Kuhnert
Not even taking into account the items specific to Tapestry templates/pages/etc, it really comes down to which usability effect you are going for: -) Aesthetically pleasing to the eye. This would seem to support your all lowercase idea for url's. Not necessarily the best thing as far as reading u