Seconded - my company will not use Tapestry because of the constant
changes between versions. Its even starting to drive me away in favor
of WebObjects...
On Dec 28, 2007, at 5:59 PM, Emmanuel Sowah wrote:
Howard,
Well, left me alone, I would say instead of the effort to support
Portlets
Well, you can always make a portlet-container component. :)
Christian.
On 30-Dec-07, at 15:12 , Arve Klev wrote:
My vote is to portlet in T5.
Sincerely, Arve Klev
2007/12/29, Jan Vissers <[EMAIL PROTECTED]>:
Add me to the portlet petition;
Me too!
Add me to the portlet petition; we're
My vote is to portlet in T5.
Sincerely, Arve Klev
2007/12/29, Jan Vissers <[EMAIL PROTECTED]>:
>
> > Add me to the portlet petition;
>
> Me too!
>
> > Add me to the portlet petition; we're about to start development on a
> > portal
> > with Liferay and it would be great to have portlet support in
> Add me to the portlet petition;
Me too!
> Add me to the portlet petition; we're about to start development on a
> portal
> with Liferay and it would be great to have portlet support in T5.
>
> Regards,
>
> D
>
>
> On 12/28/07, Emmanuel Sowah <[EMAIL PROTECTED]> wrote:
>>
>> Howard,
>>
>> Well,
Add me to the portlet petition; we're about to start development on a portal
with Liferay and it would be great to have portlet support in T5.
Regards,
D
On 12/28/07, Emmanuel Sowah <[EMAIL PROTECTED]> wrote:
>
> Howard,
>
> Well, left me alone, I would say instead of the effort to support Port
Howard,
Well, left me alone, I would say instead of the effort to support Portlets
in T5, spend that in making T5 backward compatible to T4 and T3. You would
save many people a lot of misery in migrating.
E.
On Dec 28, 2007 11:24 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> It's really th
Hi,
Consider this as interest in having T5 support portlets. We are just about
starting porting a largish JSP-hell application to a proper CMS system plus
Tapestry and portlets, and I would very much like to see that we can jump
right onto T5.
To us, portlets are more important that AJAX (since w
It's really the other way around; a Portlet is defined in terms of a
T5 application, where the application pages are mapped to different
views of the portlet. A portal would contain many portlets, some T5
applications, some natively implemented.
On Dec 28, 2007 11:19 AM, Michael Lake <[EMAIL PROTE
would it be completely ridiculous for a T5 component to house a
portlet? is that at all feasible?
-mike
On Dec 28, 2007, at 2:06 PM, Howard Lewis Ship wrote:
Currently there are not plans to support Portlets in T5 for the
initial release. If there is enough interest, it will be added as a
Currently there are not plans to support Portlets in T5 for the
initial release. If there is enough interest, it will be added as a
follow on. It will be much easier to add to T5 than it was to T4,
since a lot of the ideas in T5 came from T4 and its portlet support.
such as the action request / ren
I can't seem to find a reference in the documentation.
I know Tapestry4 at least covers 168
What are the plans for covering JSR 286 Portlet 2.0 spec?
Carlos
11 matches
Mail list logo
