Re: problem concerning version number in targetNamespace

Thanks for the information. Now I see that there are good reasons for using such a namespace. Sorry for saying that this could be a mistake. I just have not seen a namespace like that before and did not know what benefit it could have. Johannes Radu Preotiuc-Pietro wrote: People do have

NPE running scomp

Hi, ANyone got any ideas what is causing this NPE. I am using 2.1.0 Exception in thread "main" java.lang.NullPointerException at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.getIndexForLocalAttribute(SchemaTypeImpl.java:690) at

RE: NPE running scomp

BTW the schema validates OK with XMLSPY and SQC From: Mike Skells [mailto:[EMAIL PROTECTED] Sent: 09 December 2005 10:30To: user@xmlbeans.apache.orgSubject: NPE running scomp Hi, ANyone got any ideas what is causing this NPE. I am using 2.1.0 Exception in

Good Reference Sites

Can someone please direct to good examples of how to use XML Beans? I downloaded all the samples from the XML Beans website. Richard Butterwood| Senior Analyst/Programmer | Infor | office:770-418-2000 X 1167| cell:678-492-3080 | fax:770-418-2022 | [EMAIL PROTECTED] SAVE THE DATE:

RE: problem concerning version number in targetNamespace

It may be worth mentioning that you can use xsdconfig files to override the default mapping from a given namespace to a package name and pick anything you want. (Although the package name you pick obviously has to be a valid Java package name - so you can't have just numbers). You will then have

RE: NPE running scomp

Hi Mike Could you post the schema and the exact command line youre invoking when you see this? I think that would allow easier investigation. Cheers, Lawrence From: Mike Skells [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 8:42 AM To:

Re: Schema compilation to some specific package

Hi Radu, I think you didnot get my problem at all. Let me precise it. I already have a .xsdconfig that is generating all the beans to my custom package. The problem is that schema compiled classes such as the TypeSystemHolder are not generated to this package but by default to schema.system.

RE: Attributes and NameSpaces

Hi Richard I think youre running into the infamous elementFormDefault=qualified | unqualified issue. If you dont put an elementFormDefault attribute in the schema element of your schema the default is elementFormDefault=unqualified. This means that when you refer to non-global

Re: Attributes and NameSpaces

Lawrence, I ran into this exactproblem when I startedusing xmlBeans and it was baffling and cost me hours of time before you sent a similiar explanation. Isn't there some kind of creative check that xmlBeans could run to detect the possible existence of this problem and alert the user?

RE: Attributes and NameSpaces

Hi Lawrence, Thank you for the reply. Option 1 did not seem to work. Option 2 worked great! Richard Butterwood| Senior Analyst/Programmer | Infor | office:770-418-2000 X 1167| cell:678-492-3080 | fax:770-418-2022 | [EMAIL PROTECTED] From: Lawrence Jones [mailto:[EMAIL

RE: NPE running scomp

Hi Mike I can repro your problem and I think its a bug so Ive raised a JIRA - http://issues.apache.org/jira/browse/XMLBEANS-236. Its something to do with the attribute called scope at line 175. I changed use=prohibited to use=required at line 175 and it compiled fine. Im also

RE: Attributes and NameSpaces

Title: Message Well, XmlBeans doesn't really know when you meant to call something else and when you actually need are able to handle null (plus, adding any such code on the critical path for a 'get' would slow things down noticeably). But, what one can do when in doubt is call .validate()

RE: NPE running scomp

Hi Laurance, the lack of a target namespace was an error in the schema I changed it but the bug still persists I had a look at the scope attribute, unusually for a prohibited attribute it has an enumeration or values. I removed this and the compilation works OK Maybe it is to do with