Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 89759 invoked from network); 7 Nov 2006 09:52:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Nov 2006 09:52:57 -0000 Received: (qmail 66423 invoked by uid 500); 7 Nov 2006 09:53:07 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 66402 invoked by uid 500); 7 Nov 2006 09:53:07 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 66391 invoked by uid 99); 7 Nov 2006 09:53:07 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 01:53:07 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of milinda.pathirage@gmail.com designates 64.233.162.203 as permitted sender) Received: from [64.233.162.203] (HELO nz-out-0102.google.com) (64.233.162.203) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 01:52:53 -0800 Received: by nz-out-0102.google.com with SMTP id 12so970422nzp for ; Tue, 07 Nov 2006 01:52:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=aKxczG//X//m+ybpF+cgkrieJqkM3jn/OeCrOMgHdGrkkbdyMTT3SgiYWpVwpOaz3En5lWBZoUh2ncWdITYSCdzHWS+SpdvQXo1TGTeMIsSGjWGC0dy7ayYsCd7Q239iYwEaA+ces3kLIyvO0TC9ftil70VvZ22pJtNXPYrN1VQ= Received: by 10.65.254.13 with SMTP id g13mr9751639qbs.1162892781394; Tue, 07 Nov 2006 01:46:21 -0800 (PST) Received: by 10.65.52.14 with HTTP; Tue, 7 Nov 2006 01:46:21 -0800 (PST) Message-ID: <22a059a60611070146p66e4054dibc3c17b8ad745197@mail.gmail.com> Date: Tue, 7 Nov 2006 15:16:21 +0530 From: "Milinda Pathirage" To: "Apache AXIS C Developers List" Subject: Re: AXIS2C: capabilities of code generation In-Reply-To: <45504279.1090506@isogmbh.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3010_25249520.1162892781339" References: <45504279.1090506@isogmbh.de> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_3010_25249520.1162892781339 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 11/7/06, Franz Fehringer wrote: > > Hello, > > I have some question regarding C code generation from WSDL/XSD. > First as i understand there are in fact two tools for this; one is Java > based and depends on XSLT stylesheets for the actual source code generation, > the other is written purely in C itself. > C tool also depends on XSLT stylesheets for the code generation. It has same architecture as Java tool. Is this a valid description of the curren state of affairs? > How do both tools compare regarding their support of WSDL/XSD > constructs/functionalities? > Java Tool has more features than C tool. C tool is still in experimental state. Are the following areas settlet with these tools: > > - Multiple port types in one WSDL? > > If there are multiple port types in WSDL Java tool ( org.apache.axis2.wsdl.WSDL2C) generate source code for only one port type. You can give port name as a argument to WSDL2C tool and in this case port type is selected from the port binding for given port. > - xsd:all? > > (WSDL2C Java tool)Not supported. > - xsd:union? > > (WSDL2C Java tool)Not supported. > - anonymous complexTypes (nested at arbitrary depth)? > > (WSDL2C Java tool)Support for anonymous complexTypes. > - restrictions of simple/builtin types? > - detection of presence/absence of optional xml attributes? > > (WSDL2C Java tool)Not supported. > - xml attributes, whose types are userdefined? > > (WSDL2C Java tool)Not supported. Greetings > > Franz > Best Regards, Milinda --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-c-dev-help@ws.apache.org > > > ------=_Part_3010_25249520.1162892781339 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 11/7/06, Franz Fehringer <feh@isogmbh.de> wrote:
Hello,

I have some question regarding C code generation from WSDL/XSD.
First as i understand there are in fact two tools for this; one is Java based and depends on XSLT stylesheets for the actual source code generation, the other is written purely in C itself.

C tool also depends on  XSLT stylesheets for the code generation. It has same architecture as Java tool.

Is this a valid description of the curren state of affairs?
How do both tools compare regarding their support of WSDL/XSD constructs/functionalities?

Java Tool has more features than C tool. C tool is still in experimental state.

Are the following areas settlet with these tools:
  • Multiple port types in one WSDL?

If there are multiple port types in WSDL Java tool (org.apache.axis2.wsdl.WSDL2C) generate source code for only one port type. You can give port name as a argument to WSDL2C tool and in this case port type is selected from the port binding for given port.

  • xsd:all?

(WSDL2C Java tool)Not supported.

  • xsd:union?

(WSDL2C Java tool)Not supported.

  • anonymous complexTypes (nested at arbitrary depth)?

(WSDL2C Java tool)Support for anonymous complexTypes.

  • restrictions of simple/builtin types?
  • detection of presence/absence of optional xml attributes?

(WSDL2C Java tool)Not supported. 

  • xml attributes, whose types are userdefined?

(WSDL2C Java tool)Not supported. 

Greetings

Franz


Best Regards,
Milinda

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org



------=_Part_3010_25249520.1162892781339--