Re: PLEASE PLEASE HELP - Castor porblem

From: ZJT (zjt1114_at_yahoo.com)
Date: 02/09/04


Date: 8 Feb 2004 19:20:00 -0800

cpptutor2000@yahoo.com (Gandu) wrote in message news:<3c7c9804.0401112216.208ff066@posting.google.com>...
> I am a newbie to Castor. I downloaded all the jar files, made changes
> to the classpath etc, but I keep on getting exceptions being thrown.
>
> The XML schema file is as follows:
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="catalog">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="book" minOccurs="0" maxOccurs="unbounded">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="author" type="xsd:string"/>
> <xsd:element name="title" type="xsd:string"/>
> <xsd:element name="genre" type="xsd:string"/>
> <xsd:element name="price" type="xsd:float"/>
> <xsd:element name="publish_date" type="xsd:date"/>
> <xsd:element name="description" type="xsd:string"/>
> </xsd:sequence>
> <xsd:attribute name="id" type="xsd:string"/>
> </xsd:complexType>
> </xsd:element>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
>
> If I type in:
> C:\>java org.exolab.castor.builder.SourceGenerator -i
> C:\\Temp\\Test.xsd
>
> I get the error message:
> Exception in thread "main" java.lang.IllegalArgumentException: The
> prefix 'xml' is reserved (XML 1.0 Specification) and cannot be
> declared.
> at org.exolab.castor.xml.Namespaces.addNamespace(Namespaces.java:130)
> at org.exolab.castor.xml.UnmarshalHandler.startPrefixMapping(UnmarshalHandler.java:1953)
> at org.apache.xerces.parsers.AbstractSAXParser.startNamespaceMapping(Unknown
> Source)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
> Source)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
> Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
> Source)
> at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown
> Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> Source)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:583)
> at org.exolab.castor.mapping.Mapping.loadMappingInternal(Mapping.java:515)
> at org.exolab.castor.mapping.Mapping.loadMapping(Mapping.java:441)
> at org.exolab.castor.xml.schema.SimpleTypesFactory.loadTypesDefinitions(SimpleTypesFactory.java:414)
> at org.exolab.castor.xml.schema.SimpleTypesFactory.getType(SimpleTypesFactory.java:380)
> at org.exolab.castor.xml.schema.SimpleTypesFactory.getBuiltInType(SimpleTypesFactory.java:202)
> at org.exolab.castor.xml.schema.Schema.getSimpleType(Schema.java:919)
> at org.exolab.castor.xml.schema.Schema.getSimpleType(Schema.java:858)
> at org.exolab.castor.xml.schema.TypeReference.resolveTypeReference(TypeReference.java:113)
> at org.exolab.castor.xml.schema.TypeReference.getType(TypeReference.java:69)
> at org.exolab.castor.xml.schema.ElementDecl.getType(ElementDecl.java:327)
> at org.exolab.castor.xml.schema.ElementDecl.validate(ElementDecl.java:743)
> at org.exolab.castor.xml.schema.Group.validate(Group.java:471)
> at org.exolab.castor.xml.schema.ComplexType.validate(ComplexType.java:795)
> at org.exolab.castor.xml.schema.ElementDecl.validate(ElementDecl.java:748)
> at org.exolab.castor.xml.schema.Group.validate(Group.java:471)
> at org.exolab.castor.xml.schema.ComplexType.validate(ComplexType.java:795)
> at org.exolab.castor.xml.schema.ElementDecl.validate(ElementDecl.java:748)
> at org.exolab.castor.xml.schema.Schema.validate(Schema.java:1466)
> at org.exolab.castor.builder.SourceGenerator.generateSource(SourceGenerator.java:312)
> at org.exolab.castor.builder.SourceGenerator.generateSource(SourceGenerator.java:394)
> at org.exolab.castor.builder.SourceGenerator.generateSource(SourceGenerator.java:425)
> at org.exolab.castor.builder.SourceGenerator.main(SourceGenerator.java:760)
>
> Any help would be greatly appreciated. Thanks in advance for your
> help.

For Castor 0.9.5.2

The issue occurs with newer versions of Xerces than the version 1.4
that ships with Castor. The older version works ok. For some reason,
when the newer version of Xerces encounters an "xml" prefixed
attribute, such as "xml:lang" it tries to automatically start a prefix
mapping for "xml". Which, in my opinion, is technically incorrect.
They shouldn't be doing that. According to the w3c, the "xml" prefix
should never be declared.

The reason it started appearing in the new Castor (0.9.5.2), was
because of a switch to SAX 2 by default during unmarshalling.

Solution:
A built in work-around has been checked into the Castor CVS and will
automatically exist in any post 0.9.5.2 releases. For those who are
using 0.9.5.2 and can't upgrade I found a simple workaround (tested
with Xerces 2.5) , at first I thought about disabling namespace
processing in Xerces, but then realized that it's already disabled by
default by Castor...so I have no idea why they call
#startPrefixMapping when namespace processing has been disabled. But
in any event... explicitly enabling namespace processing seems to fix
the problem:

      in the castor.properties file change the following line:

      org.exolab.castor.parser.namespaces=false

      to:

      org.exolab.castor.parser.namespaces=true
              Note: that work-around has only been tested with Xerces
2.5.



Relevant Pages

  • Re: xml pour remplacer une base de donnée ?
    ... > Une très bonne solution est à mon avis d'utiliser une api de sérialisation ... > d'objets java en XML. ... > L'exemple le plus édifiant est sans nul doute Castor ...
    (comp.lang.java.databases)
  • Re: parsing string data through castor
    ... This is normal behavior for XML. ... Given below is the xml input before and after marshaling with castor ... <ScriptConfiguration> ...
    (comp.lang.java.programmer)
  • Re: ADO.NET Dataset equivalent using Java?
    ... >programmatically define relationships and output as XML using an XML ... However I am very familiar with .NET framework. ... >in Java specifically that would allow me to hand design an XML ... I looked at Castor - Zeus ...
    (comp.lang.java.programmer)
  • Re: parsing string data through castor
    ... >> I'm trying to parse string data using castor and it looks like the new ... >> lines are getting lost. ... This is normal behavior for XML. ...
    (comp.lang.java.programmer)
  • Re: Suche Java-Bibliothek zur Analyse von XML-Schemata
    ... Speziell wenn Du das XML Schema nicht nur lesen, ... Aber auch wenn Du es nur einlesen willst, um das Schema in aufbereiteter Form zur Verfügung zu haben, kann ich XSD empfehlen. ... Allerdings ist es komplexer als Castor bzw. Xerces, so dass Du je nach Aufgabenstellung evtl. ...
    (de.comp.text.xml)