Error in parsing xsd schema using jaxb !!

I want to parse an xsd which contains links to other schema (.xsd) files. in the following format along with other things :
<xsd:include schemaLocation="fgdc-std-001-1998-sect01.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect02.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect03.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect04.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect05.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect06.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect07.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect08.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect09.xsd" />
<xsd:include schemaLocation="fgdc-std-001-1998-sect10.xsd" />
But when i issue the xjc command, an error occours saying
[ERROR] In "strict" mode, the following schema feature is not allowed (See App E
.2).Use the "-extension" switch:
<key>
line 127 of fgdc-std-001-1998-sect02.xsd
I don't understand what the error means.................................Any help in this regard shall be sincerely appreciated.
Thanks in Advance,
Bibhusan

ERROR] In "strict" mode, the following schema feature is not allowed (See App E
.2).Use the "-extension" switch:
<key>
line 127 of fgdc-std-001-1998-sect02.xsd
Some of the schema constructs xs:any, xs:anyAttribute, xs:key, xs:keyref, xs:unique are not supported
by Jaxb.

Similar Messages

Error while compiling schema using JAXB 1.0.2 to

Hi ,
Please help ! i am trying to compile my schema using JAXB1.0.2 (bundled with Java Web Services Developer Pack 1.3 ) .I am getting a java.util.MissingResourceException . Can anyone help as to which portion of the schema i should look at.Here are the error details.
thanks
Rahul
parsing a schema...
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.util.MissingResourceException: Can't find resource for bundle ja
va.util.PropertyResourceBundle, key parser.cc.8
at java.util.ResourceBundle.getObject(ResourceBundle.java:314)
at java.util.ResourceBundle.getString(ResourceBundle.java:274)
at com.sun.msv.datatype.xsd.regex.RegexParser.ex(RegexParser.java:138)
at com.sun.msv.datatype.xsd.regex.ParserForXMLSchema.parseCharacterClass
(ParserForXMLSchema.java:291)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseAtom(RegexParser.java
:736)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseFactor(RegexParser.ja
va:638)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseTerm(RegexParser.java
:342)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseRegex(RegexParser.jav
a:320)
at com.sun.msv.datatype.xsd.regex.RegexParser.parse(RegexParser.java:158
at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
pression.java:3040)
at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
pression.java:3051)
at com.sun.msv.datatype.xsd.regex.RegularExpression.<init>(RegularExpres
sion.java:3017)
at com.sun.msv.datatype.xsd.PatternFacet.compileRegExps(PatternFacet.jav
a:79)
at com.sun.msv.datatype.xsd.PatternFacet.<init>(PatternFacet.java:67)
at com.sun.msv.datatype.xsd.TypeIncubator.derive(TypeIncubator.java:261)
at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.restrictionSimpleT
ype(DatatypeBuilder.java:82)
at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
leTypeImpl.java:66)
at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.build(DatatypeBuil
der.java:65)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.buildPrimitiveTy
pe(SimpleTypeBuilder.java:161)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.access$100(Simpl
eTypeBuilder.java:50)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.checkCon
version(SimpleTypeBuilder.java:201)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.restrict
ionSimpleType(SimpleTypeBuilder.java:276)
at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
leTypeImpl.java:66)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.build(SimpleType
Builder.java:93)
at com.sun.tools.xjc.reader.xmlschema.cs.DefaultClassBinder.simpleType(D
efaultClassBinder.java:130)
at com.sun.xml.xsom.impl.SimpleTypeImpl.apply(SimpleTypeImpl.java:89)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector._bindToClass(Clas
sSelector.java:212)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.bindToType(ClassS
elector.java:177)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.populate(BGMBuilder.jav
a:254)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.buildContents(BGMBuilde
r.java:223)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build(BGMBuilder.java:
116)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build(BGMBuilder.java:8
0)
at com.sun.tools.xjc.GrammarLoader.annotateXMLSchema(GrammarLoader.java:
424)
at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:130)
at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:79)
at com.sun.tools.xjc.Driver.run(Driver.java:177)
at com.sun.tools.xjc.Driver._main(Driver.java:80)
at com.sun.tools.xjc.Driver.access$000(Driver.java:46)
at com.sun.tools.xjc.Driver$1.run(Driver.java:60)

