This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The <class> binding declaration enables you to customize the binding of a schema element to a Java content interface or a Java Element interface. <class> declarations can be used to customize:
* A name for a schema-derived Java interface
* An implementation class for a schema-derived Java content interface
The syntax for <class> customizations is:
* name is the name of the derived Java interface. It must be a legal Java interface name and must not contain a package prefix. The package prefix is inherited from the current value of package. * implClass is the name of the implementation class for className and must include the complete package name.
* The <javadoc> element specifies the Javadoc tool annotations for the schema-derived Java interface. The string entered here must use CDATA or < to escape embedded HTML tags.
So it does mention that given a xsd schema element, i can generate a Java interface for the element by using something like this:
However when i use the xjc command (and even the XJCTask Ant task), it generates POType as a "class" instead of an interface: