cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Pieber (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON3-19) [PATCH] stax-sax converter
Date Wed, 04 Feb 2009 04:29:59 GMT

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

Andreas Pieber commented on COCOON3-19:
---------------------------------------

The stax-utils components directly taken from stax-utils are:

org.apache.cocoon.stax.converter.util.DummyLocator
org.apache.cocoon.stax.converter.util.ExtendedNamespaceContext
org.apache.cocoon.stax.converter.util.SimpleNamespaceContext
org.apache.cocoon.stax.converter.util.StaticNamespaceContext
org.apache.cocoon.stax.converter.util.XMLFilterImplEx

Components which are taken from the stax-utils project, but which were modified are:

org.apache.cocoon.stax.converter.util.StAXEventContentHandler
org.apache.cocoon.stax.converter.util.XMLEventToContentHandler

What do you mean with: "point me to the original license"? The original license from the source
code is exactly what you added again with the difference that all of them contain an id like:

$Id: ExtendedNamespaceContext.java,v 1.1 2004/07/05 23:10:46 cniles Exp $

and some of them does not have a sun-copyright header (Copyright (c) 2004, Sun Microsystems,
Inc.) but a copyright of the autor itself (Copyright (c) 2004, Christian Niles, unit12.net).
Should I change all licenses back to the original and provide a patch?

> [PATCH] stax-sax converter
> --------------------------
>
>                 Key: COCOON3-19
>                 URL: https://issues.apache.org/jira/browse/COCOON3-19
>             Project: Cocoon 3
>          Issue Type: Sub-task
>          Components: cocoon-stax
>            Reporter: Andreas Pieber
>            Assignee: Reinhard Poetz
>         Attachments: cocooon-stax-converter.patch
>
>
> 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 of COCOON3-18 since first the patch of COCOON3-18
have to be applied before this patch could be used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message