Hi,
A similar problem occur to me once.
In that case it was that I copied the files from:
JWSDP_HOME\jaxb\lib
to
JAVA_HOME\jre\lib\endorsed
when I shouldn�t.
I should take the files only from JWSDP_HOME\jwsdp-sahred\lib\endorsed
So try taking the files:
jaxb-api.jar
jaxb-impl.jar
jaxb-xjc.jar
jaxb-libs.jar
out of the JAVA_HOME\jre\lib\endorsed directory living them only in jaxb\lib where they should be.
Try that, and let�s see if the compilation improves.

How to Map XML data with XSD Schema in JAXB

Hello,
I am very much new to JAXB.
I am in need of someone help to go further in my dev.
I am having an XSD and i could able to do marshall and unmarshall using JAXB.
My problem is...
Consider followings are my Schema...
- <person id="general" help="USER.DOM.HELP.GENERAL" label="USER.DOM.LABEL.GENERAL" access="READWRITE">
<attribute id="Name" mandatory="true" type="STRING" access="READONLY" widget="NONE" />
<attribute id="login" label="USER.LABEL.LOGIN" help="USER.HELP.LOGIN" regexp="[A-a]" type="STRING" summary="true" access="WCREATE_RUPDATE" widget="TEXTFIELD" />
<attribute id="firstname" summary="true" label="USER.LABEL.FIRSTNAME" help="USER.HELP.FIRSTNAME" type="STRING" regexp="[A-a]" access="READWRITE" widget="TEXTFIELD" />
In this example a person contains set of attributes... some are mandatory(Name)...
In my application i will unmarshall the the schema file and show in GUI as a set of attributes when the operator want to create a person. And its very well working.
Now say for example, i am requesting my server to show all the created persons and its showing. when i click on the particular person the GUI will place the request to the server to get the corresponding date for the selected person.
But the response contains only the mandatory attribute.. i mean Name.... this may be because of the way my server working. So now i want to show the operator all the set of attributes for that person with the Name.
I mean i need to merge the schema with me resultant data and show it in the GUI.
My result is in the form of xml stream. And i will convert my schema also in the form of XML...
Now i need to merge both of this XMl and need to present in the GUI...
Any help please...
Thank You!!!

Still i am not getting any reply :(

Object reference not set to an instance of an object error when generating a schema using flat file schema wizard.

I have a csv file that I need to generate a schema for. I am trying to generate a schema using flat file schema wizard but I keep getting "Object reference not set to an instance of an object." error when I am clicking on the Next button after
specifying properties of the child elements on the wizard. At the end I get schema file generated but it contains an empty root record with no child elements.
I thought may be this is because I didn't have my project checked out from the Visual SourceSafe db first but I tried again with the project checked out and got the same error.
I also tried creating a brand new project and generating a schema for it but got the same error.
I am not sure what is causing Null Reference exception to be thrown and there is nothing in the Windows event log that would tell me more about the problem.
I am using Visual Studio 2008 for my BizTalk development.
I would appreciate if some has any insides on this issue.

Hi,
To test your environment, create a new BizTalk project outside of source control.
Create a simple csv file on the file system.
Name,City,State
Bob,New York,NY
Use the Flat file schema Wizard to create the flat file schema from your simple csv instance.
Validate the schema.
Test the schema using your csv instance.
This will help you determine if everything is ok with you environment.
Thanks,
William

Error with creating star schema using HsvStarSchemaACM

Hi,
I am trying to create a star schema using the API HsvStarSchemaACM. But when calling the create function of API, i get the below exception. Exception from HRESULT: 0x80040251 (A general error occurred while trying to obtain a database Reader/Writer lock). Is this something to do with the parameters passed and its connections(connection works fine and createstarschema is running thru workspace).
Any solutions to this is more welcome.
Thanks,
Logu

Can you provide details on HsvStarSchemaACM API? How is it related to ODI?

Parsing .xsd files using DOM

Hi,
I am trying to parse a xsd file using DOM. The xsd has several nodes like
<xsd:complexType name="AccountLocate">
I want to extract the strings AccountLocate and AccountCategory and use them for further processing.
The hierarchy of the nodes is created without issues, but when I try to view the name and value of each node using getNodeName() and getNodeValue() method the node name I get and node value is as follows:
NODE-NAME NODE-VALUE NODE-TYPE
xsd:complexType null 1 //corresponds to the xsd:complexType node
#text 3 //corresponds to the AccountLocate node
Is there anyway (any DOM method for example) by which I can isolate the name AccountLocate?
Thanks and regards,
Prabal

Which parser is used for parsig?
With the DocumentBuilder parser set:
DocumentBuilderFactory factory
= DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);For parsing with the javax.xml.xpath.XPath class set the NamespaceContext on the XPath object.

How to generate .xsd file using jaxb generated java files

Hi,
We need to upgrade our applicatio to jdk1.6 which has jaxb2.0 class files in it. Our application has java files generated from .xsd using jaxb1.0.2 version. At present we dont have .xsd or .xml file with us.
We decide to generate .xsd file by using jaxb1.0.2 generated java files. I tried using schemagen.exe given by jdk1.6 to generate .xsd file. It error out. Is there any other way to generate .xsd file ?
pls let me know.
thanks,
Thiru

Object-XML mapping is a new feature in JAXB 2.0. Classes generated with JAXB 1.0 won't generate a schema.
Generate Java classes with JAXB 2.0 xjc.
http://www.theregister.co.uk/2006/09/22/jaxb2_guide/

Error while exporting a schema using data pump

Hi all,
I have 11.1.0.7 database and am using expdp to export a schema. The schema is quite huge and has roughly about 4 GB of data. When i export using the following command,
expdp owb_exp_v1/welcome directory=dmpdir dumpfile=owb_exp_v1.dmp
i get the following error after running for around 1 hour.
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [TABLESPACE_QUOTA:"OWB_EXP_V1"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7839
----- PL/SQL Call Stack -----
object line object
handle number name
4A974B9C 18237 package body SYS.KUPW$WORKER
4A974B9C 7866 package body SYS.KUPW$WORKER
4A974B9C 2744 package body SYS.KUPW$WORKER
4A974B9C 8504 package body SYS.KUPW$WORKER
4A961BF0 1 anonymous block
4A9DAA4C 1575 package body SYS.DBMS_SQL
4A974B9C 8342 package body SYS.KUPW$WORKER
4A974B9C 1545 package body SYS.KUPW$WORKER
4A8CD200 2 anonymous block
Job "SYS"."SYS_EXPORT_SCHEMA_01" stopped due to fatal error at 14:01:23
This owb_exp_v1 user has dba privileges. I am not sure what is causing this error. I have tried running it almost thrice but in vain. I also tried increasing the sort_area_size parameter. Even then, i get this error.
Kindly help.
Thanks,
Vidhya

Hi,
Can you let us know what the last object type it was working on? It would be the line in the log file that looks like:
Processing object type SCHEMA_EXPORT/...
Thanks
Dean

Problem in parsing XML Schema

I am trying to parse XML Schema using XSOM. The Schema has <xs:include>s
e.g. I have first.xsd which includes second.xsd and second.xsd again includes third.xsd.
First.xsd
<xs:include schemaLocation="../Second.xsd">....
Second.xsd
<xs:include schemaLocation="Third.xsd">....
When I parse "First.xsd" parser passes the correct path "C:/XSDSchema/Second.xsd"(First.xsd resides in "C:/XSDSchema/Schema/") to the EntityResolver's resolveEntity method. But for Second.xsd it passes "Third.xsd" only (Third.xsd resides in "C:/XSDSchema/" ) .
Any Idea ?????

Here is a screenshort of the part of my workflow:
In the mappings of the "Set Value" activity, I have one line with those properties:
Location: /process_data/bonusValidationForm/object/data/xdp/datasets/data/BonusValidationForm/buMan agerID
Expression: /process_data/currentUser/object/@userId
Where:
bonusValidationForm is a process variable of my workflow that point my xdp form
buManagerID is the textfield I want to set
currentUser is a process variable (type User) that was well setted by the task Find BU Manager

Validating XML against an XML Schema using PL/SQL

Hello everyone,
I've a strange problem.
I'm trying to validate an XMLTYPE variable against an XSD schema using the XMLisValid function.
The XML I was trying to validate was returning false (0) when using this method.
However, when I register the XSD against a column in a table and then insert this XMLTYPE into that column, I do not get any errors. If I change the XSD to ensure failure when using this method, I do get an error, so it is registered and working.
I have then created a very basic XSD and both methods work when validating the XML against this. So obviously the more complicated XSD I want to validate against is making a difference, but I would expect them to either both fail or both pass, not one fail and one pass.
Does anyone know why they'd be returning different results?
Thanks in advance for your help.
Robin
examples of what I'm using:
XML to validate:
<centres>
<add>
<centre>
<centreName>Name 1</centreName>
<centreRef>45678</centreRef>
</centre>
</add>
</centres>
Simple XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="centres" type="centresType"/>
<xs:complexType name="addType">
<xs:sequence>
<xs:element type="xs:string" name="centreName"/>
<xs:element type="xs:short" name="centreRef"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="centresType">
<xs:sequence>
<xs:element type="addType" name="add" maxOccurs="3" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Complicated XSD:
<?xml version="1.0" encoding="utf-8" ?>

<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="centres">
<xs:complexType>
<xs:sequence>
<xs:element name="remove">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="centreRef">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="add">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="centre">
<xs:complexType>
<xs:sequence>
<xs:element name="centreName">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="centreRef">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element minOccurs="0" maxOccurs="1" name="qualifications">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="qualRef">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="modifyQualAssociations">
<xs:complexType>
<xs:sequence>
<xs:element name="remove">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="r">
<xs:complexType>
<xs:attribute name="centreRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="qualRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="add">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="a">
<xs:complexType>
<xs:attribute name="centreRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="qualRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

Steps to validate XML data against a schema in Oracle:
1. Register your XSD in the database.
begin
dbms_xmlschema.registerschema(
SchemaUrl,
SchemaDoc,
local => TRUE/FALSE);
end;
2. For validating your XML document against your registered schema, here is a sample pl/sql block.
declare
v_xml xmltype;
begin
v_xml := your_xml_document;
v_xml.schemaValidate();
end;
Hope this helps :)

