DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23921>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23921 New ReadDOMTransformer/WriteDOMTransformer available. Summary: New ReadDOMTransformer/WriteDOMTransformer available. Product: Cocoon 2 Version: 2.0.2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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
