Malisetti, Ramanjaneyulu wrote:
We experienced similar problem. We solved this problem by editing WSDL to have
XS:any for the DataObject type. It means, our WSDL has the following.
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://sdo.commonj/"; version="1.0" xmlns="http://sdo.commonj//";>
<xs:complexType name="dataObject">
<xs:sequence>
<xs:element name="sdo" type="xs:anyType"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Regards
Raman
It shouldn't be difficult (about 2 lines of code) to update the Tuscany
WSDL generator to generate xs:anyType for the Java interface type
commonj.sdo.DataObject and remove the import for http://sdo.commonj/.
If this is a suitable fix for the problem, please create a JIRA.
Simon
-----Original Message-----
From: Millies, Sebastian [mailto:[email protected]]
Sent: Thursday, November 18, 2010 4:12 PM
To: [email protected]
Subject: Tuscany generated incorrect WSDL for SDO
Hello there,
I'd like to ask this question again, perhaps meanwhile someone has a fresh idea.
How can I create an SCA service in Tuscany 1.6 that uses dynamic SDOs (backed by
xsd-files) and has a webservice binding with a useful wsdl?
I have created a service using dynamic SDOs. The wsdl - generated by the
Tuscany 1.6 runtime and downloaded from the service URL - cannot be imported in
SOAP UI 3.5.1. It gives a NullPointerException. I attach the service interface
and generated wsdl to this post.
Simon Laws found a namespace issue with the generated wsdl (see below). But
unfortunately I have not been able to make progress with this issue.
-- Sebastian
-----Original Message-----
From: Simon Laws [mailto:[email protected]]
Sent: Friday, September 03, 2010 3:36 PM
To: [email protected]
Subject: Re: FW: Is SDO/DAS specific to a data model or generic
[snip]
I'm not really an expert on SDO but the issue with the WSDL that
Tuscany generated is that it includes
<xs:import namespace="http://sdo.commonj/"; />
Which doesn't resolve to anything sensible. The type dataObject is
defined here [1] but even then that's in a different namespace.
IIUC the dynamic SDO data object is intended to provide a dynamic
set/get given element name style interface over an xml model. This
allows you to define service interfaces that take arbitrary data
types
(imagine the scenario where you want to implement a service that
process every message, regardless or message type, entering a
message queue for example). Assuming that the dynamic object is
backed by
some
known type model then I don't see why it shouldn't be persisted but
I'm getting out of my depth re. what the Tuscany implementation
actually does.
The guy that knows about this stuff is away today I think so you may
get a real answer on Monday.
[1] http://svn.apache.org/repos/asf/tuscany/sdo-java/trunk/sdo-
api/src/main/resources/xml/sdoModel.xsd
Simon
--
Apache Tuscany committer: tuscany.apache.org Co-author of a book
about Tuscany and SCA: tuscanyinaction.com
