[ http://jira.magnolia.info/browse/MAGNOLIA-985?page=all ]
Oliver Lietz updated MAGNOLIA-985:
----------------------------------
Attachment: DataTransporter.diff
DataTransporter.java
Had the license issue in mind, but couldn't find anything on the website and
the wiki. Therefore I named the license explicitly.
Found a far smarter way of adding the XSL transformation feature with filter
chaining. There's no need for the CircularByteBuffer and Ostermiller's lib
anymore, the pom.diff can be dropped.
This is my first working version of the new XSL transformation feature.
> cleanup of import methods in DataTransporter (and depending classes) as
> preliminary work for new XSL transformation feature
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-985
> URL: http://jira.magnolia.info/browse/MAGNOLIA-985
> Project: magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0 RC3
> Reporter: Oliver Lietz
> Assigned To: Boris Kraft
> Priority: Minor
> Attachments: Bootstrapper.diff, DataTransporter.diff,
> DataTransporter.diff, DataTransporter.java, DataTransporter.java,
> ImportPage.diff, ModuleUtil.diff, pom.diff
>
>
> Renamed methods, made them more consistent and improved javadoc. This is
> preliminary work for a new XSL transformation feature. The methods for XSL
> transformation are also in "DataTransporter" namely "transformXmlStream" and
> "getXslStreamForXmlFile".
> The "importXmlStream" method (was "executeImport") is somewhat inconsistent
> and should be reviewed by the core developers. The two filters
> "ImportXmlRootFilter" and "MagnoliaV2Filter" for the XML stream are only
> applied when "keepVersionHistory" ist not true, otherwise the XML stream is
> completely unfilterred.
> The XSL transformation should happen after all filters are applied. This
> could be useful when bootstrapping and default values should be changed
> (passwords, subscribers, ...). It makes more sense to save a XSL file to
> version control, because it is easier to read and self-explanatory than an
> exported system view of the repository. Maybe a plugin mechanism for filters
> and transformations makes sense here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
