You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Yunfeng Hou <ho...@yahoo.com> on 2005/07/25 15:35:02 UTC
component packaging
I am thinking about that if Tapestry could have a
consistent component packaging mechanism, which will
ease the development, the usage and tools such as
spindle. Here's what I thought.
1. components should be packaged into a jar file, or,
may be we can name it as tapestry archive(tar) :-)
2. components should have an entry in META-INF, just
as hivemind.xml, it will list all libabry files this
archive contains.
3. component archives can be put into
WEB-INF/components directory, this can be default or
be configured in tapestry.application file, or as
servlet parameter. I prefer the latter, since most the
time my tapestry.application file contains only the
library reference. I think tools like spindle can easy
find all components there.
4. tapestry servlet should have a context class loader
including these archives which can be referenced by
all pages it serves.
Yunfeng Hou
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: render informal parameters in composite components
Posted by Johan Maasing <jo...@zoom.nu>.
Robert Zeigler wrote:
> Hi Johan,
> In your .jwc file of C, try:
>
> <component id="A" inherit-informal-parameters="yes">
> </component>
>
> Robert
That works, thanks a lot.
> Johan Maasing wrote:
>
>>I got stuck on how to pass informal parameters from one component to
>>another (Tapestry 3).
>>Say that I have defined my own component C. The C.jwc allows informal
>>parameters.
>>Now the C.html template looks like this:
>>
>><span jwcid="A" /> <span jwcid="B" />
>>
>>How can I make A render the informal parameters passed to C?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: render informal parameters in composite components
Posted by Robert Zeigler <ro...@scazdl.org>.
Hi Johan,
In your .jwc file of C, try:
<component id="A" inherit-informal-parameters="yes">
</component>
Robert
Johan Maasing wrote:
> I got stuck on how to pass informal parameters from one component to
> another (Tapestry 3).
> Say that I have defined my own component C. The C.jwc allows informal
> parameters.
> Now the C.html template looks like this:
>
> <span jwcid="A" /> <span jwcid="B" />
>
> How can I make A render the informal parameters passed to C?
>
>
> My concrete problem is that I want a component that acts like the Any
> component except that the id parameter is generated from getIdPath (or
> some unique string) and a script should be included on the page that
> operates on the HTML element id. So the template is actually:
>
> <span jwcid="@Any" element="ognl:element" id="ognl:idPath">
> <span jwcid="@RenderBody"/>
> </span>
> <span jwcid="script"/>
>
> Cheers,
> Johan Maasing
>
> ---------------------------------------------------------------------
> 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
render informal parameters in composite components
Posted by Johan Maasing <jo...@zoom.nu>.
I got stuck on how to pass informal parameters from one component to
another (Tapestry 3).
Say that I have defined my own component C. The C.jwc allows informal
parameters.
Now the C.html template looks like this:
<span jwcid="A" /> <span jwcid="B" />
How can I make A render the informal parameters passed to C?
My concrete problem is that I want a component that acts like the Any
component except that the id parameter is generated from getIdPath (or
some unique string) and a script should be included on the page that
operates on the HTML element id. So the template is actually:
<span jwcid="@Any" element="ognl:element" id="ognl:idPath">
<span jwcid="@RenderBody"/>
</span>
<span jwcid="script"/>
Cheers,
Johan Maasing
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: component packaging
Posted by Robert Zeigler <ro...@scazdl.org>.
Well... you /can/ upload components, download components, comment on
them, and rate them at tassel...
(http://equalitylearning.org/Tassel/app). There was a big discussion on
this very topic not so long ago (~2 weeks?). You might also check out
the tacos project on sourceforge. From the discussion, it sounded like
several people were going to jump into the furthering of tacos.
I've also opened the code of tassel on sourceforge and there are a
couple of people who have stepped up to the plate in helping improve it.
(Incidentally... much thanks to Johan Maasing for coming up with a much
improved stylesheet for Tassel! :)
Robert
Yunfeng Hou wrote:
> Howard,
>
> Is that possible for us to have a site as
> http://eclipse-plugins.2y.net/eclipse/index.jsp, which
> will allow us upload componets, download them, comment
> on them, rate them. I believe that will encourage more
> people to participate in this great project. As every
> one knows the power of tapestry components, but still
> it is too difficult to find components from the net.
>
> I think the following will make a component
> useful,
> 1. component archive
> 2. component doc
> 3. dependency and supported tapestry version
> 4. sample code/template
> 5. screen snapshot
> 6. user comments, rating, download counts
>
> Tapestry is a technically superior project, we now
> need some kind of effort non-technically to make it a
> perfect project. :-)
>
>
> Yunfeng Hou
>
> --- Howard Lewis Ship <hl...@gmail.com> wrote:
>
>
>>Actually, he was making some suggestions to go
>>beyond what Tapestry
>>provides today, some of which would be useful to
>>tools like Spindle
>>and Palette, or even to distro communities like
>>Tacos.
>>
>>On 7/25/05, Nick Westgate <ni...@key-planning.co.jp>
>>wrote:
>>
>>>Hi.
>>>
>>>Howard's book "Tapestry In Action" explains how to
>>
>>do this in
>>
>>>chapter 6.9 "Packaging components into libraries".
>>>
>>>Components are (1) packaged in a jar, (2)
>>
>>specified in a
>>
>>>".library" file, (3) included in the classpath and
>>
>>configured
>>
>>>in the ".application" file, just like the contrib
>>
>>library
>>
>>>(bundled with Tapestry) and the base library (from
>>
>>T-Deli).
>>
>>>Cheers,
>>>Nick.
>>>
>>>
>>>Yunfeng Hou wrote:
>>>
>>>>I am thinking about that if Tapestry could have
>>
>>a
>>
>>>>consistent component packaging mechanism, which
>>
>>will
>>
>>>>ease the development, the usage and tools such
>>
>>as
>>
>>>>spindle. Here's what I thought.
>>>>
>>>>1. components should be packaged into a jar
>>
>>file, or,
>>
>>>>may be we can name it as tapestry archive(tar)
>>
>>:-)
>>
>>>>2. components should have an entry in META-INF,
>>
>>just
>>
>>>>as hivemind.xml, it will list all libabry files
>>
>>this
>>
>>>>archive contains.
>>>>3. component archives can be put into
>>>>WEB-INF/components directory, this can be
>>
>>default or
>>
>>>>be configured in tapestry.application file, or
>>
>>as
>>
>>>>servlet parameter. I prefer the latter, since
>>
>>most the
>>
>>>>time my tapestry.application file contains only
>>
>>the
>>
>>>>library reference. I think tools like spindle
>>
>>can easy
>>
>>>>find all components there.
>>>>4. tapestry servlet should have a context class
>>
>>loader
>>
>>>>including these archives which can be referenced
>>
>>by
>>
>>>>all pages it serves.
>>>>
>>>>
>>>>Yunfeng Hou
>>>>
>>>>
>>>>
>>>>
>>>>__________________________________
>>>>Do you Yahoo!?
>>>>Yahoo! Mail - You care about security. So do we.
>>>>http://promotions.yahoo.com/new_mail
>>>>
>>>>
>>
> ---------------------------------------------------------------------
>
>>>>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
>>
>>Professional Tapestry training, mentoring, support
>>and project work. http://howardlewisship.com
>>
>>
>
> ---------------------------------------------------------------------
>
>>To unsubscribe, e-mail:
>>tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail:
>>tapestry-user-help@jakarta.apache.org
>>
>>
>
>
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
> ---------------------------------------------------------------------
> 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: component packaging
Posted by Yunfeng Hou <ho...@yahoo.com>.
Howard,
Is that possible for us to have a site as
http://eclipse-plugins.2y.net/eclipse/index.jsp, which
will allow us upload componets, download them, comment
on them, rate them. I believe that will encourage more
people to participate in this great project. As every
one knows the power of tapestry components, but still
it is too difficult to find components from the net.
I think the following will make a component
useful,
1. component archive
2. component doc
3. dependency and supported tapestry version
4. sample code/template
5. screen snapshot
6. user comments, rating, download counts
Tapestry is a technically superior project, we now
need some kind of effort non-technically to make it a
perfect project. :-)
Yunfeng Hou
--- Howard Lewis Ship <hl...@gmail.com> wrote:
> Actually, he was making some suggestions to go
> beyond what Tapestry
> provides today, some of which would be useful to
> tools like Spindle
> and Palette, or even to distro communities like
> Tacos.
>
> On 7/25/05, Nick Westgate <ni...@key-planning.co.jp>
> wrote:
> > Hi.
> >
> > Howard's book "Tapestry In Action" explains how to
> do this in
> > chapter 6.9 "Packaging components into libraries".
> >
> > Components are (1) packaged in a jar, (2)
> specified in a
> > ".library" file, (3) included in the classpath and
> configured
> > in the ".application" file, just like the contrib
> library
> > (bundled with Tapestry) and the base library (from
> T-Deli).
> >
> > Cheers,
> > Nick.
> >
> >
> > Yunfeng Hou wrote:
> > > I am thinking about that if Tapestry could have
> a
> > > consistent component packaging mechanism, which
> will
> > > ease the development, the usage and tools such
> as
> > > spindle. Here's what I thought.
> > >
> > > 1. components should be packaged into a jar
> file, or,
> > > may be we can name it as tapestry archive(tar)
> :-)
> > > 2. components should have an entry in META-INF,
> just
> > > as hivemind.xml, it will list all libabry files
> this
> > > archive contains.
> > > 3. component archives can be put into
> > > WEB-INF/components directory, this can be
> default or
> > > be configured in tapestry.application file, or
> as
> > > servlet parameter. I prefer the latter, since
> most the
> > > time my tapestry.application file contains only
> the
> > > library reference. I think tools like spindle
> can easy
> > > find all components there.
> > > 4. tapestry servlet should have a context class
> loader
> > > including these archives which can be referenced
> by
> > > all pages it serves.
> > >
> > >
> > > Yunfeng Hou
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail - You care about security. So do we.
> > > http://promotions.yahoo.com/new_mail
> > >
> > >
>
---------------------------------------------------------------------
> > > 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
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
>
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: component packaging
Posted by Yunfeng Hou <ho...@yahoo.com>.
I write a tapestry servlet which will load component
jars in WEB-INF/lib directory into specification. A
component jar is a jar with tapestry information
packaged in META-INF/MANIFEST.MF. For example
Manifest-Version: 1.0
Name: Tapestry
Library-Id: contrib
Library-Path:
/org/apache/tapestry/contrib/Contrib.library
Where Tapestry is the entry name, Library-Id defines
library id, and Library-Path defines classpath of
library file.
The servlet will try to find such information, but it
will ignore the library id already defined. So if
component jars have same Library-Id defined, we can
still override the value in tapestry.application file.
I think even people do not like to use this servlet to
load component jars, it is still a good practice to
have information defined in the jar manifest. I like
to add more attributes such as,
Tapestry-Version: the version supported by the
component library;
Library-Version: version of the library itself.
These kind of information may not be used at runtime,
but it certainly can help dev tools.
Yunfeng Hou
--- Kevin Menard <km...@servprise.com> wrote:
>
> On Jul 25, 2005, at 2:13 PM, Marcus Brito wrote:
>
> > Kevin Menard <kmenard <at> servprise.com> writes:
> >
> >
> >> What do you propose should happen when two JARs
> set the same
> >> Tapestry-
> >> Component-Library value?
> >>
> >
> > Hmm, that would be tricky. How about loading only
> the first one
> > found, and issue
> > warnings about any duplicate namespaces?
>
> This would most certainly cause confusion.
>
> > A second option would be to detect this
> > situation *before* loading any library, and loudly
> complain about
> > it (i.e.,
> > throw an exception) if there are duplicate
> namespaces.
>
> This would result in a case where two component libs
> cannot be used
> unless the two authors coordinate on who uses what
> namespace. Even
> if it was configurable, you'd lose the "works
> out-of-the-box" feature.
>
> I think a convention for namespace claiming would be
> more
> appropriate, although I'm not sure what that
> convention would be.
>
> --
> Kevin
>
>
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Re: component packaging
Posted by Kevin Menard <km...@servprise.com>.
On Jul 25, 2005, at 2:13 PM, Marcus Brito wrote:
> Kevin Menard <kmenard <at> servprise.com> writes:
>
>
>> What do you propose should happen when two JARs set the same
>> Tapestry-
>> Component-Library value?
>>
>
> Hmm, that would be tricky. How about loading only the first one
> found, and issue
> warnings about any duplicate namespaces?
This would most certainly cause confusion.
> A second option would be to detect this
> situation *before* loading any library, and loudly complain about
> it (i.e.,
> throw an exception) if there are duplicate namespaces.
This would result in a case where two component libs cannot be used
unless the two authors coordinate on who uses what namespace. Even
if it was configurable, you'd lose the "works out-of-the-box" feature.
I think a convention for namespace claiming would be more
appropriate, although I'm not sure what that convention would be.
--
Kevin
Re: component packaging
Posted by Marcus Brito <mb...@gmail.com>.
Kevin Menard <kmenard <at> servprise.com> writes:
> What do you propose should happen when two JARs set the same Tapestry-
> Component-Library value?
Hmm, that would be tricky. How about loading only the first one found, and issue
warnings about any duplicate namespaces? A second option would be to detect this
situation *before* loading any library, and loudly complain about it (i.e.,
throw an exception) if there are duplicate namespaces.
-- Marcus Brito
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: component packaging
Posted by Kevin Menard <km...@servprise.com>.
On Jul 25, 2005, at 12:06 PM, Marcus Brito wrote:
> At runtime, Tapestry would load all MANIFEST.MF files, and check if
> any of them
> contains Tapestry-Component-Library attributes, and automatically
> add any
> libraries found to the current application.
What do you propose should happen when two JARs set the same Tapestry-
Component-Library value?
--
Kevin
Re: component packaging
Posted by Marcus Brito <mb...@gmail.com>.
Yunfeng Hou <houyunf <at> yahoo.com> writes:
> At runtime, the tapestry servlet will create a context
> class loader with all these archives included, and all
> pages or components created by the servlet can have
> the correct classpath.
-1 to more classloader tricks. These component jars could be loaded from
WEB-INF/lib as everything else -- The tapestry runtime would look for something
on MANIFEST.MF or some other configuration file to figure out libraries.
Proposal: component jars could contain something like this on MANIFEST.MF
Tapestry-Component-Library: contrib;org/apache/tapestry/contrib/Contrib.library
i.e, for each component library, the MANIFEST should contain a
Tapestry-Component-Library attribute. The value of the attribute should be the
namespace, followed by a semicolon, followed by the path to the library
specification.
At runtime, Tapestry would load all MANIFEST.MF files, and check if any of them
contains Tapestry-Component-Library attributes, and automatically add any
libraries found to the current application.
-- Marcus Brito
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: component packaging
Posted by Yunfeng Hou <ho...@yahoo.com>.
That is right, I think these kind of packaging can
affect us at dev time and run time.
At dev time, we do not need add each library into
tapestry.application, what we need is to put the
archives into a well known directory, say,
WEB-INF/components, or being configured as servlet
parameter. Spindle can discover all components without
the help of tapestry.application.
At runtime, the tapestry servlet will create a context
class loader with all these archives included, and all
pages or components created by the servlet can have
the correct classpath.
Yunfeng Hou
--- Nick Westgate <ni...@key-planning.co.jp> wrote:
> Some kind of auto-discovery via the classloader you
> mean?
>
> Anything to help these tools would be great. I think
> greater
> ease of component sharing and Trails powered RAD
> would propel
> Tapestry into the market position it deserves.
>
> Cheers,
> Nick.
>
>
> Howard Lewis Ship wrote:
> > Actually, he was making some suggestions to go
> beyond what Tapestry
> > provides today, some of which would be useful to
> tools like Spindle
> > and Palette, or even to distro communities like
> Tacos.
> >
> > On 7/25/05, Nick Westgate
> <ni...@key-planning.co.jp> wrote:
> >
> >>Hi.
> >>
> >>Howard's book "Tapestry In Action" explains how to
> do this in
> >>chapter 6.9 "Packaging components into libraries".
> >>
> >>Components are (1) packaged in a jar, (2)
> specified in a
> >>".library" file, (3) included in the classpath and
> configured
> >>in the ".application" file, just like the contrib
> library
> >>(bundled with Tapestry) and the base library (from
> T-Deli).
> >>
> >>Cheers,
> >>Nick.
> >>
> >>
> >>Yunfeng Hou wrote:
> >>
> >>>I am thinking about that if Tapestry could have a
> >>>consistent component packaging mechanism, which
> will
> >>>ease the development, the usage and tools such as
> >>>spindle. Here's what I thought.
> >>>
> >>>1. components should be packaged into a jar file,
> or,
> >>>may be we can name it as tapestry archive(tar)
> :-)
> >>>2. components should have an entry in META-INF,
> just
> >>>as hivemind.xml, it will list all libabry files
> this
> >>>archive contains.
> >>>3. component archives can be put into
> >>>WEB-INF/components directory, this can be default
> or
> >>>be configured in tapestry.application file, or
> as
> >>>servlet parameter. I prefer the latter, since
> most the
> >>>time my tapestry.application file contains only
> the
> >>>library reference. I think tools like spindle can
> easy
> >>>find all components there.
> >>>4. tapestry servlet should have a context class
> loader
> >>>including these archives which can be referenced
> by
> >>>all pages it serves.
> >>>
> >>>
> >>>Yunfeng Hou
> >>>
> >>>
> >>>
> >>>
> >>>__________________________________
> >>>Do you Yahoo!?
> >>>Yahoo! Mail - You care about security. So do we.
> >>>http://promotions.yahoo.com/new_mail
> >>>
>
>>>---------------------------------------------------------------------
> >>>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
> >>
> >>
> >
> >
> >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
>
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: component packaging
Posted by Nick Westgate <ni...@key-planning.co.jp>.
Some kind of auto-discovery via the classloader you mean?
Anything to help these tools would be great. I think greater
ease of component sharing and Trails powered RAD would propel
Tapestry into the market position it deserves.
Cheers,
Nick.
Howard Lewis Ship wrote:
> Actually, he was making some suggestions to go beyond what Tapestry
> provides today, some of which would be useful to tools like Spindle
> and Palette, or even to distro communities like Tacos.
>
> On 7/25/05, Nick Westgate <ni...@key-planning.co.jp> wrote:
>
>>Hi.
>>
>>Howard's book "Tapestry In Action" explains how to do this in
>>chapter 6.9 "Packaging components into libraries".
>>
>>Components are (1) packaged in a jar, (2) specified in a
>>".library" file, (3) included in the classpath and configured
>>in the ".application" file, just like the contrib library
>>(bundled with Tapestry) and the base library (from T-Deli).
>>
>>Cheers,
>>Nick.
>>
>>
>>Yunfeng Hou wrote:
>>
>>>I am thinking about that if Tapestry could have a
>>>consistent component packaging mechanism, which will
>>>ease the development, the usage and tools such as
>>>spindle. Here's what I thought.
>>>
>>>1. components should be packaged into a jar file, or,
>>>may be we can name it as tapestry archive(tar) :-)
>>>2. components should have an entry in META-INF, just
>>>as hivemind.xml, it will list all libabry files this
>>>archive contains.
>>>3. component archives can be put into
>>>WEB-INF/components directory, this can be default or
>>>be configured in tapestry.application file, or as
>>>servlet parameter. I prefer the latter, since most the
>>>time my tapestry.application file contains only the
>>>library reference. I think tools like spindle can easy
>>>find all components there.
>>>4. tapestry servlet should have a context class loader
>>>including these archives which can be referenced by
>>>all pages it serves.
>>>
>>>
>>>Yunfeng Hou
>>>
>>>
>>>
>>>
>>>__________________________________
>>>Do you Yahoo!?
>>>Yahoo! Mail - You care about security. So do we.
>>>http://promotions.yahoo.com/new_mail
>>>
>>>---------------------------------------------------------------------
>>>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
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: component packaging
Posted by Howard Lewis Ship <hl...@gmail.com>.
Actually, he was making some suggestions to go beyond what Tapestry
provides today, some of which would be useful to tools like Spindle
and Palette, or even to distro communities like Tacos.
On 7/25/05, Nick Westgate <ni...@key-planning.co.jp> wrote:
> Hi.
>
> Howard's book "Tapestry In Action" explains how to do this in
> chapter 6.9 "Packaging components into libraries".
>
> Components are (1) packaged in a jar, (2) specified in a
> ".library" file, (3) included in the classpath and configured
> in the ".application" file, just like the contrib library
> (bundled with Tapestry) and the base library (from T-Deli).
>
> Cheers,
> Nick.
>
>
> Yunfeng Hou wrote:
> > I am thinking about that if Tapestry could have a
> > consistent component packaging mechanism, which will
> > ease the development, the usage and tools such as
> > spindle. Here's what I thought.
> >
> > 1. components should be packaged into a jar file, or,
> > may be we can name it as tapestry archive(tar) :-)
> > 2. components should have an entry in META-INF, just
> > as hivemind.xml, it will list all libabry files this
> > archive contains.
> > 3. component archives can be put into
> > WEB-INF/components directory, this can be default or
> > be configured in tapestry.application file, or as
> > servlet parameter. I prefer the latter, since most the
> > time my tapestry.application file contains only the
> > library reference. I think tools like spindle can easy
> > find all components there.
> > 4. tapestry servlet should have a context class loader
> > including these archives which can be referenced by
> > all pages it serves.
> >
> >
> > Yunfeng Hou
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail - You care about security. So do we.
> > http://promotions.yahoo.com/new_mail
> >
> > ---------------------------------------------------------------------
> > 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
Professional Tapestry training, mentoring, support
and project work. 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: component packaging
Posted by Nick Westgate <ni...@key-planning.co.jp>.
Hi.
Howard's book "Tapestry In Action" explains how to do this in
chapter 6.9 "Packaging components into libraries".
Components are (1) packaged in a jar, (2) specified in a
".library" file, (3) included in the classpath and configured
in the ".application" file, just like the contrib library
(bundled with Tapestry) and the base library (from T-Deli).
Cheers,
Nick.
Yunfeng Hou wrote:
> I am thinking about that if Tapestry could have a
> consistent component packaging mechanism, which will
> ease the development, the usage and tools such as
> spindle. Here's what I thought.
>
> 1. components should be packaged into a jar file, or,
> may be we can name it as tapestry archive(tar) :-)
> 2. components should have an entry in META-INF, just
> as hivemind.xml, it will list all libabry files this
> archive contains.
> 3. component archives can be put into
> WEB-INF/components directory, this can be default or
> be configured in tapestry.application file, or as
> servlet parameter. I prefer the latter, since most the
> time my tapestry.application file contains only the
> library reference. I think tools like spindle can easy
> find all components there.
> 4. tapestry servlet should have a context class loader
> including these archives which can be referenced by
> all pages it serves.
>
>
> Yunfeng Hou
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - You care about security. So do we.
> http://promotions.yahoo.com/new_mail
>
> ---------------------------------------------------------------------
> 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