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/10/08 12:22:41 UTC
Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Hallo!
I'm sure that this question is likely to be one that only Howard & the
Tapestry framework developers can answer:
Is there already a timeline for the first (beta/rc?) releases of
Tapestry 3.1?
Moreover how good are the chances that Tapestry 3.1 can interact with
the Java Portal specification, respectively work e.g. with the eXo platform?
Cheers,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Michael Echerer <me...@tngtech.com>.
Erik Hatcher wrote:
> your sleeves and implement it. I suspect it is not a high priority for
> Howard, nor is it for me and apparently not for the other current
> committers.
Thanks, that all I like to know.
Cheers,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Lars Hoss <wo...@acidware.net>.
Hi!
> I do believe that supporting JSR-168 is one of the more important
> things for Tapestry to do. One requirement that constantly pops up
> forcing projects back to Struts is current or future support for a
> Portal. Not so much that all web apps need to be portals, but
> companies don't want to burn that bridge by developing web apps in
> Tapestry.
Indeed! In fact we many of our customers these days are asking for
portal based solutions for it allows the integration of various
applications into one central place. Therefore it would be very nice to
be able to embed Tapestry applications as portlets.
Yours,
Lars
--
"Stil ist die Fähigkeit, komplizierte Dinge einfach zu sagen - nicht
umgekehrt." -- Cocteau, Jean
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Adam Greene <ag...@iq-2000.com>.
I have looked at Pluto as a Portal container, and it conceptually it
wouldn't be hard to get it to work within Tapestry, it consists of 3
parts and 2 of the 3 parts are just api's and the final one is the
actual presentation engine. It would need to be adapted to work within
Tapestry. I plan on doing that eventually (next year around May
probably, unless someone beats me to it).
Vince Marco wrote:
> I would think that at a high level the basic needed steps would be a
> version of the ApplicationServlet extending the GenericPortlet class,
> and perhaps a PortletShell component. That is probably simplifying
> things too much, but seem like the basic steps.
>
> I do believe that supporting JSR-168 is one of the more important
> things for Tapestry to do. One requirement that constantly pops up
> forcing projects back to Struts is current or future support for a
> Portal. Not so much that all web apps need to be portals, but
> companies don't want to burn that bridge by developing web apps in
> Tapestry.
>
> Vince
>
> On Oct 13, 2004, at 3:33 PM, Mikaël Cluseau wrote:
>
>> From the spec., all I see is that (conceptualy) components *are*
>> portlets, Tapestry is the portlet container and the Page is the
>> aggregation layer (the portal). It just seems to me that the spec. is
>> a Tapestry application limited to one page containing many components
>> and constrained to their API.
>
>
>
> ---------------------------------------------------------------------
> 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: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Vince Marco <vm...@mac.com>.
I would think that at a high level the basic needed steps would be a
version of the ApplicationServlet extending the GenericPortlet class,
and perhaps a PortletShell component. That is probably simplifying
things too much, but seem like the basic steps.
I do believe that supporting JSR-168 is one of the more important
things for Tapestry to do. One requirement that constantly pops up
forcing projects back to Struts is current or future support for a
Portal. Not so much that all web apps need to be portals, but
companies don't want to burn that bridge by developing web apps in
Tapestry.
Vince
On Oct 13, 2004, at 3:33 PM, Mikaël Cluseau wrote:
> From the spec., all I see is that (conceptualy) components *are*
> portlets, Tapestry is the portlet container and the Page is the
> aggregation layer (the portal). It just seems to me that the spec. is
> a Tapestry application limited to one page containing many components
> and constrained to their API.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Lars Hoss <wo...@acidware.net>.
Tapestry components are indeed some kind of portlets though they are
not JSR168 portlets. According to the JSR168 a portlet is a class that
implements the Portlet interface (or derives from GenericPortlet).
Furthermore a portlet is packaged into a typical WAR file with an
additional "portlet.xml" file besides the web.xml file. The Pluto
portlet container (portlets.apache.org/pluto) for example deploys
portlets by enhancing the web.xml of the portlet WAR by adding a
special wrapper servlet to the web.xml. A special WAR contains a sample
implementation of a portal (the portlet aggregator) that aggregates the
response output of all wrapper servlets into one page.
For Tapestry we only need a class that implements the portlet interface
and "wraps" a Tapestry application into a portlet. In order to use a
Tapestry application as a portlet certain requirements must be taken
into account. For example the application should not generate a
complete HTML document but only a "fragment".
Yours,
Lars
Am 13.10.2004 um 23:33 schrieb Mikaël Cluseau:
> From the spec., all I see is that (conceptualy) components *are*
> portlets, Tapestry is the portlet container and the Page is the
> aggregation layer (the portal). It just seems to me that the spec. is
> a Tapestry application limited to one page containing many components
> and constrained to their API.
>
> Lars Hoss wrote:
>
>> Hi Howard,
>>
>> I did not mean to offend you. What I wanted to say is that
>> _generally_ it shouldn't be too complicated for writing portlets in
>> general isn't complicated. Whoever want's to write a portlet proxy
>> :-)
>>
>> Yours,
>> Lars
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
"Stil ist die Fähigkeit, komplizierte Dinge einfach zu sagen - nicht
umgekehrt." -- Cocteau, Jean
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Mikaël Cluseau <nw...@nwrk.dyndns.org>.
From the spec., all I see is that (conceptualy) components *are*
portlets, Tapestry is the portlet container and the Page is the
aggregation layer (the portal). It just seems to me that the spec. is a
Tapestry application limited to one page containing many components and
constrained to their API.
Lars Hoss wrote:
> Hi Howard,
>
> I did not mean to offend you. What I wanted to say is that _generally_
> it shouldn't be too complicated for writing portlets in general isn't
> complicated. Whoever want's to write a portlet proxy :-)
>
> Yours,
> Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Lars Hoss <wo...@acidware.net>.
Hi Howard,
I did not mean to offend you. What I wanted to say is that _generally_
it shouldn't be too complicated for writing portlets in general isn't
complicated. Whoever want's to write a portlet proxy :-)
Yours,
Lars
Am 12.10.2004 um 19:58 schrieb Howard Lewis Ship:
> If you read the CVS commit notices, I've been very busy on Tapestry
> 3.1 of late ... but it is squeezing it around the edges of my full
> time work.
>
> I do want to learn about the Portlet API and see how to leverage that
> for Tapestry. 3.1? 3.2? Hard to say. I think Tapestry might be a
> great way to create portlets, but I've never created a portlet myself,
> so I don't know what the constraints are.
>
> Tapestry 3.1 is going to be luminous, with our without the portlet
> connection.
>
>
> On Tue, 12 Oct 2004 18:42:56 +0200, Lars Hoss <wo...@acidware.net>
> wrote:
>> We are currently playing around with Portlets though not Tapestry
>> related however. But I think that it shouldn't be too complicated to
>> write a Portlet-Prox y for Tapestry-Applications.
>>
>> Yours,
>> Lars
>>
>> Am 10.10.2004 um 01:09 schrieb Erik Hatcher:
>>
>>
>>
>>>
>>> On Oct 9, 2004, at 2:11 PM, Michael Echerer wrote:
>>>> I just don't know if portlets are as likely to happend like e.g.
>>>> Hivemind in Tapestry 3.1.
>>>>
>>> [...]
>>>>
>>>> Thus still open question: Tapestry 3.x and Portlet/eXo support? -
>>>> Possible or even planned?
>>>
>>> Jakarta is a meritocracy and an open-source community. The mantra
>>> being "scratch your own itch". So, if folks need portlet support,
>>> roll up your sleeves and implement it. I suspect it is not a high
>>> priority for Howard, nor is it for me and apparently not for the
>>> other
>>> current committers.
>>>
>>> All of the committers came on board by being proactive and bringing
>>> solutions back to the community. Discussing implementation details
>>> is
>>> fair game for the tapestry-dev list - I'm sure others would be more
>>> than happy to review design approaches.
>>>
>>> While the wiki plans make for a great roadmap, all you can truly rely
>>> on is what you can checkout from CVS HEAD.
>>>
>>> So, without further ado.... scratch your itches!
>>>
>>> Erik
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>>
>>>
>> --
>> "Stil ist die Fähigkeit, komplizierte Dinge einfach zu sagen - nicht
>> umgekehrt." -- Cocteau, Jean
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
--
"Stil ist die Fähigkeit, komplizierte Dinge einfach zu sagen - nicht
umgekehrt." -- Cocteau, Jean
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Howard Lewis Ship <hl...@gmail.com>.
If you read the CVS commit notices, I've been very busy on Tapestry
3.1 of late ... but it is squeezing it around the edges of my full
time work.
I do want to learn about the Portlet API and see how to leverage that
for Tapestry. 3.1? 3.2? Hard to say. I think Tapestry might be a
great way to create portlets, but I've never created a portlet myself,
so I don't know what the constraints are.
Tapestry 3.1 is going to be luminous, with our without the portlet connection.
On Tue, 12 Oct 2004 18:42:56 +0200, Lars Hoss <wo...@acidware.net> wrote:
> We are currently playing around with Portlets though not Tapestry
> related however. But I think that it shouldn't be too complicated to
> write a Portlet-Prox y for Tapestry-Applications.
>
> Yours,
> Lars
>
> Am 10.10.2004 um 01:09 schrieb Erik Hatcher:
>
>
>
> >
> > On Oct 9, 2004, at 2:11 PM, Michael Echerer wrote:
> >> I just don't know if portlets are as likely to happend like e.g.
> >> Hivemind in Tapestry 3.1.
> >>
> > [...]
> >>
> >> Thus still open question: Tapestry 3.x and Portlet/eXo support? -
> >> Possible or even planned?
> >
> > Jakarta is a meritocracy and an open-source community. The mantra
> > being "scratch your own itch". So, if folks need portlet support,
> > roll up your sleeves and implement it. I suspect it is not a high
> > priority for Howard, nor is it for me and apparently not for the other
> > current committers.
> >
> > All of the committers came on board by being proactive and bringing
> > solutions back to the community. Discussing implementation details is
> > fair game for the tapestry-dev list - I'm sure others would be more
> > than happy to review design approaches.
> >
> > While the wiki plans make for a great roadmap, all you can truly rely
> > on is what you can checkout from CVS HEAD.
> >
> > So, without further ado.... scratch your itches!
> >
> > Erik
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
> --
> "Stil ist die Fähigkeit, komplizierte Dinge einfach zu sagen - nicht
> umgekehrt." -- Cocteau, Jean
>
>
>
>
> ---------------------------------------------------------------------
> 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: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Lars Hoss <wo...@acidware.net>.
We are currently playing around with Portlets though not Tapestry
related however. But I think that it shouldn't be too complicated to
write a Portlet-Prox y for Tapestry-Applications.
Yours,
Lars
Am 10.10.2004 um 01:09 schrieb Erik Hatcher:
>
> On Oct 9, 2004, at 2:11 PM, Michael Echerer wrote:
>> I just don't know if portlets are as likely to happend like e.g.
>> Hivemind in Tapestry 3.1.
>>
> [...]
>>
>> Thus still open question: Tapestry 3.x and Portlet/eXo support? -
>> Possible or even planned?
>
> Jakarta is a meritocracy and an open-source community. The mantra
> being "scratch your own itch". So, if folks need portlet support,
> roll up your sleeves and implement it. I suspect it is not a high
> priority for Howard, nor is it for me and apparently not for the other
> current committers.
>
> All of the committers came on board by being proactive and bringing
> solutions back to the community. Discussing implementation details is
> fair game for the tapestry-dev list - I'm sure others would be more
> than happy to review design approaches.
>
> While the wiki plans make for a great roadmap, all you can truly rely
> on is what you can checkout from CVS HEAD.
>
> So, without further ado.... scratch your itches!
>
> Erik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
"Stil ist die Fähigkeit, komplizierte Dinge einfach zu sagen - nicht
umgekehrt." -- Cocteau, Jean
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Oct 9, 2004, at 2:11 PM, Michael Echerer wrote:
> I just don't know if portlets are as likely to happend like e.g.
> Hivemind in Tapestry 3.1.
>
[...]
>
> Thus still open question: Tapestry 3.x and Portlet/eXo support? -
> Possible or even planned?
Jakarta is a meritocracy and an open-source community. The mantra
being "scratch your own itch". So, if folks need portlet support, roll
up your sleeves and implement it. I suspect it is not a high priority
for Howard, nor is it for me and apparently not for the other current
committers.
All of the committers came on board by being proactive and bringing
solutions back to the community. Discussing implementation details is
fair game for the tapestry-dev list - I'm sure others would be more
than happy to review design approaches.
While the wiki plans make for a great roadmap, all you can truly rely
on is what you can checkout from CVS HEAD.
So, without further ado.... scratch your itches!
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Michael Echerer <me...@tngtech.com>.
Vjeran Marcinko wrote:
>>I'm sure that this question is likely to be one that only Howard & the
>>Tapestry framework developers can answer:
>>
>>Is there already a timeline for the first (beta/rc?) releases of
>>Tapestry 3.1?
>>
>>Moreover how good are the chances that Tapestry 3.1 can interact with
>>the Java Portal specification, respectively work e.g. with the eXo
>
> platform?
>
> Don't mean to start any flame wars here, but for me, portlet support is by
> far the least attractive feature that could get included in Tapestry.
I wouldn't ask, if this wasn't interesting for us respectivly customers!
Moreover it is already mentioned as "proposal" in the Tapestry twiki.
I just don't know if portlets are as likely to happend like e.g.
Hivemind in Tapestry 3.1.
> I also talked with some java developers that mention portlet specs like true
> example of "another one" specification out there, and not knowing anyone
> interested in it ... Maybe I'm just surrounded with these kind of
> people...;)
Well, I AM a Java & Tapestry developer and do not only talk to some ;-)
Certainly it's one more spec, but customers are definitely interested in
Portal solutions, if they don't have them yet.
So why should they have to take Struts and Portlets, instead of Tapestry?
> BTW. I'm not tapestry developer.
>
> -Vjeran
Thus still open question: Tapestry 3.x and Portlet/eXo support? -
Possible or even planned?
Cheers,
Michael
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
Posted by Vjeran Marcinko <vj...@tis.hr>.
----- Original Message -----
From: "Michael Echerer" <me...@tngtech.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Friday, October 08, 2004 12:22 PM
Subject: Release plan for Tapestry 3.1? Portal spec/eXo platform supported?
> Hallo!
>
> I'm sure that this question is likely to be one that only Howard & the
> Tapestry framework developers can answer:
>
> Is there already a timeline for the first (beta/rc?) releases of
> Tapestry 3.1?
>
> Moreover how good are the chances that Tapestry 3.1 can interact with
> the Java Portal specification, respectively work e.g. with the eXo
platform?
Don't mean to start any flame wars here, but for me, portlet support is by
far the least attractive feature that could get included in Tapestry.
I also talked with some java developers that mention portlet specs like true
example of "another one" specification out there, and not knowing anyone
interested in it ... Maybe I'm just surrounded with these kind of
people...;)
BTW. I'm not tapestry developer.
-Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org