ada2wsdl(1) [debian man page]

ADA2WSDL(1)							 AWS User's Guide						       ADA2WSDL(1)

NAME

       ada2wsdl - Generate a WDSL document from an Ada package specification

SYNOPSIS

       ada2wsdl [options] ada_spec

DESCRIPTION

       The  Ada Web Server is a library that allows you to embed a web server into your Ada application.  It provides not only HTTP but also SOAP,
       WSDL and several other facilities.  Thus you can write full-fledged web applications.

       WSDL (Web Service Definition Language) is a language based on XML.  WSDL documents describe, in a formal way, the  interface  to  Web  Ser-
       vices.  This description consists of the end-point (URL to the server offering the service), the SOAPAction (needed to call the remote pro-
       cedure), the procedure names and a description of the input and output parameters.

       Using ada2wsdl, you can create a WSDL document that describes Web Services provided by an Ada package.  ada2wsdl uses ASIS  to  parse  your
       Ada package specification, and generates a WSDL document by mapping Ada types to Web Services types, and Ada subprograms to operations.

       Please see the AWS User's guide for more details on how ada2wsdl works, and how you can use it to develop web services.

OPTIONS

       -a url Specify  the  URL  for  the  Web Server address. Web Services will be available at this address. A port can be specified on the URL,
	      http://server[:port]. The default value is http://.../.

       -f     Force creation of the WSDL file. Overwrite exiting file with the same name.

       -I path
	      Add path option for the ASIS compilation step. This option can appear any number of time on the command line.

       -noenum
	      Do not generate WSDL representation for Ada enumerations, map them to standard string.

       -o file
	      Generate the WSDL document into file.

       -q     Quiet mode (no output).

       -s name
	      Specify the Web Service name for the WSDL document, by default the spec package's name is used.

       -v     Verbose mode, display the parsed spec.

BUGS

       ada2wsdl does not handle constrained arrays in records.

       Unbounded_String are supported with full interoperability only inside a record.

       Only unconstrained arrays are supported.

       Arrays with multiple dimensions are not supported.

SEE ALSO

       awsres(1), wsdl2aws(1)

       The Ada Web Server User's Guide in package libaws-doc.

AUTHOR

       wsdl2aws was written by Dmitriy Anisimkov <anisimkov@yahoo.com> and Pascal Obry <p.obry@wanadoo.fr> as part of the Ada Web Server.

       This manual page was written by Ludovic Brenta <ludovic.brenta@insalien.org> for Debian GNU/Linux.

GNU Ada Tools							    11 JUN 2004 						       ADA2WSDL(1)

SOAP::WSDL::Manual::CodeFirst(3pm)			User Contributed Perl Documentation			SOAP::WSDL::Manual::CodeFirst(3pm)

NAME

       CodeFirst - Writing Code-First Web Services with SOAP::WSDL

       Note: This document is just a collection of thought. There's no implementation yet.

   How Data Class definitions could look like
       Moose

       Of course SOAP::WSDL could (and probably should) just use Moose - it provides the full Metaclass Framework needed for generating Schemas
       from class definitions.

       However, Moose is way too powerful for building (just) simple Data Transfer Objects which can be expressed in XML.

       With Moose, a class could look like this:

	package MyElements::GenerateBarCode;
	use Moose;

	has 'xmlns' =>
	    is => 'ro',
	    default => 'http://webservicex.net';

	has 'xmlname' =>
	    is => 'ro',
	    default => 'GenerateBarCode';

	has 'BarCodeParam' =>
	     is => 'rw',
	     type => 'MyTypes::BarCodeData';

	has 'BarCodeText' =>
	     is => 'rw',
	     type => 'String';
	1;

       This is - despite the condensed syntax - a lot of line noise.

       Native SOAP::WSDL

       SOAP::WSDL::XSD::Typelib::ComplexType (should) provide a simple setup method allowing a even shorter description (and offering the
       additional performance boost SOAP::WSDL has over Moose):

	package MyElements::GenerateBarCode;
	use strice; use warnings;
	use SOAP::WSDL::XSD::Typelib::Element;
	use SOAP::WSDL::XSD::Typelib::ComplexType;

	_namespace 'http://webservicex.net';	# might be better in the SOAP server interface
	_name 'GenerateBarCode';
	_elements
		BarCodeParam => 'MyTypes::BarCodeData',
		BarCodeText => 'string';

       This would result in the following XML Schema (inside a schema with the namespace "http://webservicex.net" - the namespaces could even be
       declared outside the DTO classes.

	<complexType name="GenerateBarCode">
	     <sequence>
		  <element name="BarCodeParam" type="tns:BarCodeData"/>
		  <element name="BarCodeText" type="xsd:string"/>
	     </sequence>
	</complexType>

   Interface definitions
       Perl does not have the concept of interfaces. However, Moose provides Roles, which can be used for defining interfaces.

       However, it's not really necessary to define a interface Interface (in the sense of a Java interface) - a interface class is sufficient.

       Subroutine attributes could be used for providing additional information - attributes in perl are much like annotations in Java

       A interface could look like this:

	package MyServer::BarCode;
	use strict; use warnings;
	use SOAP::WSDL::Server::CodeFirst;

	sub generateBarCode :WebMethod(name=<GenerateBarCode>
	    return=<MyElements::GenerateBarcodeResponse>
	    body=<MyElements::GenerateBarcode>) {
	    my ($self, $body, $header) = @_;
	    my $result = MyElements::GenerateBarcodeResponse->new();
	    return $result;
	};
	1;

perl v5.10.1							    2010-12-21					SOAP::WSDL::Manual::CodeFirst(3pm)