Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: Inconsistent behavior of session handling
Date: Mon, 11 Jul 2005 10:34:54 +0200
Message-ID: 
 <4202DDA3828BD24D9381128D46B13D2B01ED87CD@ktaemail01.villa-bosch.de>
Thread-Topic: Inconsistent behavior of session handling
Thread-Index: AcWERvIM5IA4gLstT+CAaefGuU9vxQBq4zHw
From: "Messing, Elad" <elad.messing@eml-d.villa-bosch.de>
To: <dev@cocoon.apache.org>

Thank you Reinhard ! Words perfect now :)

Is it documented somewhere  ?=20
Should I expect a change soon, so that I will have to change everything =
back to coccon.session.blah ?=20

Thanks!
Elad

-----Urspr=FCngliche Nachricht-----
Von: Reinhard Poetz [mailto:reinhard@apache.org]=20
Gesendet: Samstag, 9. Juli 2005 07:28
An: dev@cocoon.apache.org
Betreff: Re: Inconsistent behavior of session handling

Messing, Elad wrote:
> Hello all
> 	I have encountered an inconsistent behavior of cocoon in relation to=20
> session handling.
> 	First I had this in my sitemap :
>=20
>       <map:match pattern=3D"session">
>         <map:act type=3D"session">
>           <map:parameter name=3D"action" value=3D"create"/>
>         </map:act>
>         <map:call function=3D"testSession"/>
>       </map:match>
>       <map:match pattern=3D"session.html">
>         <map:generate type=3D"jx" src=3D"content/session.html"/>
>         <map:serialize/>
>       </map:match>
> =09
> 	testSession:
>=20
> 	function testSession(){
> 		cocoon.sendPage("session.html");
> 	}
>=20
> 	and in session.html I used JX to print the some session
> information:
> 	${cocoon.session.getAttribute("elad")}
> 	${cocoon.session.creationTime}
>=20
> 	Everything works fine.
>=20
>=20
> 	When I change the sitemap to :
>       <map:match pattern=3D"session">
>         <map:act type=3D"session">
>           <map:parameter name=3D"action" value=3D"create"/>
>         </map:act>
>         <map:generate type=3D"jx" src=3D"content/session.html"/>
>         <map:serialize/>
>       </map:match>
>=20
> 	I get the session.html file empty.. Like the session is not there=20
> anymore because I didn't go through flow script ??
>=20
> 	Is this a bug ? Feature ?


I guess it's not a bug in Cocoon session handling but a problem with an =
inconsistency in the not-refactored version of jx-template. your example =
should work fine with jx-template in trunk but not with jx-template in =
2.1. there you should try ${session.getAttribute("elad")} instead of =
${cocoon.session.getAttribute("elad")}.

HTH

--=20
Reinhard P=F6tz           Independent Consultant, Trainer & (IT)-Coach=20

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------