How to validate an XML file with XSD Schema on JDK 1.4

Hi
I'm looking for samples how to validate xml files with xsd schema using jsdk 1.4
Thank you.

This is how.
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.dom.DOMResult;
import javax.xml.transform.dom.DOMSource;
import javax.xml.validation.Schema;
import javax.xml.validation.SchemaFactory;
import javax.xml.validation.Validator;
DocumentBuilderFactory dbfac = DocumentBuilderFactory.newInstance();
dbfac.setNamespaceAware(true);
SchemaFactory factory1 = SchemaFactory
.newInstance("http://www.w3.org/2001/XMLSchema");
Schema schema = factory1.newSchema(new File("person.xsd"));
dbfac.setSchema(schema);
DocumentBuilder dbparser1 = dbfac.newDocumentBuilder();
Document doc1 = dbparser1.parse(new File("person.xml"));
Validator validator1 = schema.newValidator();
DOMSource dm1 = new DOMSource(doc1);
DOMResult domresult1 = new DOMResult();
validator1.validate(dm1, domresult1);

Getting the following error while parsing the values usng xml parser

Hi
I am getting the following error while parsing the values using the code in r12 instance on linux
declare
XML_PARSER XMLPARSER.PARSER;
DOC XMLDOM.DOMDOCUMENT;
DOCELEMENT DBMS_XMLDOM.DOMELEMENT;
BEGIN
-- NEW PARSER
XML_PARSER := XMLPARSER.NEWPARSER;
-- SET SOME CHARACTERISTICS
XMLPARSER.SETVALIDATIONMODE(XML_PARSER, FALSE);
     IF P_DIR IS NOT NULL AND P_FILENAME IS NOT NULL
     THEN
     FND_FILE.PUT_LINE(FND_FILE.LOG,'DIRECTORY FOUND'||'-'||P_DIR);
     XMLPARSER.SETBASEDIR(XML_PARSER, P_DIR);
     -- PARSE INPUT FILE
     FND_FILE.PUT_LINE(FND_FILE.LOG,'FILE FOUND'||'-'||P_FILENAME);
     XMLPARSER.PARSE(XML_PARSER, P_DIR || '/' || P_FILENAME);
     -- GET DOCUMENT
     DOC := XMLPARSER.GETDOCUMENT(XML_PARSER);
     LOAD_SUPP(doc);
     ELSE
     DBMS_OUTPUT.PUT_LINE('DIRACTORY/FILENAME CANNOT BE NULL');
     END IF;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('DATA NOTINSERTED'||sqlerrm);
     ROLLBACK;
END
I am getting the following error
DIRACTORYL-/home/appldevORA-0000: normal, successful completion
FILE NAME-suppliersample_data.xmlORA-0000: normal, successful completion
DATA NOTINSERTEDORA-31001: Invalid resource handle or path name "/home/appldev/suppliersample_data.xml"
ORA-06512: at "SYS.XDBURITYPE", line 11
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 142
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-29280: invalid directory path
It could be great if some one could give a suggestion/solution.
Thanks
Ajesh

Besides this is not the correct forum try to google the error message first before posting:
http://ora-29280.ora-code.com/
cheers

Error while parsing OTA standard XSD

Hi,
I am trying to create java objects using Toplink Workbench for an XSD which corresponds to OTA 2006B standard.
When I try to create a new JAXB project, pointing to the target XSD for which java objects have to be generated, I get the following error message -
'Error importing schema During JAXB Project Generation, The following error was encountered while loading the schema: invalid derivation from base type "extension".'
I am actually able to generate java code for the same xsd using JAXB from command line without problems, but i need a JDK1.4 compliant src, unlike JAXB-generated src which uses Annotations.
Any suggestions on this please?
Just an interesting thing - I am able to generate java objects for OTA 2005B standard XSD, but have problems compiling the generated src.
best regards
murali

Maybe "extraneous" is an incorrect term. Apparantly, based upon the writeup within Wiki, the parser I am using does not interpret the """? How do I find which parser is being utilized and how to control it?
<<<
If the document is read by an XML parser that does not or cannot read external entities, then only the five built-in XML character entities (see above) can safely be used, although other entities may be used if they are declared in the internal DTD subset.
If the document is read by an XML parser that does read external entities, then the five built-in XML character entities can safely be used. The other 248 HTML character entities can be used as long as the XHTML DTD is accessible to the parser at the time the document is read. Other entities may also be used if they are declared in the internal DTD subset.
>>>

Getting error while using jaxb/xjc

hello every one,
i have a xsd and i want automated classes from it for which i am using jaxb and xjc compiler but when i am running it then i am getting error
parsing a schema...
compiling a schema...
Exception in thread "main" java.lang.IllegalArgumentException: Expected
class ja
vax.xml.bind.annotation.XmlAccessType but found class
javax.xml.bind.annotation.
my xsd is
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="clients"
type="ClientsDef"/>
<xs:complexType name=" ClientsDef ">
<xs:sequence>
<xs:element name="pers" type="Person"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="Person">
<xs:sequence>
<xs:element name="name"
type="xs:string"/>
<xs:element name="date_of_birth"
type="xs:date"/>
<xs:element name="cnp"
type="xs:string"/>
<xs:element name="adress"
type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
any one please help me out...

Hi,
XSD is well formed but for JAXB, it needs to have the complexType declaration inner the root element:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="clients">
    <xs:complexType>
        <xs:sequence>
            <xs:element name="pers" type="Person" maxOccurs="unbounded"/>
        </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:complexType name="Person">
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element name="date_of_birth" type="xs:date"/>
<xs:element name="cnp" type="xs:string"/>
<xs:element name="adress" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>Tested this works with this Main using jaxb-bindings in Netbeans (defining XSD compilation under clients package, Main in default package):
import clients.Clients;
import clients.ObjectFactory;
import clients.Person;
import java.io.ByteArrayOutputStream;
import javax.xml.bind.JAXBContext;
import javax.xml.bind.Marshaller;
public class Main
    public static void main(String args[]) throws Exception
        ObjectFactory of = new ObjectFactory();
        Clients cd = of.createClients();
        Person p = of.createPerson();
        p.setAdress("address");
        p.setCnp("cnp");
        p.setName("name");
        cd.getPers().add(p);
        ByteArrayOutputStream bos = new ByteArrayOutputStream();
        try
            JAXBContext ctx;
            ctx = JAXBContext.newInstance(Clients.class);
            Marshaller marshaller = ctx.createMarshaller();
            marshaller.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT, new Boolean(true));
            marshaller.marshal(cd, bos);
            System.out.println(bos.toString());
        finally
            bos.close();
}Generates:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<clients>
<pers>
<name>name</name>
<cnp>cnp</cnp>
<adress>address</adress>
</pers>
</clients>

Catch all error information while validating xml content with xsd schema

Hi experts,
I created a java mapping to validating the input xml content with xsd schema (schema validation). What I want is to catch all error message to the xml not just the first error. I used SAXParser in sapxmltoolkit.jar to do the schema validation. The below is a part of my java mapping.
XMLReader parser = XMLReaderFactory.createXMLReader("com.sap.engine.lib.xml.parser.SAXParser");
parser.setFeature( "http://xml.org/sax/features/validation" , true);
parser.setFeature( "http://apache.org/xml/features/validation/schema" , true);
parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");          parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource",this.getClass().getClassLoader().getResourceAsStream(schema)); // schema is my schema name
parser.setErrorHandler(new ParseErrorHandler()); // ParseErrorHandler is my own ErrorHandler which extends DefaultHandler
parser.parse(new InputSource(new ByteArrayInputStream(sinput.getBytes())));
// In error handler, I comment all code so as not to throw any exception
public class ParseErrorHandler extends DefaultHandler
     public void error(SAXParseException e) throws SAXException
          // sSystem.out.println("Error" + e.getMessage());
          // throw e;
     public void fatalError(SAXParseException e)
          // throw e;
          // System.out.println("SAP Fatal Error" + e.getMessage());
Unfortunately the program always stopped while catching the first error. Check the below log.
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
ERRORS :
cvc-simple-type : information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is not valid, because it's value does not satisfy the constraints of facet 'minLength' with value '1'.
cvc-data : information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is is not valid with respoct to the corresponding simple type definition.
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is associated with invalid data.
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]' is not valid with respect to it's complex type definition..
-> com.sap.engine.lib.xml.parser.ParserException:
I tried using Xerces and JAXP to do validation, the same error happened. I have no idea on this. Does xi has its own error handler logic? Is there any body can make me get out of this?
Thanks.

<h6>Hi experts,
<h6>
<h6>I created a java mapping to validating the input xml content with xsd schema (schema validation). What I want is to catch all <h6>error message to the xml not just the first error. I used SAXParser in sapxmltoolkit.jar to do the schema validation. The below <h6>is a part of my java mapping.
<h6>XMLReader parser = XMLReaderFactory.createXMLReader("com.sap.engine.lib.xml.parser.SAXParser");
<h6>parser.setFeature( "http://xml.org/sax/features/validation" , true);
<h6>parser.setFeature( "http://apache.org/xml/features/validation/schema" , true);
<h6>parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");          <h6>parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource",this.getClass().getClassLoader().getResourceAsStream(schema)); <h6>// schema is my schema name
<h6>parser.setErrorHandler(new ParseErrorHandler()); // ParseErrorHandler is my own ErrorHandler which extends Default Handler
<h6>parser.parse(new InputSource(new ByteArrayInputStream(sinput.getBytes())));
<h6>
<h6>// In error handler, I comment all code so as not to throw any exception
<h6>public class ParseErrorHandler extends DefaultHandler
<h6>{
<h6>     public void error(SAXParseException e) throws SAXException
<h6>     {
<h6>          // sSystem.out.println("Error" + e.getMessage());
<h6>          // throw e;
<h6>     }
<h6>
<h6>     public void fatalError(SAXParseException e)
<h6>     {
<h6>          // throw e;
<h6>          // System.out.println("SAP Fatal Error" + e.getMessage());
<h6>
<h6>     }
<h6>
<h6>}
<h6>
<h6>Unfortunately the program always stopped while catching the first error. Check the below log.
<h6>
<h6>com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
<h6>ERRORS :
<h6>cvc-simple-type : information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is not valid, because it's value does not satisfy the constraints of facet 'minLength' with value '1'.
<h6>cvc-data : information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is is not valid with respoct to the corresponding simple type definition.
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is associated with invalid data.
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item '/:ShipNotice[1]' is not valid with <h6>respect to it's complex type definition..
<h6> -> com.sap.engine.lib.xml.parser.ParserException:
<h6>
<h6>
<h6>I tried using Xerces and JAXP to do validation, the same error happened. I have no idea on this. Does xi has its own error <h6>handler logic? Is there any body can make me get out of this?
<h6>Thanks.

Error in parsing xsd schema using jaxb !!

Similar Messages

Maybe you are looking for