The question is, are those xsi:types necessary according to the schema
or not. Example:
<js:SubmitJob>
<job xsi:type="js:UserJob">
According to the schema:
<element name="job" type="js:UserJob" ....>
Thus, the xsi:type is irrelevant.
Next:
<vJobs xsi:type="js:JobList">
Schema:
<element name="vJobs" type="js:Job" ....
Job is a Subclass of JobList. Thus, it's invalid to have an xsi:type
of JobList there. That's not valid.
Next:
<vJobs xsi:type="js:Job">
The schema say's it's already a "Job", thus, the xsi:type is not needed.
Next:
<vImgLayers xsi:type="js:ImgLayer">
Schema:
<element name="vImgLayers" type="js:ImgLayer" ....
Thus, irrelevant.
So, the _client.xml message is definitely invalid as the vJobs element
cannot be a js:Job.
Dan
On Jul 28, 2008, at 1:10 PM, Benjamin Coiffe wrote:
The wsdl was not attached in the first message…
Benjamin Coiffe
From: Benjamin Coiffe [mailto:[EMAIL PROTECTED]
Sent: 28 July 2008 18:02
To: [EMAIL PROTECTED]
Subject: xsi:types declaration missing
Hi,
I have issues getting a web service integration working with the
wsdl attached in this email. The problem is simple: because some
“xsi:type” declarations are missing, the web service does not manage
to handle the message, sent by a CXF, client nicely.
I attached the cxf soap message (definiens_cxf.xml) and the right
one (definiens_client.xml) where you can see by youself that the
“Job” type and “UserJob” type are missing in the cxf message.
Is there a reason for this? Is this a known issue? Is there a
workaround?
I am using CXF 2.1.
Thanks,
Benjamin Coiffe
<<definiens_cxf.xml>> <<definiens_client.xml>>
<<DiaJS.wsdl>>
<definiens_cxf.xml><definiens_client.xml>
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
