Hi,
After the other day mail (no direct URL access to components), we start
to review our architecture and how to re-design things in order to have
pages instead of components.
We have seen 2 possible options.
The first one:
http://tapestry.apache.org/tapestry5/guide/layout.html
We find out that this is not so useful to us because if the idea is to
have a general page (to be used in other projects), we can't define a
t:type in the page because we don't know if the webApp will have that
type defined.
This is making a kind of circular dependency between the lib that
contains the page and the webapp and we are not so sure if that is the best.
The only way we see is using by convention always "Layout.tml" in the
different webApps so that the weblibs refer to "Layout" in the
t:type(maybe is the way to use it).
The second option was the layout including blocks of components (the one
we are using right now). But this solution is no longer useful to us
because we are needing to access to some components through direct URL
(that's not possible in tapestry).
Does anybody have some problem like this one? How can we solve this? Is
the first option the only way to do it?
Thanks to everyone.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
