cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2044) Aegis Custom Type Mapping
Date Fri, 20 Feb 2009 21:49:02 GMT

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

Daniel Kulp commented on CXF-2044:
----------------------------------


Benson,  

Could a utility method be created to help out the migration?   Basically, something that would
create a dummy JDOM element that could be passed into their method and another utility to
take that JDOM element and fill in the XmlSchema stuff. 

If their methods are complex, migrating to XmlSchema could be a non-trivial.   Having something
to help out with it would be a good thing.   Not sure how hard that would be to write though.
 :-(

> 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.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