cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Relph (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CXF-2044) Aegis Custom Type Mapping
Date Fri, 20 Feb 2009 22:25:02 GMT

    [ https://issues.apache.org/jira/browse/CXF-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675487#action_12675487
] 

relphie edited comment on CXF-2044 at 2/20/09 2:24 PM:
-----------------------------------------------------------

I attached an expanded test case to reproduce null-pointer exception.

I think an auto-conversion jdom to xmlschema utility would probably be too much work.  Is
there a way to get these bug fixes without introducing this change?  Can 2.1.x branch continue
to use jdom?

Have you thought about moving all of the api to something even more generic, perhaps the org.w3c.dom
apis, so that there is no xml-schema library lock-in?

      was (Author: relphie):
    I attached an expanded test case to reproduce null-pointer exception.

I think an auto-conversion jdom to xmlschema utility would probably be too much work.  Is
there a way to get these bug fixes without introducing this change?  Can 2.1.x branch continue
to use jdom?
  
> 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.


Mime
View raw message