> Well, but have you tried using the <jaxb:property> to resolve the
> conflict as the tool suggests?
The tool's suggestions are not acceptable in my situation. I am creating an
automated tool that will use the schema to Java generation to create some
beans skeleton classes. I don't want too much user intervention, so I can't
change every schema that has an error and I am certainly not going to modify
the official W3C XHTML 1.0 schema to suit the XJC tool. I should not have
to. I was hoping there was a way around it that would not require user
intervention, but it seems there is not. As usual it looks like I'll be
rolling my own.
--
View this message in context: http://www.nabble.com/Error-parsing-xhtml1-strict.xsd-%22%22Lang%22-is-already-defined.%22-tp19004954p19017399.html
Sent from the java.net - jaxb users mailing list archive at Nabble.com.