I see what you mean, but still can't make it work.
If I move ProfileInfo.html anywhere outside root folder, I get "Page
'ProfileInfo' not found in application namespace."
If Tapestry could find ProfileInfo.html in subfolder other then root,
maybe it would find ProfileInfo.class in subpackage as well.
This ProfileInfo.html page is called from some other page as
ExternalLink like this:
<a jwcid="@ExternalLink" page="ProfileInfo" ....>
James Carman wrote:
No, here's what I mean. In your application's root directory, create a
directory called "profile." In there, put your ProfileInfo.html file.
Then, Tapestry will look in a subpackage called "profile" under your root
pages package for the ProfileInfo class. Does that make sense?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
