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]
