You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Michael Echerer <me...@tngtech.com> on 2004/07/07 18:10:05 UTC
Spindle 3.1.2 / Eclipse 3.0final. Problem with resolving page. Maybe Spindle issue
Hi,
I'm using Spindle 3.1.2 and Eclipse 3.0final. Still Tapestry 3.0rc1, but I doubt
that matters.
I get a warning "Page 'Well-known-page' not found in namespace 'mylib'".
For my webapp I have two main packages "myapp" and "mylib", which is an expanded
custom Tapestry library.
I have a simple mylib component which has a <a jwcid="@PageLink"
page="Well-known-page"> inside its .html.
When the webapp is running Tapestry can resolve the Well-known-page, although it
is logically within my Tapestry application (myapp) and "not" in the mylib.
But Spindle complains it would not work...
Of course it might not be a good idea to reference pages in a library which are
not included in the libary itself, but you can do it.
Maybe Geoff could verify if this is a Spindle bug as a running Tapestry webapp
works with this and it should be reflected in the Spindle warnings.
Or is there a way to tell that the Well-known-page is in the namespace of the
application and not of the library?
Greetings
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Re: Attn Howard (Was: Spindle 3.1.2 / Eclipse 3.0final. Problem with resolving page. Maybe Spindle issue)
Posted by Howard Lewis Ship <hl...@gmail.com>.
I'll look at it over the weekend; my eyes are blurred right now from
too much quality time with my laptop.
On Fri, 09 Jul 2004 14:08:28 -0400, Geoff Longman
<gl...@intelligentworks.com> wrote:
> Any reading on this Howard? Other users are coming across this problem.
>
> Geoff
>
>
>
> Geoff Longman wrote:
>
> >Seems I missed something when I was sleuthing about the Tapestry code when figuring out how pages are resolved in libraries.
> >
> >Howard, pls correct me if I'm wrong here. (pcode)
> >
> >In Spindle, checking the condition described goes as follows:
> >
> >given:
> >
> >INamespace componentNS = The namespace of the page/component (in this case a library)
> >+ The contents of the PageLink page parameter: aaaaa:bbbbb
> >
> >libraryId = aaaaa
> >pageName=bbbbb
> >
> >INamespage useToResolve = null
> >
> >if (libraryId != null && libraryId != componentNS.getId())
> >
> >then useToResolve = componentNS.getChildNamespace(libraryId)
> >else useToResolve = componentNS
> >
> >if (useToResolve == null)
> > return null (no page found) <--- I guess this should not be. Rather locate the App namespace.
> >
> >if (useToResolve.containsPage(pageName))
> > return useToResolve.getPageSpecification(pageName)
> >
> >if (libraryId == null)
> > return resolveInFramework(pageName)
> >
> >(no page found)
> >
> >Geoff
> >
> >----- Original Message -----
> >From: "Michael Echerer" <me...@tngtech.com>
> >To: "'Tapestry users'" <ta...@jakarta.apache.org>
> >Sent: Wednesday, July 07, 2004 12:10 PM
> >Subject: Spindle 3.1.2 / Eclipse 3.0final. Problem with resolving page. Maybe Spindle issue
> >
> >
> >
> >
> >>Hi,
> >>
> >>I'm using Spindle 3.1.2 and Eclipse 3.0final. Still Tapestry 3.0rc1, but I doubt
> >>that matters.
> >>
> >>I get a warning "Page 'Well-known-page' not found in namespace 'mylib'".
> >>
> >>For my webapp I have two main packages "myapp" and "mylib", which is an expanded
> >>custom Tapestry library.
> >>
> >>I have a simple mylib component which has a <a jwcid="@PageLink"
> >>page="Well-known-page"> inside its .html.
> >>
> >>When the webapp is running Tapestry can resolve the Well-known-page, although it
> >>is logically within my Tapestry application (myapp) and "not" in the mylib.
> >>But Spindle complains it would not work...
> >>Of course it might not be a good idea to reference pages in a library which are
> >>not included in the libary itself, but you can do it.
> >>
> >>Maybe Geoff could verify if this is a Spindle bug as a running Tapestry webapp
> >>works with this and it should be reflected in the Spindle warnings.
> >>Or is there a way to tell that the Well-known-page is in the namespace of the
> >>application and not of the library?
> >>
> >>Greetings
> >>Michael
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >>
> >>
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Attn Howard (Was: Spindle 3.1.2 / Eclipse 3.0final. Problem with
resolving page. Maybe Spindle issue)
Posted by Geoff Longman <gl...@intelligentworks.com>.
Any reading on this Howard? Other users are coming across this problem.
Geoff
Geoff Longman wrote:
>Seems I missed something when I was sleuthing about the Tapestry code when figuring out how pages are resolved in libraries.
>
>Howard, pls correct me if I'm wrong here. (pcode)
>
>In Spindle, checking the condition described goes as follows:
>
>given:
>
>INamespace componentNS = The namespace of the page/component (in this case a library)
>+ The contents of the PageLink page parameter: aaaaa:bbbbb
>
>libraryId = aaaaa
>pageName=bbbbb
>
>INamespage useToResolve = null
>
>if (libraryId != null && libraryId != componentNS.getId())
>
>then useToResolve = componentNS.getChildNamespace(libraryId)
>else useToResolve = componentNS
>
>if (useToResolve == null)
> return null (no page found) <--- I guess this should not be. Rather locate the App namespace.
>
>if (useToResolve.containsPage(pageName))
> return useToResolve.getPageSpecification(pageName)
>
>if (libraryId == null)
> return resolveInFramework(pageName)
>
>(no page found)
>
>Geoff
>
>----- Original Message -----
>From: "Michael Echerer" <me...@tngtech.com>
>To: "'Tapestry users'" <ta...@jakarta.apache.org>
>Sent: Wednesday, July 07, 2004 12:10 PM
>Subject: Spindle 3.1.2 / Eclipse 3.0final. Problem with resolving page. Maybe Spindle issue
>
>
>
>
>>Hi,
>>
>>I'm using Spindle 3.1.2 and Eclipse 3.0final. Still Tapestry 3.0rc1, but I doubt
>>that matters.
>>
>>I get a warning "Page 'Well-known-page' not found in namespace 'mylib'".
>>
>>For my webapp I have two main packages "myapp" and "mylib", which is an expanded
>>custom Tapestry library.
>>
>>I have a simple mylib component which has a <a jwcid="@PageLink"
>>page="Well-known-page"> inside its .html.
>>
>>When the webapp is running Tapestry can resolve the Well-known-page, although it
>>is logically within my Tapestry application (myapp) and "not" in the mylib.
>>But Spindle complains it would not work...
>>Of course it might not be a good idea to reference pages in a library which are
>>not included in the libary itself, but you can do it.
>>
>>Maybe Geoff could verify if this is a Spindle bug as a running Tapestry webapp
>>works with this and it should be reflected in the Spindle warnings.
>>Or is there a way to tell that the Well-known-page is in the namespace of the
>>application and not of the library?
>>
>>Greetings
>>Michael
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Attn Howard (Was: Spindle 3.1.2 / Eclipse 3.0final. Problem with resolving page. Maybe Spindle issue)
Posted by Geoff Longman <gl...@intelligentworks.com>.
Seems I missed something when I was sleuthing about the Tapestry code when figuring out how pages are resolved in libraries.
Howard, pls correct me if I'm wrong here. (pcode)
In Spindle, checking the condition described goes as follows:
given:
INamespace componentNS = The namespace of the page/component (in this case a library)
+ The contents of the PageLink page parameter: aaaaa:bbbbb
libraryId = aaaaa
pageName=bbbbb
INamespage useToResolve = null
if (libraryId != null && libraryId != componentNS.getId())
then useToResolve = componentNS.getChildNamespace(libraryId)
else useToResolve = componentNS
if (useToResolve == null)
return null (no page found) <--- I guess this should not be. Rather locate the App namespace.
if (useToResolve.containsPage(pageName))
return useToResolve.getPageSpecification(pageName)
if (libraryId == null)
return resolveInFramework(pageName)
(no page found)
Geoff
----- Original Message -----
From: "Michael Echerer" <me...@tngtech.com>
To: "'Tapestry users'" <ta...@jakarta.apache.org>
Sent: Wednesday, July 07, 2004 12:10 PM
Subject: Spindle 3.1.2 / Eclipse 3.0final. Problem with resolving page. Maybe Spindle issue
> Hi,
>
> I'm using Spindle 3.1.2 and Eclipse 3.0final. Still Tapestry 3.0rc1, but I doubt
> that matters.
>
> I get a warning "Page 'Well-known-page' not found in namespace 'mylib'".
>
> For my webapp I have two main packages "myapp" and "mylib", which is an expanded
> custom Tapestry library.
>
> I have a simple mylib component which has a <a jwcid="@PageLink"
> page="Well-known-page"> inside its .html.
>
> When the webapp is running Tapestry can resolve the Well-known-page, although it
> is logically within my Tapestry application (myapp) and "not" in the mylib.
> But Spindle complains it would not work...
> Of course it might not be a good idea to reference pages in a library which are
> not included in the libary itself, but you can do it.
>
> Maybe Geoff could verify if this is a Spindle bug as a running Tapestry webapp
> works with this and it should be reflected in the Spindle warnings.
> Or is there a way to tell that the Well-known-page is in the namespace of the
> application and not of the library?
>
> Greetings
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org