|
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----- Yes,
that's a solution, but it's a pity that serializers are 2nd
class citizens in Cocoon!. -------- David -----Mensaje original----- 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----- 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 |
- Custom serializers and session Carmona Perez, David
- RE: Custom serializers and session Jorg Heymans
- RE: Custom serializers and session Carmona Perez, David
- Jorg Heymans
