Kunal Ashar wrote:
I cannot understand this! I've used components for navigation with no problems. For instance,There still seems to be a fine line between pages and components.
For example, problems started with when I began developing components which needed to take some data from a page/parent component and update some data into page/parent component. Intercomponent communication turned out to be quite messy, as were components that participated in navigation. Apparently pages win where inter communication is needed and where navigation is required.
For example, a Login page can be a component if it just indicates that user is authenticated but should not be a component if it says, "user is authenticated so go to home page". Overall, it seems like components can not be used when they will be involved in navigation based on the user clicks.
I always use/create a menu component and it's quite handy. I mainly have PageLinks and
DirectLinks inside these components to change the current page or perform custom actions...
I don't usually need these component to update any parent page properties, so I don't know
if there are any issues there, but I generally allow them to interact with the visit object.
Regarding restricting page access to authenticated users, I agree that this is a job of a
"base" Page (i.e. extend pageValidate(PageEvent event) )
On re-reading your mail, perhaps you're talking about having components auto-forward to
other pages? Again, I haven't yet had any need to perform that and I don't know if there are
any issues there...
Perhaps you could give some more exaples of your problems :)
Seems like with Tapestry 3.0, components should be self sustainable. I feel component bindings are not matured and may be the reason for some of the issues.
Any thoughts?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
