You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Helma van der Linden (JIRA)" <ji...@apache.org> on 2005/10/25 16:03:02 UTC
[jira] Reopened: (COCOON-845) [PATCH] New ReadDOMTransformer/WriteDOMTransformer available.
[ http://issues.apache.org/jira/browse/COCOON-845?page=all ]
Helma van der Linden reopened COCOON-845:
-----------------------------------------
reopened just to set the resolution to fixed
> [PATCH] New ReadDOMTransformer/WriteDOMTransformer available.
> -------------------------------------------------------------
>
> Key: COCOON-845
> URL: http://issues.apache.org/jira/browse/COCOON-845
> Project: Cocoon
> Type: Improvement
> Components: - Components: Sitemap
> Versions: 2.0.2
> Environment: Operating System: other
> Platform: Other
> Reporter: Andrzej Taramina
> Assignee: Cocoon Developers Team
> Priority: Minor
> Attachments: ReadDOMTransformer.java, WriteDOMTransformer.java
>
> The existing Read/WriteDOMSessionTransformer was limited to reading/writing to
> sessions only. I didn't really like this behaviour, since there are times you
> only want to store stuff for the duration of a request, and thus not have it get
> serialized to a persistent store (eg. by Tomcat) if you forget to invalidate the
> session or delete the DOM object (deletion currently being problematic
> with Cocoon).
> So I wrote new ReadDOMTransformer and WriteDOMTransformer classes that take an
> extra parameter specifying whether to read from/write to the session or the
> request instead. Default is to write to a session to stay more or less
> compatible with the older versions.
> Because WriteDOMTransformer parameters were made consistent with the
> ReadDOMTransformer, it's not a direct drop-in replacement for the older
> WriteDOMSessionTransformer (it now uses the "attribute-name" parameter instead
> of the prior "dom-name parameter" which was misnamed,
> IMNSHO).
> ....Andrzej
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira