[
https://issues.apache.org/jira/browse/CXF-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675433#action_12675433
]
Brian Relph commented on CXF-2044:
----------------------------------
Your fixes did indeed solve my test case. I was looking to create the patch,
but it is taking me some time to figure out the format of your existing test
cases.
However, after updating to 2.1.5-SNAPSHOT in my own code, I am now getting a
null-pointer exception during AegisDatabinding.initialize(Service s) -
apparently my BeanTypeInfo has a null info object. I guess neither
getTypeInfo() nor createTypeInfo() are called prior.
I was able to updated the test case to reproduce the issue. Basically, adding
a second service method that accepts the NoDefaultConstructorBean object
generates the null pointer. Would you like me to create a new issue for this,
or just upload the updated test case here? The same null-pointer exception
occurs with 2.2-SNAPSHOT.
> 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-0.1-SNAPSHOT-sources.jar,
> cxf-test-case-0.1-SNAPSHOT-test-sources.jar, 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.
