[
https://issues.apache.org/jira/browse/COCOON3-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645841#action_12645841
]
Simone Tripodi commented on COCOON3-10:
---------------------------------------
I agree with you, Steven!
Even if it's not necessary, it could be useful (and nice in therms of design)
separating the pure pipeline APIs from XML specific APIs, one scope could be
reusing the basic APIs to implement other different - and XML independent -
kinds of pipelines, like text processors, filters, and so on.
In that way, the pipeline package is a light and self-contained package,
without any dependency - at least the Logger, like now.
The XML module could be merged with the optional module, that contains XML only
related classes + dependencies.
> Packages could be re-organized
> ------------------------------
>
> Key: COCOON3-10
> URL: https://issues.apache.org/jira/browse/COCOON3-10
> Project: Cocoon 3
> Issue Type: Improvement
> Components: cocoon-pipeline
> Affects Versions: 3.0.0-alpha-2
> Reporter: Simone Tripodi
> Assignee: Cocoon Developers Team
> Priority: Trivial
> Fix For: 3.0.0-alpha-2
>
> Attachments: PackageOrganizing.patch
>
>
> According to older cocoon's taxonomy, packages - particularly the xml package
> - could be re-organized, discerning the roles of cocoon's components:
> - generators
> - serializers
> - transformer
> This is a nice way to maintain well-organized the code.
> What do you think about it?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
