You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be better to ask this on Stack Overflow, but I didn't see anything there or here.
I'm using the plugin to create Java Classes from a DTD. Everything is working. However, I have to conform to some "standards" that I can't seem to figure out how to do with the maven-jaxb2-plugin. I think it might be some change from JAXB 1 to 2 or something, but I can't figure out how to configure the plugin correctly to comply.
You should really better ask this on StackOverflow.
This is not directly related to the maven-jaxb2-plugin so I'll close the issue. Backwards incompatibility might have been introduced by the newer version of XJC which maven-jaxb2-plugin now uses.
But here are a few hints.
I haven't touched DTD in ages, but DTD compilaton also support bindings to some extent. Google "xml-java-binding-schema", you will find a bit of documentation.
Unfortunately, seems like generated choice properties cannot be customized this way:
It might be better to ask this on Stack Overflow, but I didn't see anything there or here.
I'm using the plugin to create Java Classes from a DTD. Everything is working. However, I have to conform to some "standards" that I can't seem to figure out how to do with the maven-jaxb2-plugin. I think it might be some change from JAXB 1 to 2 or something, but I can't figure out how to configure the plugin correctly to comply.
Given a DTD element like...
The previous code would generate a Java class with a generic
getContent
method.However, using version 0.14.0 of the maven-jaxb2-plugin generates the following...
How can I rename the generic choice method that's getting created?
The text was updated successfully, but these errors were encountered: