Thanks for that clarification. On that note, are there any clear, concise examples of bundling the portlet container in a web app?
-- jim On Fri, Jul 23, 2010 at 8:11 PM, Eric Dalquist <[email protected]>wrote: > I believe the container portion of pluto has support but it must be > implemented by the portal. The pluto driver is the little example portal for > pluto and it does not implement the container apis needed for this feature. > > -Eric > > > On 7/23/10 11:07 AM, James Cook wrote: > > Just seems a little strange that the "Reference Implementation" doesn't > support _all_ of the optional features of a spec. > > Thanks for the heads up. > > -- jim > > On Fri, Jul 23, 2010 at 1:15 PM, Woonsan Ko <[email protected]> wrote: > >> Hi James, >> >> Currently, Pluto doesn't support the portlet head element contribution >> which is an *optional* feature of Portlet 2.0. >> By the way, Jetspeed-2.2 supports that feature. >> >> Regards, >> >> Woonsan >> >> >> *From:* James Cook <[email protected]> >> *To:* [email protected] >> *Sent:* Fri, July 23, 2010 6:06:14 AM >> *Subject:* Support for Markup in Head >> >> I am not sure if I am doing something wrong, or whether Pluto does not >> support the full JSR-286 specification. I am trying to inject content into >> the head section of my portal page. I have implemented doHeaders() and >> confirmed that my code works on Liferay portal. >> >> When I ask pluto's PortalContext to reply with the value of the >> MimeResponse.MARKUP_HEAD_ELEMENT property, it reports "null". >> >> Does this mean that Pluto does not support this feature? >> >> >> >> >
