You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Cherry Development <av...@cherrydev.com> on 2004/08/05 22:34:33 UTC
Namespaces, Libraries and application structure?
How do you refer to a component in one library from another?
For example:
Inside a component in library foo
<div jwcid="bar:Component"/>
Produces an error: library 'bar' not found in namespace 'foo'.
If you have circular library references, both Spindle and Tapestry end
up with stack overflows.
The following suggestion seems like a simple solution. Would it work?
If a page/component path begins with a colon, simply traverse back to
the application namespace and search recursively from there.
I've done what I believe is a thorough search of the mailing list and
other archives on this subject and it appears that people have been
asking for this sort of ability for a long time. Tapestry projects,
I'm sure, are getting larger and larger and therefore, the ability to
structure them needs to grow with the framework.
Has anyone else discovered a solution to this?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Namespaces, Libraries and application structure?
Posted by Jamie Orchard-Hays <ja...@dang.com>.
Sorry, I missed that part!
----- Original Message -----
From: "Cherry Development" <av...@cherrydev.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Thursday, August 05, 2004 5:19 PM
Subject: Re: Namespaces, Libraries and application structure?
> The problem begins when you try to refer to one library from within a
> component in another library, as I described.
>
> On Aug 5, 2004, at 2:02 PM, Jamie Orchard-Hays wrote:
>
> > In your .application file you tell your application what the prefix is:
> > <library id="foo"
> > specification-path="/org/my/company/library/Foo.library"/>
> >
> > Now it will be referred to as "foo:MyComponent"
> >
> > When you jar up a library you put in a file called "<mylibrary>.library
> >
> > Look in the Contrib.library file for reference.
>
>
> ---------------------------------------------------------------------
> 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
Re: Namespaces, Libraries and application structure?
Posted by Cherry Development <av...@cherrydev.com>.
The problem begins when you try to refer to one library from within a
component in another library, as I described.
On Aug 5, 2004, at 2:02 PM, Jamie Orchard-Hays wrote:
> In your .application file you tell your application what the prefix is:
> <library id="foo"
> specification-path="/org/my/company/library/Foo.library"/>
>
> Now it will be referred to as "foo:MyComponent"
>
> When you jar up a library you put in a file called "<mylibrary>.library
>
> Look in the Contrib.library file for reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Namespaces, Libraries and application structure?
Posted by Jamie Orchard-Hays <ja...@dang.com>.
In your .application file you tell your application what the prefix is:
<library id="foo" specification-path="/org/my/company/library/Foo.library"/>
Now it will be referred to as "foo:MyComponent"
When you jar up a library you put in a file called "<mylibrary>.library
Look in the Contrib.library file for reference.
Jamie
----- Original Message -----
From: "Cherry Development" <av...@cherrydev.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Thursday, August 05, 2004 4:34 PM
Subject: Namespaces, Libraries and application structure?
>
> How do you refer to a component in one library from another?
>
> For example:
> Inside a component in library foo
> <div jwcid="bar:Component"/>
> Produces an error: library 'bar' not found in namespace 'foo'.
>
> If you have circular library references, both Spindle and Tapestry end
> up with stack overflows.
>
> The following suggestion seems like a simple solution. Would it work?
>
> If a page/component path begins with a colon, simply traverse back to
> the application namespace and search recursively from there.
>
> I've done what I believe is a thorough search of the mailing list and
> other archives on this subject and it appears that people have been
> asking for this sort of ability for a long time. Tapestry projects,
> I'm sure, are getting larger and larger and therefore, the ability to
> structure them needs to grow with the framework.
>
> Has anyone else discovered a solution to this?
>
>
> ---------------------------------------------------------------------
> 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