Not really an answer to your question, but unless you *really* need to use XMLBeans I would suggest that you use some other framework. I've used the xmlbeans-m-p in a project with some major pains.
The problem is that XMLBeans has no support of specifying the char encoding, but it simply uses the platform's default which leads to platform dependent builds and also don't play well with Maven. We managed to solve the encoding problem during compilation by having the xmlbeans-m-p handling both source generation AND compilation. But we ran into an encoding problem during relase when the javadoc jar was produced as the source encoding configured in Maven was different from the platform's default (which the source code generated by XMLBeans will use). It all lead to some very hacky solutions which will haunt us for the years to come. So, be warned! I suggest using JAXB instead. /Anders On Thu, Nov 24, 2011 at 22:51, Asmann, Roland <roland.asm...@adesso.at> wrote: > Hi all, > > I am checking out this plugin to generate classes from XSDs and I was > wondering whether I need to package all the extra stuff that is being > generated? > Besides the JAVA-files, I get several XSBs which are packaged into the > final WAR. Do I need those files? What are they actually for? > > Thanks. > > -- > Roland Asmann > Senior Software Engineer > > adesso Austria GmbH > Floridotower 26. Stock T +43 1 2198790-27 > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 > A-1210 Wien M +43 664 88657566 > E roland.asm...@adesso.at > W www.adesso.at > > ------------------------------------------------------------- > >>> business. people. technology. <<< > ------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
