RE: [wsdm] Issues with compiling the most current wsdl

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

Either map URLs to the local file locations or your approach is fine.

For the interop we should be using fixed WS-ResourceProperties currently publicly available at http://www.oasis-open.org/archives/wsdm/200403/bin00001.bin 

The wsrp:ErrorMessage may need to be fixed. Just take the file above, fix it and send it back to the list as an attachment. After validating it we may all use it. The URL to your file will be public immediately after your message is archived.

Right now, DO NOT use  http://www-106.ibm.com/developerworks/webservices/library/ws-resource/WS-ResourceProperties.wsdl.


-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788

-----Original Message-----
From: Warren Roberts [mailto:wroberts@webmethods.com] 
Sent: Monday, March 29, 2004 3:55 PM
To: wsdm@lists.oasis-open.org
Cc: Akshay Kumar
Subject: [wsdm] Issues with compiling the most current wsdl

I've forwarded an email that I received from the engineer who is implementing our webservice.  He is using Axis to compile the wsdl.  

  Should the wsdl refer to oasis to get the namespace and schema? 
  Should  wsrp:ErrorMessage be defined somewhere?

The Feb 19th wsdl compiles fine but we have to modify the more recent wsdl's to get them to compile.  Do the wsdl's need to be modified before compiling them?

Any guidance would be appreciated.

Thanx
Warren

=========================================================================
 Hi Warren;
I tried to import the new WSDL from the latest docs that you sent me. I have been able to compile the WSDL, although with the following changes.
I still have to put some dummy implementation and try the generated code out though.

1)  The latest WSDL has namespace and schema locations defined like:

            <import
namespace="http://docs.oasis-open.org/wsdm/2004/04/muws-0.5/wsdl";
location="http://docs.oasis-open.org/wsdm/2004/04/muws-0.5/wsdl"/>
             <import
namespace="http://docs.oasis-open.org/wsdm/2004/04/mows-0.5/wsdl";
location="http://docs.oasis-open.org/wsdm/2004/04/mows-0.5/wsdl"/>
            
            <xs:import
namespace="http://docs.oasis-open.org/wsdm/2004/04/muws-0.5/schema";
schemaLocation="http://docs.oasis-open.org/wsdm/2004/04/muws-0.5/schema"/>
             <xs:import
namespace="http://docs.oasis-open.org/wsdm/2004/04/mows-0.5/schema";
schemaLocation="http://docs.oasis-open.org/wsdm/2004/04/mows-0.5/schema"/>

I had to change these to the ones like in Feb 19th WSDL.

<import namespace="urn:wsdm:muws-wsdl" location="MUWS.wsdl"/>
            <import namespace="urn:wsdm:mows-wsdl" location="MOWS.wsdl"/>
                                    
            <xs:import namespace="urn:wsdm:muws-xs"
schemaLocation="MUWS.xsd"/>
             <xs:import namespace="urn:wsdm:mows-xs"
schemaLocation="MOWS.xsd"/>

2) The latest and the Feb 19th WSDLs both refer to the Resource Property message type ----- "wsrp:ErrorMessage"

<fault  name="UnknownResource" 
                   message="wsrp:ErrorMessage" />
            <fault  name="InvalidResourcePropertyQName" 
                   message="wsrp:ErrorMessage" />     

However, there is no such "ErrorMessage" defined in the http://www-106.ibm.com/developerworks/webservices/library/ws-resource/WS-Res
ourceProperties.wsdl document.

So I had to change the Fault messages to wsrp:ResourceUnknownFault and InvalidResourcePropertyQNameFault respectively, which I think are defined in the WS-ResourceProperties.wsdl

<fault  name="UnknownResource" 
                   message="wsrp:ResourceUnknownFault" />
             <fault  name="InvalidResourcePropertyQName" 
                   message="wsrp:InvalidResourcePropertyQNameFault" />   


Wanted to discuss the bearings that these changes may/mat not have on the project.

Will try your desk number in a while.

Thanks............

-akshay

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.