Wolfgang--
One thing that can be risky here is when the classes in WSM's schemas JAR get out of sync with the XMLBean JAR itself.
In this case, WSM's schemas JAR in the tree needs to be re-generated in order to take a new XMLBean version. This might not be frequent, but because both Beehive and XMLBeans are under active development -- ie we're not using the fixed v1 of XMLBeans -- it seems like these should be generated from the XSD after doing a full Beehive (or WSM) clean.
One approach for doing this would be to build the XMLBean classes into a directory that is outside of the usual directory for the output of .class files from WSM. For example, something like this:
wsm/
build/
xsd-classes/ <= this contains the output of the XSD compile
classes/ <= this contains the output of a <javac> of WSMwhere xsd-classes/ is generated from the XSD compile and classes/ is generated from the WSM compile and references xsd-classes/ in its classpath. Then, these two classes directories can be put together in the same JAR. This way, it's possible to build all of the code from scratch but the XSD doesn't need to compile as long as the xsd-classes/ directory exists.
How about a compromise like that?
Eddie
[EMAIL PROTECTED] wrote:
Hi Michael,
It's possible if I make the ant task doing so but I now think only the generated jar file by XMLBeans should be in wsm since the xml schema won't be modified frequently. ( might be never )
If the jar, source files are generated everytime one builds, it can be annoying...
The generated jar file contains the xml schema so that if we want to modify the schema later, we can take it out from the jar and generate a new jar file using XMLBeans again. ( This process is not automatic though.)
Thanks in advance.
Wolfgang.
