You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Norbert Sándor <de...@erinors.com> on 2006/08/11 12:22:23 UTC
nested namespaces
Hello,
IRequestCycle.getPage() allows accessing of pages in subnamespaces like
cycle.getPage("Library.SubLibrary:SomePage")
Would it be difficult to implement the same in case of the component
type definitions?
I mean something like
<component type="Library.SubLibrary:SomeComponent" ...
Thanks in advance:
Norbi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: nested namespaces
Posted by Norbert Sándor <de...@erinors.com>.
I think yes, by using
cycle.getPage("Library:Page")
Regards,
Norbi
Mark Stang wrote:
> Is it possible in 3.x to access pages in libraries?
>
> thanks,
>
> Mark
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
> Sent: Fri 8/11/2006 11:52 AM
> To: Tapestry development
> Subject: Re: nested namespaces
>
> For pages, the syntax needs to be possible, otherwise there'd be no way to
> identify a page within a library as part of a URL (i..e, the page
> parameter).
>
> For components, this should not be necessary, as it reflects the internal
> implementation of a library (i.e., the fact that Library uses SubLibrary is
> a implementation detail, not part of its API).
>
> On 8/11/06, Norbert Sándor <de...@erinors.com> wrote:
>
>> Hello,
>>
>> IRequestCycle.getPage() allows accessing of pages in subnamespaces like
>>
>> cycle.getPage("Library.SubLibrary:SomePage")
>>
>> Would it be difficult to implement the same in case of the component
>> type definitions?
>> I mean something like
>>
>> <component type="Library.SubLibrary:SomeComponent" ...
>>
>> Thanks in advance:
>> Norbi
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>>
>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.10.8/414 - Release Date: 2006.08.09.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
RE: nested namespaces
Posted by Mark Stang <ms...@pingidentity.com>.
Is it possible in 3.x to access pages in libraries?
thanks,
Mark
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Fri 8/11/2006 11:52 AM
To: Tapestry development
Subject: Re: nested namespaces
For pages, the syntax needs to be possible, otherwise there'd be no way to
identify a page within a library as part of a URL (i..e, the page
parameter).
For components, this should not be necessary, as it reflects the internal
implementation of a library (i.e., the fact that Library uses SubLibrary is
a implementation detail, not part of its API).
On 8/11/06, Norbert Sándor <de...@erinors.com> wrote:
>
> Hello,
>
> IRequestCycle.getPage() allows accessing of pages in subnamespaces like
>
> cycle.getPage("Library.SubLibrary:SomePage")
>
> Would it be difficult to implement the same in case of the component
> type definitions?
> I mean something like
>
> <component type="Library.SubLibrary:SomeComponent" ...
>
> Thanks in advance:
> Norbi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
Re: nested namespaces
Posted by Howard Lewis Ship <hl...@gmail.com>.
For pages, the syntax needs to be possible, otherwise there'd be no way to
identify a page within a library as part of a URL (i..e, the page
parameter).
For components, this should not be necessary, as it reflects the internal
implementation of a library (i.e., the fact that Library uses SubLibrary is
a implementation detail, not part of its API).
On 8/11/06, Norbert Sándor <de...@erinors.com> wrote:
>
> Hello,
>
> IRequestCycle.getPage() allows accessing of pages in subnamespaces like
>
> cycle.getPage("Library.SubLibrary:SomePage")
>
> Would it be difficult to implement the same in case of the component
> type definitions?
> I mean something like
>
> <component type="Library.SubLibrary:SomeComponent" ...
>
> Thanks in advance:
> Norbi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com