Hi Michal, thanks for reporting these two problems! I applied your patch and fixed the serializer the way you suggested. Could you please verify and then close the bugs? Thanks
Thanks Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.osoco.net/weblogs/rael/ > -----Original Message----- > From: DURDINA Michal [mailto:[EMAIL PROTECTED] > Sent: Monday, March 15, 2004 9:37 AM > To: [EMAIL PROTECTED] > Subject: RE: [portal] JSR168 portlets problems under PortalEngine > > Hi, > I found some more issues about running JSR-168 portlets in > the Cocoon Portal. > > 1. There is one serious problem with IncludingHTMLSerializer > when serializing 2 and more portlets whose are interleaved > with bigger amount of HTML markup. Serialization is carried > out in blocks of 8Kb and ReplacingOutputStream.write is > called after every block is ready. The portlet iterator > created from the orderedPortletList on the first call of > writeNext() is later broken by following calls of > orderedPortletList.add() when more portlets are being added > to the orderedPortletList at startElement(). As a result the > java.util.ConcurrentModification exception occurs on the next > call of valueIterator.next(). > More at bug description: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=27657 > > 2. Pluto container embedded in Cocoon Portal requires several > services (SPI) to be implemented by portal. > PropertyManagerService service is used for setting and > getting vendor specific information by portlets via > PortletResponse.setProperty(), but this service is not > implemented by Cocoon Portal. That would be ok because this > service is optional but cocoon throws > CascadingRuntimeException "Unable to lookup service > org.apache.pluto.services.property.PropertyManagerService > key" what prevents portlet to be started. > > http://issues.apache.org/bugzilla/show_bug.cgi?id=27658 > > Michal > >
