Open mgrobarek opened 10 months ago
Thank you for reporting this issue. A new commit 5be585a includes your Limit example, in the unit test, and a modification to DefaultValuePlugin to handle anonymous types. It will be included in the next release (no ETA).
Hello,
I faced the same issue and default value is a key featurefor me. When is planned version 2.2.1 ?
Many thanks
I believe the current release period will be shorter than past periods. Note: I refrain from guessing ETAs.
The DefaultValuePlugin has been released to Maven Central.
Thanks for release,
Using Maven plugin "org.patrodyne.jvnet:hisrc-higherjaxb-maven-plugin:2.2.0" with this dependency (only this release available), I have this error
[ERROR] Failed to execute goal org.patrodyne.jvnet:hisrc-higherjaxb-maven-plugin:2.2.0:generate (default) on project plma-tools-commons: Execution default of goal org.patrodyne.jvnet:hisrc-higherjaxb-maven-plugin:2.2.0:generate failed: An API incompatibility was encountered while executing org.patrodyne.jvnet:hisrc-higherjaxb-maven-plugin:2.2.0:generate: java.lang.NoSuchMethodError: 'boolean org.jvnet.basicjaxb.util.FieldUtils.isConstantField(com.sun.tools.xjc.outline.FieldOutline)'
The hisrc-higherjaxb-maven-plugin v2.2.1 should be available to you.
I’m currently migrating to your default value xjc plugin when I encountered the following problem:
This happens for the following element definition:
The simpleType used for the Limit element has no name, hence the QName cannot be instantiated in DefaultValuePlugin.java:325. I can work around this issue by adding an explicit name for the inline type in my XSD, like this:
<xsd:simpleType name="LimitInt">
But in my case, the XSD comes from outside my project and I can’t change it on my own. Hence it would be nice to have the DefaultValuePlugin to ignore such empty names.
I’m using: