Right in front of my nose. I practically stole my example right out of the
chapter.

Any insight though into the main part of my question where I am trying to
create a page that has the same name as a package?

It doesn't seem as though the optimizations described in that chapter should
have an effect in this situation.

Thanks.



> For example, in: 
> 
>    com.mydomain.myapp.pages.subpackage1.* 
> 
> I could reference a page at: 
> 
>    www.mydomain.com/myapp/subpackage1 
> 
-- 
View this message in context: 
http://www.nabble.com/-T5--Page-with-same-name-as-package-tf4497463.html#a12827544
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to