cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorg Heymans <Jorg.Heym...@12snap.com>
Subject RE: Custom serializers and session
Date Wed, 30 Jul 2003 14:29:40 GMT
Maybe it's more sort of a way of enforcing certain design rules upon the
cocoon developer. The serializer should really only be responsible for
serializing what it receives from the pipeline it seems, application logic
should be moved up the pipeline instead of at the end. I'm not sure really
what the design constraint is for this
 
 
-----Original Message-----
From: Carmona Perez, David [mailto:DPerezCar@fcc.es] 
Sent: Mittwoch, 30. Juli 2003 16:00
To: users@cocoon.apache.org
Subject: RE: Custom serializers and session
 
Yes, that's a solution, but it's a pity that serializers are 2nd class
citizens in Cocoon!.
 
--------
David
 
-----Mensaje original-----
De: Jorg Heymans [mailto:Jorg.Heymans@12snap.com]
Enviado el: miƩrcoles, 30 de julio de 2003 15:38
Para: 'users@cocoon.apache.org'
Asunto: RE: Custom serializers and session
 
Can't you access your session in a custom generator or transformer and
insert the information you want into the SAX stream that is being passed to
the serializer?
 
 
Just a guess ...
 
-----Original Message-----
From: Carmona Perez, David [mailto:DPerezCar@fcc.es] 
Sent: Mittwoch, 30. Juli 2003 15:23
To: users@cocoon.apache.org
Subject: Custom serializers and session
 
Dear Cocooners,
 
As serializers doesn't implement the interface  SitemapModelComponent, they
don't have a setup() method and no access to the objectModel and the
session.
 
I need to access to the session of the current request from the serializer.
 
Does anyone know how this can be performed?
 
--------
David
 

Mime
View raw message