|
Hi Stuart The problem is that (prior to checkin
220181) a TypeSystemHolder class was directly referenced in every generated class.
This TypeSystemHolder class is the link between the .class (generated Java
code) world and the .xsb (binary files equivalent to schema entries) world and it’s
generated in the _binary_
directory (i.e. the argument to the –d flag if you’re using scomp
or the classgendir arg to the xmlbean ant task). When it comes time to compile the generated
.java files this will only work if you include the classgendir in the
classpath. If you don’t specify the classgendir then a temp dir is
created and used for this purpose but unfortunately this is unlikely to be on
your classpath. After checkin 220181 we changed the direct
reference to be a reference by reflection to avoid this problem (and other
similar problems – see e.g. http://issues.apache.org/jira/browse/XMLBEANS-120). So choices are:
Cheers, From: Stuart Robertson
[mailto:[EMAIL PROTECTED] I am having the same problem as the user in thread http://www.mail-archive.com/[email protected]/msg07530.html |
- TypeSystemHolder does not exist errors Stuart Robertson
- RE: TypeSystemHolder does not exist errors Lawrence Jones
- Re: TypeSystemHolder does not exist errors Stuart Robertson
- Re: TypeSystemHolder does not exist errors Stuart Robertson
- RE: TypeSystemHolder does not exist errors Lawrence Jones

