Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 55449 invoked from network); 23 Sep 2003 10:26:08 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 23 Sep 2003 10:26:08 -0000 Received: (qmail 8754 invoked by uid 500); 23 Sep 2003 10:25:37 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 8670 invoked by uid 500); 23 Sep 2003 10:25:36 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 8645 invoked from network); 23 Sep 2003 10:25:34 -0000 In-Reply-To: <018601c381a1$9cba03e0$0200a8c0@Gary005> To: axis-dev@ws.apache.org Subject: RE: Java2WSDL problem MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.1CF1 March 04, 2003 From: Ajay Gondhiya Message-ID: Date: Tue, 23 Sep 2003 10:25:17 +0000 X-MIMETrack: Serialize by Router on camdmail01/Server/Accelrys(Release 6.0.2CF1|June 9, 2003) at 23/09/2003 10:25:48, Serialize complete at 23/09/2003 10:25:48 Content-Type: multipart/alternative; boundary="=_alternative 00394F5C65256DAA_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 00394F5C65256DAA_= Content-Type: text/plain; charset="US-ASCII" Gary, May be my lack of understanding but since Axis (Java2WSDL tool) generates WSDL with the http://schemas.xmlsoap.org/wsdl/soap as wsdlsoap namespace, should it not abide by the schema? Can it internally use a schema (e.g. WSDL 1.1 that you are refering to) which is not same as the one at http://schemas.xmlsoap.org/wsdl/soap? In other words if Axis is using a WSDL 1.1 schema that does not have "name" attribute, shouldn't the generated WSDL contain the wsdlsoap namespace pointing to the URL for that schema? I am not sure even if Axis does that, whether Microsoft's VS.NET sproxy tool will use correct schema and not complain about "name" attribute or not ... Thanks, Ajay "Gary L Peskin" 09/23/2003 12:39 PM Please respond to axis-dev@ws.apache.org To cc Subject RE: Java2WSDL problem Thanks, Ajay, I see where you're getting this now. However, I have no idea where the schema shown at http://schemas.xmlsoap.org/wsdl/soap actually comes from. It doesn't seem to match the WSDL 1.1 schema that I referenced in my earlier post. Perhaps it is from the WSDL 1.0 schema, which I can't seem to find anywhere. Or, perhaps it is some Microsoft-specific WSDL specification. In any event, I believe that Axis supports WSDL 1.1 which doesn't include the name attribute. Gary -----Original Message----- From: Ajay Gondhiya [mailto:AjayGondhiya@accelrys.com] Sent: Monday, September 22, 2003 11:16 PM To: axis-dev@ws.apache.org Subject: RE: Java2WSDL problem Thanks Gary ! The fault element in the binding seems to come from xmlns:wsdlsoap=" http://schemas.xmlsoap.org/wsdl/soap/" namespace in the generated (by Java2WSDL) WSDL. In this schema, fault is of type tFault - which has "name" attribute in addition to encodingStyle, namespace and use attributes. It also indicates that "name" is a required attribute. Ajay "Gary L Peskin" 09/22/2003 09:34 PM Please respond to axis-dev@ws.apache.org To cc Subject RE: Java2WSDL problem Ajay -- I'm a little confused here. As I read the WSDL 1.1 SOAP binding schema ( http://www.w3.org/TR/wsdl#A4.2), there is no name attribute on the wsdlsoap:fault element, just encodingStyle, namespace, and use which are already present. Do you have a schema reference that shows a name attribute on this element? Or, am I missing something? Gary -----Original Message----- From: Ajay Gondhiya [mailto:AjayGondhiya@accelrys.com] Sent: Monday, September 22, 2003 6:31 AM To: axis-dev@ws.apache.org Subject: Fw: Java2WSDL problem Reposting to see if someone out there can help me .. it seems to me like a bug but before filing a bug report I just want to run by the developers in case I have any misunderstanding ... Thanks a lot, Ajay ----- Forwarded by Ajay Gondhiya/Bangalore/Accelrys on 09/22/2003 06:58 PM ----- Ajay Gondhiya/Bangalore/Accelrys 09/16/2003 01:50 PM To axis-dev@ws.apache.org cc Subject Java2WSDL problem I am having a problem with Java2WSDL in Axis 1.0 & 1.1. The problem is when I declare an exception in my EJB interface and when Java2WSDL generates corresponding WSDL, in the binding information it does not generate "name" attribute for the SOAP fault. Because of this sproxy tool from .NET is not able to compile the WSDL to generate client side stubs. Has anyone faced similar problem? Could this be a bug in Axis 1.0/1.1 ... Thanks in advance for your help. Ajay EJB interface -------------------- public String getQueryCapability (String queryCapabilityID) throws QueryCapabilityNotFoundException WSDL - binding part only ------------------------------------- xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" .... other stuff .... <-------------------------------- "name" attribute MISSING HERE as per wsdlsoap namespace --=_alternative 00394F5C65256DAA_= Content-Type: text/html; charset="US-ASCII"
Gary,

