You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Henri Dupre <he...@gmail.com> on 2005/10/26 03:12:46 UTC
scope="client" for ApplicationObjects
I was wondering if scope="client" would make any sense for ApplicationObjects?
I'm having some troubles implementing a clean navigation on our
website, I want the navigation to be separate from many page elements
and it is not simple to implement the navigation as a persistent
component property.
The other option is to set it as a page persistent property but I'd
rather like to be able to inject it everywhere I need.
Thanks,
Henri.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: scope="client" for ApplicationObjects
Posted by Henri Dupre <he...@gmail.com>.
On 10/25/05, Jesse Kuhnert <jk...@gmail.com> wrote:
> You might want to check out the SiteMap service here:
> http://tacos.sourceforge.net/hivemind/SiteMap.html. We use it for basically
> the same that you describe, injecting it wherever we want it.
If I could have one instance of the service per request, this would
really work for me. How can I do that?
Thanks,
Henri.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: scope="client" for ApplicationObjects
Posted by Jesse Kuhnert <jk...@gmail.com>.
You might want to check out the SiteMap service here:
http://tacos.sourceforge.net/hivemind/SiteMap.html. We use it for basically
the same that you describe, injecting it wherever we want it.
On 10/25/05, Henri Dupre <he...@gmail.com> wrote:
>
> I was wondering if scope="client" would make any sense for
> ApplicationObjects?
> I'm having some troubles implementing a clean navigation on our
> website, I want the navigation to be separate from many page elements
> and it is not simple to implement the navigation as a persistent
> component property.
> The other option is to set it as a page persistent property but I'd
> rather like to be able to inject it everywhere I need.
>
> Thanks,
>
> Henri.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>