You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Brian Lund <br...@concur.com> on 2010/02/03 20:56:28 UTC
Multiple schemas with different target namespaces
Apart from creating a new XSD file for each namespace, is it possible to
declare multiple schemas with different target namespaces in the types
element of a WSDL included in a BPEL? ODE seems to deploy the process just
fine, but I see errors in the logs.
Re: Multiple schemas with different target namespaces
Posted by Brian Lund <br...@concur.com>.
Eesh, sorry 'bout that. Here's the error, and snippet of the wsdl that this
particular error refers to:
[2010-02-03 11:32:53,656] ERROR - Schema error
{org.apache.ode.utils.xsd.SchemaModelImpl}
::::2:964:1002:src-import.3.1: The namespace attribute,
'http://com.rightnow.api/xsd', of an <import> element information item must
be identical to the targetNamespace attribute,
'http://connection.crm.soa.it.concur.com/xsd', of the imported document.
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)
at
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)
at
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadInputList(Unknown
Source)
at
org.apache.ode.utils.xsd.SchemaModelImpl.newModel(SchemaModelImpl.java:95)
at
org.apache.ode.bpel.compiler.WSDLRegistry.getSchemaModel(WSDLRegistry.java:1
03)
<wsdl:types>
<xs:schema attributeFormDefault="qualified"
elementFormDefault="unqualified"
targetNamespace="http://com.rightnow.api/xsd">
<xs:complexType name="RNOWUtil">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="iDL"
nillable="true" type="ax277:RNOWIDLClass" />
<xs:element minOccurs="0" name="serverURL" nillable="true"
type="xs:string" />
<xs:element minOccurs="0" name="toolkitVersion" nillable="true"
type="xs:string" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="RNOWIDLClass">
<xs:sequence>
<xs:element minOccurs="0" name="attributes" nillable="true"
type="xs:anyType" />
<xs:element minOccurs="0" name="name" nillable="true"
type="xs:string" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="RNOWObjectFactory">
<xs:complexContent>
<xs:extension base="ax277:RNOWUtil">
<xs:sequence />
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
...
<xs:schema xmlns:ax278="http://com.rightnow.api/xsd"
attributeFormDefault="qualified" elementFormDefault="unqualified"
targetNamespace="http://connection.crm.soa.it.concur.com/xsd">
<xs:import namespace="http://com.rightnow.api/xsd" />
<xs:complexType name="ConnectionFactory">
<xs:sequence>
<xs:element minOccurs="0" name="connection" nillable="true"
type="ax277:RNOWObjectFactory" />
<xs:element minOccurs="0" name="connectionURI" nillable="true"
type="xs:string" />
<xs:element minOccurs="0" name="password" nillable="true"
type="xs:string" />
<xs:element minOccurs="0" name="username" nillable="true"
type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
On 2/3/10 12:05 PM, "Antoine Toulme" <an...@gmail.com> wrote:
> What errors do you see ? It should be possible, but there are a few catchs
> there, between including or importing the schema for example.
>
> On Wed, Feb 3, 2010 at 11:56, Brian Lund <br...@concur.com> wrote:
>
>> Apart from creating a new XSD file for each namespace, is it possible to
>> declare multiple schemas with different target namespaces in the types
>> element of a WSDL included in a BPEL? ODE seems to deploy the process just
>> fine, but I see errors in the logs.
>>
Re: Multiple schemas with different target namespaces
Posted by Antoine Toulme <an...@gmail.com>.
What errors do you see ? It should be possible, but there are a few catchs
there, between including or importing the schema for example.
On Wed, Feb 3, 2010 at 11:56, Brian Lund <br...@concur.com> wrote:
> Apart from creating a new XSD file for each namespace, is it possible to
> declare multiple schemas with different target namespaces in the types
> element of a WSDL included in a BPEL? ODE seems to deploy the process just
> fine, but I see errors in the logs.
>
Re: Multiple schemas with different target namespaces
Posted by Renat Zubairov <re...@sopera.de>.
Hello Brian,
It is possible to declare multiple <xsd:schema> elements within <wsdl:types>, so that each schema elemet would have it's own targetNamespace. However each individual <xsd:schema> element could only declare one targetNamespace, so basically if you have an XSD file then you have a single xsd:schema element in it. So in most of the cases one XSD -> single namespace, one WSDL -> multiple xsd:schemas -> each one namespace so one WSDL -> many namespaces.
Hope this helps.
Renat
On 03.02.10 20:56, "Brian Lund" <br...@concur.com> wrote:
Apart from creating a new XSD file for each namespace, is it possible to
declare multiple schemas with different target namespaces in the types
element of a WSDL included in a BPEL? ODE seems to deploy the process just
fine, but I see errors in the logs.