Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: [Portal engine] Portal doesn't pass all parameters
Date: Thu, 16 Sep 2004 11:13:23 +0200
Message-ID: <5E091A68F794974CAF431CA31F5AF2CC11E96D@server.bizzdesign.nl>
Thread-Topic: [Portal engine] Portal doesn't pass all parameters
Thread-Index: AcSbzWsEXtRXyICdRwuxKxUFxqGoCg==
From: "Bart Molenkamp" <b.molenkamp@bizzdesign.nl>
To: <dev@cocoon.apache.org>

Hi,

I want to use flow-applications inside coplets, and I do it exactly the
same as demonstrated in the portal sample. But not all parameters are
passed by the portal engine to the destination URI (the one in the
coplet attribute temporary:application-uri).

E.g.
path/to/my/uri?boolean		-- the "boolean" is not passed by the
coplet
path/to/my/uri?boolean=3Dtrue	-- works fine.

As you can see I want to pass a boolean value: if the parameter is
there, it is true, otherwise it is false. But in the portal it's always
false, as the parameter isn't passed. Both scenario's work fine when
running the flow applications outside of the portal engine.

Is this a bug, or is this way of passing parameters "illegal"?? As said
before, the second option works so there is no real problem, I'm just
curious :)

Bart.