If you are trying to use a Component as a Page, then you're in for trouble. A component must be used in a page.
Jamie
Kunal Ashar wrote:
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.
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]
