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] Commented: (CXF-2044) Aegis Custom Type Mapping
Date Mon, 23 Feb 2009 17:12:02 GMT

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

Brian Relph commented on CXF-2044:
----------------------------------

Thanks for you work, I do understand your motivations for switching to and only supporting
XmlSchema.

I agree, custom type mappings hopefully are not needed, unfortunately I am working with some
external classes that are not javabeans.

I am sure I can work through creating a new type mapper with xml schema.

Aside from that, do you have a set release schedule?  Or should I plan I building my own 2.1.5
for some time?

> 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
>             Fix For: 2.2, 2.1.5
>
>         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