Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <dev@cocoon.apache.org>
Subject: RE: [portal] JSR168 portlets problems under PortalEngine
Date: Fri, 5 Mar 2004 19:24:01 +0100
Organization: S&N AG
MIME-Version: 1.0
In-Reply-To: <4C47FFB0CC6A2E4D92550B89B68FC78391F0BF@s2-ba.asset-internal>
Thread-Index: AcQC10kMr5+jPdSqTM2RdBzKds2giwABz+2g
Message-ID: <OF0DB1DCB2.D772B7BF-ONC1256E4E.00646961@sundn.de>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset="iso-8859-1"

Michal Durdina wrote:=20
>=20
> Hi,
> I found some problems while running jakarta-pluto testsuite=20
> under CocoonPortalEngine. I would like to report them and=20
> offer help if needed.
>=20
Great, really appreciated!

> 1. test2.jsp: Call to=20
> portalContext.getSupportedWindowStates() returns null.
>=20
I fixed this (hopefully) yesterday morning in the CVS.

> 2. test2.jsp: Call to renderRequest.getParameter("testName")=20
> returns null after 2.nd and every other render() was called.=20
> Portlet container should preserve request parameters sent=20
> upon 1.st request for every subsequent call of render() in=20
> the portlet which was not target of the subsequent client=20
> request (JSR-168spec chap. 11.1.1 =A73). But jakarta-pluto is=20
> also doing this, so it's not exactly cocoon problem.=20
>=20
Did you test the latest pluto version?

> 3. test3.jsp: Submit to url created by=20
> renderResponse.createRenderURL();=20
> url.setWindowState(WindowState.MAXIMIZED); changes correctly=20
> return value of renderRequest.getWindowState() to=20
> "maximized", but the portlet window actually does not=20
> maximize. By contrast when submit to url with=20
> WindowState.MINIMIZED is executed, the portlet windows=20
> minimizes but stays minimized forever - I could not get it to=20
> normal size by clicking window icons.
>=20
> 4. test4.jsp: Simmilar to point 2. but at this time=20
> parameters set by _action_ are not preserved. When testing in=20
> jakarta-pluto, they are.
>=20
> My testing env:
> cocoon-portal block build from CVS (04.march.2003)=20
> jakarta-testuite built from CVS (04.march.2003)
>=20
Thanks for reporting this! I think the best way is if you file bugs
into bugzilla. Please enter a bug to the Cocoon bugs if the
problem is only with the Cocoon portal and to Pluto's bug list
if the bug is in Pluto as well.

I will try to update the version of Pluto used in Cocoon to the
latest version in the next days and then have a look at the bugs
you described.

Many thanks!

Carsten