This seems to perpetually be something "in the next release". It isn't a significant amount of code, but its a lot of work to test. Since it hasn't been a priority for any of my clients, I haven't been able to justify working on it.
The interesting thing is that significant amounts of Tapestry are organized to cleanly support portlets, borrowing from the design of Tapestry 4.0. For example, the prime reason Tapestry has its own internal Request object is to abstract away from direct dependencies on the Servlet API (there will be an implementation of Request for API). 2010/11/1 françois facon <fra.fa...@gmail.com> > Hello Marcos, > > The last post about portlet support in tapestry 5 was made by Markus > Feindler. > > http://www.mail-archive.com/users@tapestry.apache.org/msg42770.html > > François > > 2010/11/1 Marcos Mainar <marcosmai...@gmail.com> > > > Dear Tapestry users, > > > > I wanted to ask if there is any kind of official or non-official portlet > > development support in Tapestry 5. I have seen that Tapestry 4 had > portlet > > development support but I haven't been able to find any portlet support > for > > Tapestry 5. > > > > Thank you, > > > > Marcos > > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
