Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 44130 invoked from network); 15 Mar 2004 08:37:31 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Mar 2004 08:37:31 -0000 Received: (qmail 45505 invoked by uid 500); 15 Mar 2004 08:37:04 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 45350 invoked by uid 500); 15 Mar 2004 08:37:03 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 45335 invoked from network); 15 Mar 2004 08:37:03 -0000 Received: from unknown (HELO fwlin.asset.sk) (195.28.83.3) by daedalus.apache.org with SMTP; 15 Mar 2004 08:37:03 -0000 Received: from s2-ba.asset-internal (s2-ba.asset-internal [172.16.51.1]) by fwlin.asset.sk (Postfix) with ESMTP id 0F7A84A755 for ; Mon, 15 Mar 2004 09:23:53 +0100 (CET) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Subject: RE: [portal] JSR168 portlets problems under PortalEngine Date: Mon, 15 Mar 2004 09:37:15 +0100 Message-ID: <4C47FFB0CC6A2E4D92550B89B68FC7830170C2D2@s2-ba.asset-internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [portal] JSR168 portlets problems under PortalEngine Thread-Index: AcQC10kMr5+jPdSqTM2RdBzKds2giwABz+2gAJNBu3ABTILJoA== From: "DURDINA Michal" To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, I found some more issues about running JSR-168 portlets in the Cocoon = Portal.=20 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().=20 More at bug description: http://issues.apache.org/bugzilla/show_bug.cgi?id=3D27657 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=3D27658 Michal