You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dan Retzlaff (JIRA)" <ji...@apache.org> on 2012/07/25 01:23:33 UTC
[jira] [Updated] (CXF-4441) Enabling XJC DV plugin creates invalid
content
[ https://issues.apache.org/jira/browse/CXF-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Retzlaff updated CXF-4441:
------------------------------
Attachment: fix-dv-test.patch
fix-dv.patch
fail-dv-test.patch
The first patch demonstrates the problem.
The second two do not depend on the first. They patch the plugin and test respectively. (Sorry they're separate; my workspace doesn't lend itself to a single patch.)
> Enabling XJC DV plugin creates invalid content
> ----------------------------------------------
>
> Key: CXF-4441
> URL: https://issues.apache.org/jira/browse/CXF-4441
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.6.1
> Reporter: Dan Retzlaff
> Priority: Minor
> Attachments: fail-dv-test.patch, fix-dv-test.patch, fix-dv.patch
>
>
> CF-1206 introduces a behavior where complex types containing elements with default values get automatically instantiated in a parent. For example, given
> A(complex) contains B(complex) contains C(simple with default)
> A's constructor initializes "B b = new B()". This behavior goes beyond applying a default value; nothing in the schema says that A's "b" should be present by default.
> In our case, the presence of B has semantic value. What's more, B contains additional required fields, so this "default" invalidates the content model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira