[
https://issues.apache.org/jira/browse/COCOON3-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666921#action_12666921
]
Steven Dolg commented on COCOON3-14:
------------------------------------
> Is this event-based communication guaranteed at PipelineComponent level or
> it's left to implementation how to design it?
The supplied patch does not change how the components interact with each other.
The PipelineComponent interface remains unchanged.
> How it's possible that user is using a component and does not know what kind
> of input/output this component deals with?
This is always the case when the Pipeline is assembled at runtime from a
provided description, like the Sitemap.
While the PipelineAPI is intended do be used with direct calls from the user's
code, we should not forget that automatic pipeline construction using some kind
of description is still a valid use case and that basically no assumptions
about the actual components can be made in such a case (iow Generics are pretty
much worthless for that)
> Use generics for pipeline assembly
> ----------------------------------
>
> Key: COCOON3-14
> URL: https://issues.apache.org/jira/browse/COCOON3-14
> Project: Cocoon 3
> Issue Type: Improvement
> Components: cocoon-pipeline
> Reporter: Carsten Ziegeler
> Assignee: Cocoon Developers Team
> Attachments: generics.patch
>
>
> This is a simple patch to add generics to the pipeline interface and impl.
> With additionally introducing marker interfaces for the component types (SAX,
> Stax, dom)
> this would allow compile time checks if all components have the correct type
> when assembling the pipeline.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
