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
-
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
, March 15, 2004 11:39 AM
To: [EMAIL PROTECTED]
Subject: RE: [portal] JSR168 portlets problems under PortalEngine
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
...
1. test2.jsp: Call to
portalContext.getSupportedWindowStates() returns null.
I fixed this (hopefully) yesterday morning in the CVS.
Haven't got chance to test it again. After I updated my whole cocoon-distribution from
CVS and build clean webapplication only with portal-block
Hi,
I found some problems while running jakarta-pluto testsuite under CocoonPortalEngine.
I would like to report them and offer help if needed.
1. test2.jsp: Call to portalContext.getSupportedWindowStates() returns null.
2. test2.jsp: Call to renderRequest.getParameter(testName) returns null
Michal Durdina wrote:
Hi,
I found some problems while running jakarta-pluto testsuite
under CocoonPortalEngine. I would like to report them and
offer help if needed.
Great, really appreciated!
1. test2.jsp: Call to
portalContext.getSupportedWindowStates() returns null.
I fixed
