[
https://issues.apache.org/jira/browse/CXF-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675507#action_12675507
]
Benson Margulies commented on CXF-2044:
---------------------------------------
Brian,
CXF, broadly, has always had an XML Schema dependency. It's not going away. In
fact, in general, we're doing just the opposite. Dan and I got ourselves voted
in as Xml Schema committers just so that we could more confidently depend on
it. Using a DOM API for all the schema things CXF has to do would be really
nasty from a performance and maintenance standpoint.
The change to Aegis to have the Type system work directly with Xml Schema is
consistent with the rest of the system -- if perhaps not very polite on the
2.1.x branch.
I think you might be one of about 3 people who ever bothered to invest in
custom type objects. Or, at least, who have turned up in the CXF community. CXF
2.0.x left a number of Aegis features broken from the original port. I changed
all sorts of things in 2.1.
Porting this code back to 2.1 has the potential to annoy anyone, like you, who
adapted custom type code to the 2.1 changes.
Your welcome to move this thread to the dev list. I suspect that the net-net
will be this; there's no one in the community with the time and inclination to
fix your original problem inside the 2.1 JDOM paradigm.
If you and others really would rather have JDOM and bugs than Xml Schema and
less bugs in the 2.1.x branch, then we'd have to consider unwinding my (really
laborious) backport.
--benson
> Aegis Custom Type Mapping
> -------------------------
>
> Key: CXF-2044
> URL: https://issues.apache.org/jira/browse/CXF-2044
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.1.3, 2.1.4
> Reporter: Brian Relph
> Assignee: Benson Margulies
> Attachments: cxf-test-case-updated.zip, cxf-test-case.zip
>
>
> Attempting to specify a custom type mapping to the aegis context results in a
> schema name conflict exception.
> The exception does not occur in 2.2-SNAPSHOT.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
