You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> on 2003/11/06 06:10:50 UTC
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Hi dims,All
> We CANNOT modify any of the existing WSDL's.
> If the schema is a valid schema, the parser should NOT die.
yes dims, I bealive there are few schema's in the WSDL's at axis tests
that are not **VALIED** (I need help to decide is it so)
I have append all these occurences of errors at the end of the mail. We
should adressed each one and get it **stright** how to address each.
To get all test working we need to adress following
1)what to do with 1999 XSD type
*jaxme support it?
*axis going to drop them?
2)what to do with types that are not belong to XSD nor SOAPENC. (most
are interoperability types.)
*does axis going to drop them ?
*we need to import their schema's to the dom node we are parsing
*jaxme support it?
3)What are we going to do with erronous schema's
we have to agreed on which are errornous or not.they are listed below
Thanks
Srinath
==================== possible errors ================================
1)the ./test/wsdl/ram/ram.wsdl has two schema's inside the type. The two
schema's has cross dependencies. We can parse only one at a time. So a
error is enavitable.
2)/test/wsdl/header/header.wsdl has not defined the target namespace in
the <schema> tag but define it in the <definition> tag. So as far as the
schema is concerned the targetnamespace is "" ?
3)/test/wsdl/types/CommprihensiveType.wsdl has a ComplexType direct
inside the sequence tag. XSD schema say's "It consists of a list of
particles, i.e. element declarations, wildcards and model groups" and
<complexType> is not a particle.
4)AXIS_HOME/test/wsdl/interop4/groupG/dime/rpc/dime-rpc.wsdl has <import namespace="http://schemas.xmlsoap.org/soap/encoding/"
location="http://schemas.xmlsoap.org/soap/encoding/" />
location should be schemalocation.
5)./test/wsdl/dataset/DataService.wsdl has <s:element ref="s:schema" />
what does that mean ??????????????????? The author of the WSDL might
mean that s:schema is a element, but to best of my knowladge that is
not.
=============================================================================
> --- Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> wrote:
> >
> > Hi Jochen;
> >
> > I think now jaxme is almost ready to parsing wsdl's without problem.
> >
> > I run all wsdl in the axis test through the Jaxme parser. result
> > attached. few error there. Shall we consult dims to finalize what to
> > support and what should we can leave out. (purposed solutions are inside
> > ** X**)
> >
> > probs
> > =====
> > 1)type 1999 schema namespace not supported **we should support**
> >
> >
> 2){http://test.globus.org/types}*,{http://soapinterop.org/}*,{http://java.sun.com/jax-rpc-ri/internal}*types
> > (WSDL consider they known inbuild types??)
> > **should not supported**
> > 3)Can jaxme support anyType ... if no type defined it should considered
> > to anyType
> > **should support**
> > 4)errornous schemas - see under ERRONOUS SCHEMAS in attachemant for
> > information.
> > **should fixed in the axis cvs ***
> >
> > Srinath
> >
> > BTW - Jochen
> >
> > 1)I got through that (QName,QName) problem in openattributes by getting
> > the NameSpaceSupport from the XSSchema and find the NSURI of prefix.
> >
> > 2)dose open attributes work for the attribute as well?? I have to check
> > for make sure. Will send you a test case if there is a prob.
> > > --------- ANY TYPE
> >
> ----------------------------------------------------------------------------------------------------------------
> > [You must set either the 'ref' attribute, the 'type' attribute, the 'simpleType' child element,
> > or the 'complexType' child element.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupi/round4XSD.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/soap12/additional/soap12-add-test.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/soap12/assertion/soap12-test.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/types/ComprehensiveTypes.wsdl
> > has <s:element minOccurs="0" maxOccurs="1" name="inputAnyType" /> if anything not defined it
> > should be any type ????????????????????
> >
> > [Invalid element: The type {http://www.w3.org/2001/XMLSchema}anyType is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/soap12/additional/soap12-add-test.wsdl
> >
> > ----1999 namespace
> >
> -------------------------------------------------------------------------------------------------------------------
> > [Invalid element: The type {http://www.w3.org/1999/XMLSchema}string is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/arrays/ArrayTest.wsdl
> >
> > [Invalid element: The type {http://www.w3.org/1999/XMLSchema}int is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/inout/inout.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/marrays/MArrayTest.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/names/JavaNames.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/sequence/SequenceTest.wsdl
> >
> > [Unknown base type: {http://www.w3.org/1999/XMLSchema}string]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/filegen/FileGen.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/oneway/oneway.wsdl
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/refattr/refattr.wsdl
> >
> > --- UNSUPPORTED INBUILD TYPES ??
> > --------------------------------------------------------------------------------
> > [Invalid element: The type {http://test.globus.org/types}StringType is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/import2/types1/types2/importtypes.wsdl
> >
> > [Invalid 'restriction': Unknown base type {http://www.w3.org/2003/05/soap-encoding}Array]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/soap12/assertion/soap12-test.wsdl
> >
> > [The referenced element {http://soapinterop.org/}SOAPComplexType is undefined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupi/round4XSD.wsdl
> >
> > [Invalid element: The type {http://java.sun.com/jax-rpc-ri/internal}vector is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/adaptive/adaptive.wsdl
> >
> > [Invalid element: The type {http://soapinterop.org/types}SOAPStructFault is not defined.]
> >
> /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupH/complexDocLit/complex-doc-literal.wsdl
> >
> > [Invalid element: The type {http://soapinterop.org/person}Person is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop3/compound2/Compound2.wsdl
> >
> > [Invalid element: The type {http://soapinterop.org/types}ArrayOfString is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupH/simpleDocLit/simple-doc-literal.wsdl
> >
> > [Invalid element: The type {http://soapinterop.org/types}SOAPStruct is not defined.]
> >
> /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupH/complexDocLit/complex-doc-literal.wsdl
> >
> > [Invalid element: The type {http://soapinterop.org/types}ArrayOfInt is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupH/simpleDocLit/simple-doc-literal.wsdl
> >
> -------------------------------------------------------------------------------------------------------------------
> >
> >
> > ---------- ERRONOUS SCHEMAS ------- GOING TO CHANGED
> > ----------------------------------------------
> > [Invalid element: The type {urn:header.wsdl.test}HeaderType is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/header/header.wsdl
> >
> > [The 'base' type {http://www.w3.org/2001/XMLSchema}base64Binary of 'simpleContent/restriction'
> > is simple. It ought to be a complex type with simple content: ]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupG/dime/doc/dime-doc.wsdl
> >
> > [Unknown child element 'xsd:complexType' for bean
> > org.apache.ws.jaxme.xs.xml.impl.XsESequenceImpl]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/types/ComprehensiveTypes.wsdl
> >
> > Complex type inside the sequence TAG ???????????????????????????????????
> >
> > [Invalid element: The type {urn:ram}ArrayOf_tns1_Fee is not defined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/ram/ram.wsdl
> >
> > [java.lang.IllegalStateException: Unknown attribute of
> > org.apache.ws.jaxme.xs.xml.impl.XsEImportImpl: location]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/interop4/groupG/dime/rpc/dime-rpc.wsdl
> > has
> > <import namespace="http://schemas.xmlsoap.org/soap/encoding/"
> > location="http://schemas.xmlsoap.org/soap/encoding/" />
> > should be schemaLocation
> >
> > [The referenced element {http://www.w3.org/2001/XMLSchema}schema is undefined.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/dataset/DataService.wsdl
> > has <s:element ref="s:schema" /> what does that mean ???????????????????
> >
> >
> > ------- NOT SURE -----------------------------------------------------
> > [java.lang.IllegalStateException: Unknown attribute of
> > org.apache.ws.jaxme.xs.xml.impl.XsTComplexTypeImpl: final]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/wrapped_holders/thing.wsdl
> > has ...
> > <s:complexType name="AThingResponse" final="restriction">
> > what does this mean ????????
> >
> > [java.lang.IllegalStateException: This is a simple type.]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/multiref/MultiRefTest.wsdl
> >
> > ---------------- need to support
> > -----------------------------------------------------------------------------
> > [java.lang.IllegalStateException: Unknown attribute of
> > org.apache.ws.jaxme.xs.xml.impl.XsTAttributeImpl: arrayType]
> > /home/cvs/workspace/jaxmeReEng/./test/wsdl/addrNoImplSEI/AddressBook.wsdl
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Srinath Perera wrote:
> but reading 1999 types as 2001 types (which we can do by extending the
> parser) will not do as Axis should able o work with e.g. .NET client
Is the .NET client using the 1999 namespace? If so, I understand that it
is a requirement to support this namespace. However, that makes it only
more important to understand what the differences are.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Srinath Perera wrote:
> but reading 1999 types as 2001 types (which we can do by extending the
> parser) will not do as Axis should able o work with e.g. .NET client
Is the .NET client using the 1999 namespace? If so, I understand that it
is a requirement to support this namespace. However, that makes it only
more important to understand what the differences are.
Jochen
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi Jochen;
> My guess would be, that one can simply change the 1999 namespace to the
> current 2001 namespace, because most probably the features which have
> changed haven't been used too much.
We can change the namespace of the WSDL to the 2001. (we have to
consider diffrent view before do that)
but reading 1999 types as 2001 types (which we can do by extending the
parser) will not do as Axis should able o work with e.g. .NET client
> > 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> > are interoperability types.)
> > *does axis going to drop them ?
> > *we need to import their schema's to the dom node we are parsing
> > *jaxme support it?
>
> My suggestion would be some kind of pluggability. In fact, one can even
> imagine that the XS parser should be able to add external types
> automatically. That would make these additional types a simple issue of
> configuration.
I might have done a mistake here, I think this error is becouse the WSDL
has two cross dependent schema's let me check it agien.
> I have just a very basic idea about what Axis does, so please help me
> by answering the following questions:
>
> - Does speed matter?
> - How much does it happen that a schema is being parsed? First use
> only or any use?
> - Are external datatypes changing?
>
> In other words: Is it possible or required to use a cache?
no this part genarate code for Axis ... This part of axis(WSDL2Java) is
run only once before service deployment. So give bit of speed for the
better code can be acceptable.
Srinath
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi Jochen;
> My guess would be, that one can simply change the 1999 namespace to the
> current 2001 namespace, because most probably the features which have
> changed haven't been used too much.
We can change the namespace of the WSDL to the 2001. (we have to
consider diffrent view before do that)
but reading 1999 types as 2001 types (which we can do by extending the
parser) will not do as Axis should able o work with e.g. .NET client
> > 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> > are interoperability types.)
> > *does axis going to drop them ?
> > *we need to import their schema's to the dom node we are parsing
> > *jaxme support it?
>
> My suggestion would be some kind of pluggability. In fact, one can even
> imagine that the XS parser should be able to add external types
> automatically. That would make these additional types a simple issue of
> configuration.
I might have done a mistake here, I think this error is becouse the WSDL
has two cross dependent schema's let me check it agien.
> I have just a very basic idea about what Axis does, so please help me
> by answering the following questions:
>
> - Does speed matter?
> - How much does it happen that a schema is being parsed? First use
> only or any use?
> - Are external datatypes changing?
>
> In other words: Is it possible or required to use a cache?
no this part genarate code for Axis ... This part of axis(WSDL2Java) is
run only once before service deployment. So give bit of speed for the
better code can be acceptable.
Srinath
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 drop 1999
--- Sanjiva Weerawarana <sa...@watson.ibm.com> wrote:
> Its time to drop support for the 1999 namespace - that was a
> pre-standard version and if someone really needs it they
> can use Axis/1.1.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Jochen Wiedmann" <jo...@ispsoft.de>
> To: <he...@vijayaba.cse.mrt.ac.lk>
> Cc: <di...@yahoo.com>; <ws...@apache.org>; <ax...@ws.apache.org>
> Sent: Thursday, November 06, 2003 12:08 PM
> Subject: Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
>
>
> > Srinath Perera wrote:
> >
> > > 1)what to do with 1999 XSD type
> > > *jaxme support it?
> > > *axis going to drop them?
> >
> > Before being able to decide, whether the XS parser can support another
> > namespace, I need someone who's able to describe then differences in
> > detail.
> >
> > My guess would be, that one can simply change the 1999 namespace to the
> > current 2001 namespace, because most probably the features which have
> > changed haven't been used too much.
> >
> >
> > > 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> > > are interoperability types.)
> > > *does axis going to drop them ?
> > > *we need to import their schema's to the dom node we are parsing
> > > *jaxme support it?
> >
> > My suggestion would be some kind of pluggability. In fact, one can even
> > imagine that the XS parser should be able to add external types
> > automatically. That would make these additional types a simple issue of
> > configuration.
> >
> > I have just a very basic idea about what Axis does, so please help me
> > by answering the following questions:
> >
> > - Does speed matter?
> > - How much does it happen that a schema is being parsed? First use
> > only or any use?
> > - Are external datatypes changing?
> >
> > In other words: Is it possible or required to use a cache?
> >
> >
> > Jochen
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 drop 1999
--- Sanjiva Weerawarana <sa...@watson.ibm.com> wrote:
> Its time to drop support for the 1999 namespace - that was a
> pre-standard version and if someone really needs it they
> can use Axis/1.1.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Jochen Wiedmann" <jo...@ispsoft.de>
> To: <he...@vijayaba.cse.mrt.ac.lk>
> Cc: <di...@yahoo.com>; <ws...@apache.org>; <ax...@ws.apache.org>
> Sent: Thursday, November 06, 2003 12:08 PM
> Subject: Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
>
>
> > Srinath Perera wrote:
> >
> > > 1)what to do with 1999 XSD type
> > > *jaxme support it?
> > > *axis going to drop them?
> >
> > Before being able to decide, whether the XS parser can support another
> > namespace, I need someone who's able to describe then differences in
> > detail.
> >
> > My guess would be, that one can simply change the 1999 namespace to the
> > current 2001 namespace, because most probably the features which have
> > changed haven't been used too much.
> >
> >
> > > 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> > > are interoperability types.)
> > > *does axis going to drop them ?
> > > *we need to import their schema's to the dom node we are parsing
> > > *jaxme support it?
> >
> > My suggestion would be some kind of pluggability. In fact, one can even
> > imagine that the XS parser should be able to add external types
> > automatically. That would make these additional types a simple issue of
> > configuration.
> >
> > I have just a very basic idea about what Axis does, so please help me
> > by answering the following questions:
> >
> > - Does speed matter?
> > - How much does it happen that a schema is being parsed? First use
> > only or any use?
> > - Are external datatypes changing?
> >
> > In other words: Is it possible or required to use a cache?
> >
> >
> > Jochen
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Its time to drop support for the 1999 namespace - that was a
pre-standard version and if someone really needs it they
can use Axis/1.1.
Sanjiva.
----- Original Message -----
From: "Jochen Wiedmann" <jo...@ispsoft.de>
To: <he...@vijayaba.cse.mrt.ac.lk>
Cc: <di...@yahoo.com>; <ws...@apache.org>; <ax...@ws.apache.org>
Sent: Thursday, November 06, 2003 12:08 PM
Subject: Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
> Srinath Perera wrote:
>
> > 1)what to do with 1999 XSD type
> > *jaxme support it?
> > *axis going to drop them?
>
> Before being able to decide, whether the XS parser can support another
> namespace, I need someone who's able to describe then differences in
> detail.
>
> My guess would be, that one can simply change the 1999 namespace to the
> current 2001 namespace, because most probably the features which have
> changed haven't been used too much.
>
>
> > 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> > are interoperability types.)
> > *does axis going to drop them ?
> > *we need to import their schema's to the dom node we are parsing
> > *jaxme support it?
>
> My suggestion would be some kind of pluggability. In fact, one can even
> imagine that the XS parser should be able to add external types
> automatically. That would make these additional types a simple issue of
> configuration.
>
> I have just a very basic idea about what Axis does, so please help me
> by answering the following questions:
>
> - Does speed matter?
> - How much does it happen that a schema is being parsed? First use
> only or any use?
> - Are external datatypes changing?
>
> In other words: Is it possible or required to use a cache?
>
>
> Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Its time to drop support for the 1999 namespace - that was a
pre-standard version and if someone really needs it they
can use Axis/1.1.
Sanjiva.
----- Original Message -----
From: "Jochen Wiedmann" <jo...@ispsoft.de>
To: <he...@vijayaba.cse.mrt.ac.lk>
Cc: <di...@yahoo.com>; <ws...@apache.org>; <ax...@ws.apache.org>
Sent: Thursday, November 06, 2003 12:08 PM
Subject: Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
> Srinath Perera wrote:
>
> > 1)what to do with 1999 XSD type
> > *jaxme support it?
> > *axis going to drop them?
>
> Before being able to decide, whether the XS parser can support another
> namespace, I need someone who's able to describe then differences in
> detail.
>
> My guess would be, that one can simply change the 1999 namespace to the
> current 2001 namespace, because most probably the features which have
> changed haven't been used too much.
>
>
> > 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> > are interoperability types.)
> > *does axis going to drop them ?
> > *we need to import their schema's to the dom node we are parsing
> > *jaxme support it?
>
> My suggestion would be some kind of pluggability. In fact, one can even
> imagine that the XS parser should be able to add external types
> automatically. That would make these additional types a simple issue of
> configuration.
>
> I have just a very basic idea about what Axis does, so please help me
> by answering the following questions:
>
> - Does speed matter?
> - How much does it happen that a schema is being parsed? First use
> only or any use?
> - Are external datatypes changing?
>
> In other words: Is it possible or required to use a cache?
>
>
> Jochen
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Srinath Perera wrote:
> 1)what to do with 1999 XSD type
> *jaxme support it?
> *axis going to drop them?
Before being able to decide, whether the XS parser can support another
namespace, I need someone who's able to describe then differences in
detail.
My guess would be, that one can simply change the 1999 namespace to the
current 2001 namespace, because most probably the features which have
changed haven't been used too much.
> 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> are interoperability types.)
> *does axis going to drop them ?
> *we need to import their schema's to the dom node we are parsing
> *jaxme support it?
My suggestion would be some kind of pluggability. In fact, one can even
imagine that the XS parser should be able to add external types
automatically. That would make these additional types a simple issue of
configuration.
I have just a very basic idea about what Axis does, so please help me
by answering the following questions:
- Does speed matter?
- How much does it happen that a schema is being parsed? First use
only or any use?
- Are external datatypes changing?
In other words: Is it possible or required to use a cache?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: DOM->JAXME(ERRORNOUS SCHEMA'S)
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Srinath Perera wrote:
> 1)what to do with 1999 XSD type
> *jaxme support it?
> *axis going to drop them?
Before being able to decide, whether the XS parser can support another
namespace, I need someone who's able to describe then differences in
detail.
My guess would be, that one can simply change the 1999 namespace to the
current 2001 namespace, because most probably the features which have
changed haven't been used too much.
> 2)what to do with types that are not belong to XSD nor SOAPENC. (most
> are interoperability types.)
> *does axis going to drop them ?
> *we need to import their schema's to the dom node we are parsing
> *jaxme support it?
My suggestion would be some kind of pluggability. In fact, one can even
imagine that the XS parser should be able to add external types
automatically. That would make these additional types a simple issue of
configuration.
I have just a very basic idea about what Axis does, so please help me
by answering the following questions:
- Does speed matter?
- How much does it happen that a schema is being parsed? First use
only or any use?
- Are external datatypes changing?
In other words: Is it possible or required to use a cache?
Jochen