Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-30 Thread Arve Klev
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 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
  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 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 PROTECTED] wrote:
   
   
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
 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 / render request split present in T5
  (and
 in portlets).

 On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
 [EMAIL PROTECTED] wrote:
 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




 --
 Howard M. Lewis Ship

 Creator Apache Tapestry and Apache HiveMind


  -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

   
   
   
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
  
   --
   Howard M. Lewis Ship
  
   Creator Apache Tapestry and Apache HiveMind
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
 
 
  --
  What the world needs is more geniuses with humility, there are so few
 of
  us
  left.
  Oscar Levant
 



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-30 Thread Christian Edward Gruber

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 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
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 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 PROTECTED] wrote:



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
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 / render request split present in T5

(and

in portlets).

On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
[EMAIL PROTECTED] wrote:

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





--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind



-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








--
What the world needs is more geniuses with humility, there are so  
few

of

us
left.
Oscar Levant





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-30 Thread Craig St Jean
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
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 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 PROTECTED] wrote:



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
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 / render request split present in T5  
(and

in portlets).

On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
[EMAIL PROTECTED] wrote:

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





--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-29 Thread Jan Vissers
 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, 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 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 PROTECTED] wrote:
  
  
   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
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 / render request split present in T5
 (and
in portlets).
   
On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
[EMAIL PROTECTED] wrote:
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
   
   
   
   
--
Howard M. Lewis Ship
   
Creator Apache Tapestry and Apache HiveMind
   
   
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
 
  --
  Howard M. Lewis Ship
 
  Creator Apache Tapestry and Apache HiveMind
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 




 --
 What the world needs is more geniuses with humility, there are so few of
 us
 left.
 Oscar Levant




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-28 Thread Howard Lewis Ship
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 / render request split present in T5 (and
in portlets).

On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
[EMAIL PROTECTED] wrote:
 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




-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-28 Thread Michael Lake



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
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 / render request split present in T5 (and
in portlets).

On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
[EMAIL PROTECTED] wrote:

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





--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-28 Thread Howard Lewis Ship
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 PROTECTED] wrote:


 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
  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 / render request split present in T5 (and
  in portlets).
 
  On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
  [EMAIL PROTECTED] wrote:
  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
 
 
 
 
  --
  Howard M. Lewis Ship
 
  Creator Apache Tapestry and Apache HiveMind
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-28 Thread Olle Hallin
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 we don't have much of
that in the current app anyway).

Regards,
Olle Hallin

2007/12/28, Howard Lewis Ship [EMAIL PROTECTED]:

 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 PROTECTED] wrote:
 
 
  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
   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 / render request split present in T5 (and
   in portlets).
  
   On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
   [EMAIL PROTECTED] wrote:
   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
  
  
  
  
   --
   Howard M. Lewis Ship
  
   Creator Apache Tapestry and Apache HiveMind
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 



 --
 Howard M. Lewis Ship

 Creator Apache Tapestry and Apache HiveMind

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Olle Hallin M.Sc.
+46 70 6653071
[EMAIL PROTECTED]
www.hit.se


Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-28 Thread Emmanuel Sowah
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 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 PROTECTED] wrote:
 
 
  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
   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 / render request split present in T5 (and
   in portlets).
  
   On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
   [EMAIL PROTECTED] wrote:
   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
  
  
  
  
   --
   Howard M. Lewis Ship
  
   Creator Apache Tapestry and Apache HiveMind
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 



 --
 Howard M. Lewis Ship

 Creator Apache Tapestry and Apache HiveMind

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Does Tapestry5 support Portlets specs JSR168 and 286

2007-12-28 Thread DarĂ­o Vasconcelos
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 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 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 PROTECTED] wrote:
  
  
   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
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 / render request split present in T5 (and
in portlets).
   
On Dec 28, 2007 10:09 AM, Cardenas, Juan Carlos
[EMAIL PROTECTED] wrote:
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
   
   
   
   
--
Howard M. Lewis Ship
   
Creator Apache Tapestry and Apache HiveMind
   
   
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
 
  --
  Howard M. Lewis Ship
 
  Creator Apache Tapestry and Apache HiveMind
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 




-- 
What the world needs is more geniuses with humility, there are so few of us
left.
Oscar Levant