I really have to ask ... why would you care?
And the issue here is enclosure vs. containment. Containment is the
concrete structure of the components, it really is the component
hierarchy. Enclosure is largely a factor in how the templates are
laid out ("report" encloses "header"), but can be much more dynamic
(witness the jumping around that BeanEditForm accomplishes, literally
pulling chunks of other pages into the mix).
On Fri, Mar 28, 2008 at 2:01 PM, Janko Muzykant <[EMAIL PROTECTED]> wrote:
>
> hi, i have a following problem with urls generated by nested links components
> - lets say, we have a reportUsers page and something like this inside:
>
> <t:report t:id="report">
> <th t:type="header" column="username"/>
>
> header is my component that creates ActionLink with parameter given in
> 'column' attribute. Generated url looks like this:
> http://myhost:port/context/path/reportUsers.header/username. pretty cool,
> but it's not what I would like to achieve. As 'header' component is nested
> inside 'report' I would expect the url to look like:
> .../path/reportUsers.report.header/username. Could you give me a hint how to
> get it?
>
> thanks,
> jm.
>
>
>
> --
> View this message in context:
> http://www.nabble.com/T5-Nested-Link-components-and-their-urls-tp16362062p16362062.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
