|
Hi Niklas The TypeSystemHolder class is a generated
class which is the “link” between the Java (.class) world and the
compiled schema (.xsb) world. It is output in the binary output directory (whatever
you specify with the –d flag to scomp) and is not output if you specify
-srconly. With SVN checkin #220181 XmlBeans was
updated so that the generated source no longer looks like the below but instead
uses an XmlBeans method to look up the TypeSystemHolder using the name of the
package, in your case “schemaorg_apache_xmlbeans.system.s356E206406D0E1BFD7A82E7E8EAC7C8F”, as a String. So you have a couple of choices: a) you can include the binary output directory in your classpath when
you compile – then the compilation will find the TypeSystemHolder class
and your compilation should proceed. b) you can update to a version of XmlBeans after #220181 – in which
case you should be able to compile just the generated source without the binary
dir – though you will of course need the binary output dir on the
classpath at runtime – otherwise the lookup by name will fail. Cheers, From: Niklas Modin Hi ! When using the xmlbean ant task, the generated source refers
to some strange package names, e.g : schemaorg_apache_xmlbeans.system.s356E206406D0E1BFD7A82E7E8EAC7C8F.TypeSystemHolder.typeSystem.resolveHandle("alerttype5256type"); When trying to compile the generated code this fails with
package do not exists error as expected. Am I missing something here ? It generates the .jar files ok
so should I just make sure the generated code BR Niklas |
- Generated code question Niklas Modin
- RE: Generated code question Lawrence Jones
- RE: Generated code question Niklas Modin
- RE: Generated code question Wing Yew Poon
- RE: Generated code question Niklas Modin