May be my lack of understanding but since Axis (Java2WSDL tool) generates WSDL with the http://schemas.xmlsoap.org/wsdl/soap as wsdlsoap namespace, should it not abide by the schema? Can it internally use a schema (e.g. WSDL 1.1 that you are refering to) which is not same as the one at http://schemas.xmlsoap.org/wsdl/soap?
In other words if Axis is using a WSDL 1.1 schema that does not have "name" attribute, shouldn't the generated WSDL contain the wsdlsoap namespace pointing to the URL for that schema? I am not sure even if Axis does that, whether Microsoft's VS.NET sproxy tool will use correct schema and not complain about "name" attribute or not ...
Thanks,

Ajay



"Gary L Peskin" <garyp@firstech.com>

09/23/2003 12:39 PM
Please respond to
axis-dev@ws.apache.org
To
<axis-dev@ws.apache.org>
cc
Subject
RE: Java2WSDL problem





Thanks, Ajay, I see where you're getting this now.  However, I have no idea where the schema shown at http://schemas.xmlsoap.org/wsdl/soap actually comes from.  It doesn't seem to match the WSDL 1.1 schema that I referenced in my earlier post.  Perhaps it is from the WSDL 1.0 schema, which I can't seem to find anywhere.  Or, perhaps it is some Microsoft-specific WSDL specification.
 
In any event, I believe that Axis supports WSDL 1.1 which doesn't include the name attribute.
 
Gary
-----Original Message-----
From: Ajay Gondhiya [mailto:AjayGondhiya@accelrys.com]
Sent: Monday, September 22, 2003 11:16 PM
To: axis-dev@ws.apache.org
Subject: RE: Java2WSDL problem

Thanks Gary !

The fault element in the binding seems to come from xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" namespace in the generated (by Java2WSDL) WSDL. In this schema, fault is of type tFault - which has "name" attribute in addition to encodingStyle, namespace and use attributes. It also indicates that "name" is a required attribute.

Ajay




"Gary L Peskin" <garyp@firstech.com>

09/22/2003 09:34 PM
Please respond to
axis-dev@ws.apache.org
To
<axis-dev@ws.apache.org>
cc
Subject
RE: Java2WSDL problem







Ajay --
 
I'm a little confused here.  As I read the WSDL 1.1 SOAP binding schema (http://www.w3.org/TR/wsdl#A4.2), there is no name attribute on the wsdlsoap:fault element, just encodingStyle, namespace, and use which are already present.  Do you have a schema reference that shows a name attribute on this element?
 
Or, am I missing something?
 
Gary
-----Original Message-----
From: Ajay Gondhiya [mailto:AjayGondhiya@accelrys.com]
Sent: Monday, September 22, 2003 6:31 AM
To: axis-dev@ws.apache.org
Subject: Fw: Java2WSDL problem


Reposting to see if someone out there can help me .. it seems to me like a bug but before filing a bug report I just want to run by the developers in case I have any misunderstanding ...
Thanks a lot,

Ajay

----- Forwarded by Ajay Gondhiya/Bangalore/Accelrys on 09/22/2003 06:58 PM -----
Ajay Gondhiya/Bangalore/Accelrys

09/16/2003 01:50 PM


To
axis-dev@ws.apache.org
cc
Subject
Java2WSDL problem





I am having a problem with Java2WSDL in Axis 1.0 & 1.1.

The problem is when I declare an exception in my EJB interface and when Java2WSDL generates corresponding WSDL, in the binding information it does not generate "name" attribute for the SOAP fault. Because of this sproxy tool from .NET is not able to compile the WSDL to generate client side stubs. Has anyone faced similar problem? Could this be a bug in Axis 1.0/1.1 ...

Thanks in advance for your help.

Ajay

EJB interface
--------------------

public String getQueryCapability (String queryCapabilityID)
                 throws QueryCapabilityNotFoundException

WSDL - binding part only
-------------------------------------
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
....
other stuff
....

<wsdl:binding name="QueryCapabilitySoapBinding" type="impl:QueryCapability">
  <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
  <wsdl:operation name="getQueryCapability">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="getQueryCapabilityRequest">
        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="aqs" use="encoded"/>
   </wsdl:input>
   <wsdl:output name="getQueryCapabilityResponse">
        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="aqs" use="encoded"/>
   </wsdl:output>
   <wsdl:fault name="QueryCapabilityNotFoundException">
        <wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="aqs" use="encoded"/>   <-------------------------------- "name" attribute MISSING HERE as per wsdlsoap namespace
   </wsdl:fault>
 </wsdl:operation>
</wsdl:binding>
--=_alternative 00394F5C65256DAA_=--