[TRINIDAD] Portlet 2.0 compatibility

2009-04-21 Thread Scott O'Bryan
Hey everyone, I completed a migration to Trinidad to allow it to work with either Portlet 1.0 or Portlet 2.0. Portlet 2.0 containers will support AJAX. So here is my problem. In order to support extra functionality of Portlet 2.0, I need to compile against a Portlet 2.0 container. Most of

Re: [TRINIDAD] Portlet 2.0 compatibility

2009-09-24 Thread Hiren Sheth
e extra jar to be added to their web-inf.lib. > > It is a LOT harder to support portlet 1.0 by default and add a jar for > portlet 2.0 because of the way the architecture works. Possible, but > hard. > > Please let me know if either of these options sounds acceptabl

Re: [TRINIDAD] Portlet 2.0 compatibility

2009-09-24 Thread Kito Mann
2009/4/21 Scott O'Bryan > Yes I agree Matthias. Anyone else have a contrary opinion? I agree as well. > > > Matthias Wessendorf wrote: > >> On Tue, Apr 21, 2009 at 10:23 AM, Scott O'Bryan >> wrote: >> >> >>> Hey everyone, >>> >>> I completed a migration to Trinidad to allow it to work with e

Re: [TRINIDAD] Portlet 2.0 compatibility

2009-09-29 Thread michael freedman
The TrinidadDemo that is included in TrinidadExample distribution download on the MyFaces/Trinidad site runs against the current version of the Portlet 2.0 bridge. There are some problems -- mostly related to lack of Trinidad pop-up support in the portlet environment which the example relies o

Re: [TRINIDAD] Portlet 2.0 compatibility

2009-04-21 Thread Matthias Wessendorf
On Tue, Apr 21, 2009 at 10:23 AM, Scott O'Bryan wrote: > Hey everyone, > > I completed a migration to Trinidad to allow it to work with either Portlet > 1.0 or Portlet 2.0.  Portlet 2.0 containers will support AJAX. > > So here is my problem.  In order to support extra functionality of Portlet > 2

Re: [TRINIDAD] Portlet 2.0 compatibility

2009-04-21 Thread Scott O'Bryan
Yes I agree Matthias. Anyone else have a contrary opinion? Matthias Wessendorf wrote: On Tue, Apr 21, 2009 at 10:23 AM, Scott O'Bryan wrote: Hey everyone, I completed a migration to Trinidad to allow it to work with either Portlet 1.0 or Portlet 2.0. Portlet 2.0 containers will support A