Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :)
The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer.
I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :)
I created this issue as an subtask ofCOCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used.
The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer.
I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :)
I created this issue as an subtask of