[ https://issues.apache.org/jira/browse/COCOON3-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645830#action_12645830 ] 

Steven Dolg commented on COCOON3-10:
------------------------------------

That is something we should do - rater sooner than later.
Distinguishing between the roles components can have seems to be a good idea.

What I thought about was moving all XML components from the pipeline into their own module.
Actually that's an idea someone else (I believe it was Carsten) had quite some time ago - I just didn't thought it was necessary.
However the pipeline module has grown quite large since that.

On top of that a package reorganisation as proposed here should be done.

> 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.