SchemaTypeLoaderException and index.xsd

Hello, I don't understand my issue. java.lang.ExceptionInInitializerError at com.mycompany.myproj.adminwizard.SelectionDocument.clinit(SelectionDocument.java:19) at com.mycompany.myproj.adminwizard.SelectionDocument$Factory.newInstance(SelectionDocument.java:240) at

Namespace problem reading xml

Hi I need to read an xml file. The namespace on the schema is noNamespace, and generated classes are on package noNamespace. But my project environment is a little bit special because I could not use my generated jar and I need to upload generated source code to a package name that will be

Re: scomp fails trying javac

As you can see from the example, adding the -compiler parameter caused scomp to find javac. C:\xmlbeans-2.4.0scomp -compiler c:\Progra~1\Java\jdk1.6.0_05\bin\javac

Re: Namespace problem reading xml

Have you looked into using an xmlconfig file to generate the classes into the packages you want. Take a peek on the xmlbeans wiki for more information on what to do. HTH, -jacobd On Fri, Sep 18, 2009 at 5:07 AM, JavierL xle...@gmail.com wrote: Hi I need to read an xml file. The namespace on

implementing a custom interface

I have three types in my XSD: Savings, Checking, Certificate. Is it possible to add something (to the .xsdconfig?) that makes all three types implement an interface I created? I want my beans to be like this: Product getStaringBal() getEndingBal() Savings implements Product

RE: implementing a custom interface

If I understand you correctly, in your XSD create a base type with the common attributes. Create types for each of your 3 derived from the base type. In your code you can refer to each as basetype and for specifics test with instanceof. Paul Gillen -Original Message- From: Jason

RE: implementing a custom interface

Paul, Thanks for the reply... I'm not very handy with XML (which is why I'm trying to use xbeans :-)) so I'm not exactly sure if I can do what you are recommending given my system constraints. We have product that we can't really modify that produces XML. I want to bind to that xml with xbeans.

RE: implementing a custom interface

My colleagues say this wasn't clear. The base type defined in the XSD in effect becomes the interface to the implementing types. This approach keeps you painting between the lines in the XSD world rather than drifting off the beam customizing XMLBeans. The example below implements a