Steven Dolg wrote
> Just realized there is no SAXConsumer any more.
> So how does the linking between SAX components work?
> AbstractSAXProducer will accept an AbstractSAXTransformer or
> AbstractSAXSerializer? Or operate directly against ContentHandler (which
> would explain the SAXPipe thingy)?
Y
[
https://issues.apache.org/jira/browse/COCOON3-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated COCOON3-22:
Attachment: cocoon-3.patch
Proposed patch
> Remove XMLConsumer interface
> ---
Steven Dolg wrote:
> Just random thoughts (and I must admit I haven't thought about the
> changes in detail):
>
> * Extending some abstract classes is all that was necessary all the
> time.
Yepp.
> Getting rid of some of the interfaces implemented by those
> abstract classes actually changes not
Steven Dolg schrieb:
Carsten Ziegeler schrieb:
Hi,
as part of COCOON3-22 I've refactored the whole SAX module and removed a
lot of classes :)
Before committing these changes I would like to discuss them (I can
provided a patch but not sure if this works).
Ok, the aim is to reduce the number o
Carsten Ziegeler schrieb:
Hi,
as part of COCOON3-22 I've refactored the whole SAX module and removed a
lot of classes :)
Before committing these changes I would like to discuss them (I can
provided a patch but not sure if this works).
Ok, the aim is to reduce the number of interfaces and abstr
Hi,
as part of COCOON3-22 I've refactored the whole SAX module and removed a
lot of classes :)
Before committing these changes I would like to discuss them (I can
provided a patch but not sure if this works).
Ok, the aim is to reduce the number of interfaces and abstract classes
as much as possi
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=144269&projectId=51
Build statistics:
State: Ok
Previous State: Error
Started at: Tue 17 Feb 2009 08:18:03 -0800
Finished at: Tue 17 Feb 2009 08:32:22 -0800
Total time: 14m 19s
Build Trigger: Schedule
Build Num
