> Hi,
>
> This is how my wsdl file (deployed in SCA Native) looks like...
>
> <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:tns="http://native/camcontroller";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://native/camcontroller";>
> <wsdl:types>
> <xsd:schema
> targetNamespace="http://native/camcontroller";
>
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>
> xmlns:tns="http://native/camcontroller";
> elementFormDefault="qualified">
>
> <xsd:element name="moveCamera">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="zone" type="tns:Zone"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
> <xsd:element name="moveCameraResponse">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="moveCameraReturn" type="xsd:boolean"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
> <xsd:complexType name="Zone">
> <xsd:sequence>
> <xsd:element name="topX" type="xsd:int" />
> <xsd:element name="topY" type="xsd:int" />
> <xsd:element name="botX" type="xsd:int" />
> <xsd:element name="botY" type="xsd:int" />
> </xsd:sequence>
> </xsd:complexType>
>
>
> </xsd:schema>
> </wsdl:types>
>
> <wsdl:message name="moveCameraRequest">
> <wsdl:part element="tns:moveCamera" name="parameters"/>
> </wsdl:message>
>
> <wsdl:message name="moveCameraResponse">
> <wsdl:part element="tns:moveCameraResponse" name="parameters"/>
> </wsdl:message>
>
> <!-----Snipped--------->
>
> Like I mentioned before I am using this as a reference to the SCA native
> service When I use it is a reference with the SCA java 1.1 runtime this
> is the XML message that is passed
>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> ">
> <soapenv:Body>
> <_ns_:moveCamera xmlns:_ns_="http://native/camcontroller";>
> <p0:zone xmlns:p0="http://native/camcontroller";
> xmlns:p1="http://javaservice";>
>
> <p1:topX>320</p1:topX><p1:topY>240</p1:topY><p1:botX>10</p1:botX><p1:botY>10</p1:botY>
> </p0:zone>
> </_ns_:moveCamera>
> </soapenv:Body>
> </soapenv:Envelope>
>
> But when I use it as a reference to a SCA Java service with 1.1.1
> runtime this is the XML message that is passed
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Body>
> <_ns_:moveCamera xmlns:_ns_="http://native/camcontroller";>
> <p0:zone xmlns:p0="http://native/camcontroller";
> xsi:type="p1:Zone"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-Instance"; xmlns:p1="
http://com.siemens.hintegration";>
<p1:topX>320</p1:topX><p1:topY>240</p1:topY><p1:botX>10</p1:botX><p1:botY>10</p1:botY>
</p0:zone>
</_ns_:moveCamera>
</soapenv:Body>
</soapenv:Envelope>
At the SCA native end the XML is not being parsed properly.
It calls the appropriate method but in the method when the SDO object is
being accessed it throws an SDOException.
The Exception is this : "The Referenced object is Null"
The same setup used to work well with the 1.1 runtime that is why I
surmised that it could be extra xsi:type info that is causing the
exception.
Any pointers/help would be much appreciated.
Regards,
Altaf
-----Original Message-----
From: Raymond Feng [mailto:[EMAIL PROTECTED]
Sent: 22 April 2008 21:40
To: [email protected]
Subject: Re: SDO 1.1.1 RC1
Is p0:sdoArgName a global element in your XSD? If not, the xsi:type
seems to be appropriate. What problem are you experiencing w/ the
xsi:type?
Thanks,
Raymond
--------------------------------------------------
From: "Altaf Muneer" <[EMAIL PROTECTED]>
Sent: Tuesday, April 22, 2008 7:50 AM
To: <[email protected]>
Subject: RE: SDO 1.1.1 RC1
> Hi,
>
> I tried to use the fixed version, the messages get processed
> instantaneously which is great. Thanks for the quick response.
> But I faced some other problems...
> The previous version used to work well when I had a reference to the
> native service..
> Now the appropriate native service is called but there is an SDO
> exception being thrown on the native side when I try to use the SDO
> object.
> I have noticed that the xml messages that are exchanged have changed.
> I am pasting the respective xml messages below...
>
> Before the fix:
>
> Input msg:
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Body>
> <_ns_:methodName xmlns:_ns_="http://scaNativeNamespace";>
> <p0:sdoArgName
xmlns:p0="http://scaNativeNamespace";
> xmlns:p1="http://scaJavaNamespace";>
>
> <p1:attribute1>123</p1:attribute1><p1:attribute2>456</p1:attribute2>
> </p0:sdoArgName>
> </_ns_:methodName>
> </soapenv:Body>
> </soapenv:Envelope>
>
> After the fix(Tuscany-2240):
>
> Input msg:
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Body>
> <_ns_:methodName xmlns:_ns_="http://scaNativeNamespace";>
> <p0:sdoArgName
xmlns:p0="http://scaNativeNamespace";
> xsi:type="p1:sdoComplexTypeName"
> xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";
> xmlns:p1="http://scaJavaNamespace
> ">
>
> <p1:attribute1>123</p1:attribute1><p1:attribute2>456</p1:attribute2>
> </p0:sdoArgName>
> </_ns_:methodName>
> </soapenv:Body>
> </soapenv:Envelope>
>
> There is an extra xsi tag that is being added. This problem existed in
> the 1.0.1 release of SCA and was fixed in the 1.1 version...
>
> Is there a way I can work around this problem? Any help would be
> greatly appreciated.
>
> Regards,
> Altaf
>
> -----Original Message-----
> From: ant elder [mailto:[EMAIL PROTECTED]
> Sent: 21 April 2008 17:20
> To: tuscany-dev; Tuscany Users
> Subject: SDO 1.1.1 RC1
>
> There's now a preview SDO 1.1.1 release available at
> http://people.apache.org/~antelder/tuscany/sdo/1.1.1-RC1/. The only
> difference between this and the just released 1.1 release is the fix
> http://issues.apache.org/jira/browse/TUSCANY-2240. I'll leave this a
> little while before calling a vote to give time for reviews and also
> would be good if possible to also get a fix for using EMF 2.4 as a
> user has asked about that.
>
> ...ant
>
Important notice:This e-mail and any attachment thereto contains corporate
proprietary information. If you have received it by mistake, please notify
us immediately by reply e-mail and delete this e-mail and its attachments
from your system. Thank You.
