Free wsdl software for linux

Pod::WSDL is a Perl module that creates WSDL documents from (extended) pod.

SYNOPSIS

use Pod::WSDL;

my $pod = new Pod::WSDL(source => My::Server,
location => http://localhost/My/Server,
pretty => 1,
withDocumentation => 1);

print $pod->WSDL;

Parsing the pod

How does Pod::WSDL work? If you instantiate a Pod::WSDL object with the name of the module (or the path of the file, or an open filehandle) providing the web service like this

my $pwsdl = new Pod::WSDL(source => My::Module,
location => http://my.services.location/on/the/web);

Pod::WSDL will try to find My::Module in @INC, open the file, parse it for WSDL directives and prepare the information for WSDL output. By calling

$pwsdl->WSDL;

Pod::WSDL will output the WSDL document. Thats it.
When using Pod::WSDL, the parser expects you to do the following:

Put the pod directly above the subroutines which the web services client is going to call. There may be whitespace between the pod and the sub declaration but nothing else.
Use the =begin/=end respectively the =for directives according to standard pod: anything between =begin WSDL and =end will be treated as pod. Anything composing a paragraph together with =for WSDL will be treated as pod.

Any subroutine not preceeded by WSDL pod will be left unmentioned. Any standard pod will be ignored (though, for an exception to this, see the section on own complex types below).

The individual instructions for Pod::WSDL always begin with a keyword, like _RETURN or _DOC or _FAULT. After this different things may follow, according to the specific type of instruction. The instruction may take one or more lines - everything up to the next line beginning with a keyword or the end of the pod is belonging to the current instruction.

Describing Methods

How do we use Pod::WSDL? In describing a web services method we have to say something about parameters, return values and faults. In addition you might want to add some documentation to these items and to the method itself.

wsdlpull is a C++ WSDL Library. wsdlpull project includes a WSDL Parser , a XSD Schema
Parser and Validator and XML Parser and serializer and an API for dynamic WSDL inspection and invocation.
wsdlpull uses the xml pull api to parse a WSDL1.1 document. This makes wsdlpull highly efficient which is why you can process and invoke a WSDL in no time.
The parser provides APIs to access various WSDL elements such as operations,messages,bindings,port types. Although wsdlpull is based on the pull parsing style of xml parsing the API is meant to be semantically as close as possible to the standard API for parsing WSDL, namely WSDL4J.
The invocation API allows you to dynamically inspect and invoke a web service. Unlike other toolkits there is no need to generate stubs or type serializers. Writing a web service client involves providing the WSDL URL ,setting the operation ,the input types and getting back the results in just one step.
The schema parser and validator provides an API for parsing XSD schema documents and validating their xml instance documents. The schema parser is used to parse the types section of the WSDL document.
The Xml parser and serializer provide a C++ implementation of the XML Pull API . WSDL processing, XSD schema processing ,creating SOAP messages all use the parser and serializer.
Enhancements:
- Several new features were added, including the ability to validate multiple occurences of choice elements, a new -p option to print port types of a wsdl, a -g option in the wsdl tool to generate soap message, and an experimental -g option in the schema tool to generate instances.
- Fixes were also made for a schema:import bug and for a type reference in an imported schema which is defined in same wsdl file but under another namespace.

Pod::WSDL::Doc is a Perl module that represents the WSDL pod for the documentation of methods (internal use only).

SYNOPSIS

use Pod::WSDL::Doc;
my $doc = new Pod::WSDL::Doc(_DOC This method is for blah ...);

This module is used internally by Pod::WSDL. It is unlikely that you have to interact directly with it. If that is the case, take a look at the code, it is rather simple.

METHODS

new

Instantiates a new Pod::WSDL::Attr. The method needs one parameter, the documentation string from the pod. Please see SYNOPSIS or the section "Pod Syntax" in the description of Pod::WSDL.

C++ WSDL Parser is an efficient C++ Web services library that includes a standards compliant WSDL parser API, a Schema parser and validator, an XML parser and serializer, and an API for dynamically inspecting and invoking WSDL Web services.
Enhancements:
- Many WSDLs can now be dynamically invoked.
- Added documentation (doxygen for the API).
- Better error reporting when types are found missing.

idl2rng is a IDL compiler to RELAX NG Schema.

SYNOPSIS

idl2rng [options] spec.idl

OPTIONS

All options are forwarded to C preprocessor, except -b -h -i -q -r -s -t -v -x.

With the GNU C Compatible Compiler Processor, useful options are :

-D name
-D name=definition
-I directory
-I-
-nostdinc

Specific options :

-b base uri

Specify a base uri for location of include.

-h

Display help.

-i directory

Specify a path for import (only for IDL version 3.0).

-q

Generate qualified elements.

-r root-element

Specify a root element.

-s

Generate a standalone Schema (not only type definition).

-t

Generate tabulated XML (beautify for human).

-v

Display version.

-x

Enable export (only for IDL version 3.0).

idl2rng parses the given input file (IDL) and generates :

a RELAX NG Schema spec.rng equivalent to W3C Schema following the CORBA to WSDL/SOAP Interworking Specification (WS-I comformant soap binding).

idl2rng is a Perl OO application what uses the visitor design pattern. The parser is generated by Parse::Yapp.

idl2rng needs XML::DOM module.

idl2rng needs a cpp executable.

SOAP::Lite is a client and server side SOAP implementation.
SOAP::Lite is a collection of Perl modules which provides a simple and lightweight interface to the Simple Object Access Protocol (SOAP) both on client and server side.
Main features:
- Supports SOAP 1.1 spec.
- Interoperability tests with different implementations: Apache SOAP, Apache Axis, Frontier, Microsoft SOAP, Microsoft .NET, DevelopMentor, XMethods, 4s4c, Phalanx, PocketSOAP, Kafka, SQLData, Lucin (in Java, Perl, C++, Python, VB, COM, XSLT).
- Provides COM interface. Single dll (standalone [2.5MB] or minimal [32kB]). Works on Windows 9x/Me/NT/2K. Doesnt require ROPE or MSXML. Examples in VB, Excel/VBA, C#, ASP, JavaScript, PerlScript and Perl.
- Provides transparent compression support for HTTP transport.
- Provides mod_soap module. Make SOAP server with a few lines in .htaccess or .conf file.
- Includes XML::Parser::Lite (regexp-based XML parser) which runs instead of XML::Parser where Perl 5.6 runs (even on WinCE) with some limitations.
- Includes XMLRPC::Lite, implementation of XML-RPC protocol on client and server side. All transports and features of SOAP::Lite are available.
- Supports multipart/form-data MIME attachments.
- Supports circular linked lists and multiple references.
- Supports Map datatype (encoding of maps/hashes with arbitrary keys).
- Supports HTTPS protocol.
- Provides proxy support.
- Provides CGI/daemon/mod_perl/Apache::Registry server implementations.
- Provides TCP server implementation.
- Provides IO (STDIN/STDOUT/File) server implementation.
- Provides FTP client implementation.
- Supports single/multipart MIME attachment (parsing side only).
- Supports SMTP protocol.
- Provides POP3 server implementation.
- Supports M-POST and redirects in HTTP transport.
- Supports Basic/Digest server authentication.
- Works with CGI accelerators, like VelociGen and PerlEx.
- Supports UDDI interface on client side. See UDDI::Lite for details.
- Supports UDDI publishing API. Examples and documentation provided.
- Supports WSDL schema with stub and run-time access.
- Supports blessed object references.
- Supports arrays (both serialization and deserialization with autotyping).
- Supports custom serialization.
- Provides exception transport with custom exceptions
- Supports Base64 encoding.
- Supports XML entity encoding.
- Supports header attributes.
- Supports dynamic and static class/method binding.
- Supports objects-by-reference with simple garbage collection and activation.
- Provides shell for interactive SOAP sessions.
- Supports out parameters binding.
- Supports transparent SOAP calls with autodispatch feature.
- Provides easy services deployment. Put module in specified directory and itll be accessible.
- Has tests, examples and documentation to let you be up and running in no time.

WebService::GoogleHack is a Perl package that ties together all GoogleHack modules (Webservice::GoogleHack::Search, Webservice::GoogleHack::Spelling, Webservice::GoogleHack::Rate, and Webservice::GoogleHack::Text) to implement Natural Language Processing techniques that use the World Wide Web as a source of information. Use this package to access all the functionality of GoogleHack.
SYNOPSIS
use WebService::GoogleHack;
my $google = new WebService::GoogleHack;
#Initializing the object to the contents of the configuration file
# API Key, GoogleSearch.wsdl file location.
$google->initConfig("initconfig.txt");
#Printing the contents of the configuration file
$google->printConfig();
#Measure the semantic relatedness between the words "white house" and
#"president".
$measure=$google->measureSemanticRelatedness1("white house","president");
print "nRelatedness measure between white house and president is: ";
print $measure."n";
#Going to search for words that are related to "toyota" and "ford"
my @terms=();
push(@terms,"toyota");
push(@terms,"ford");
#The parameters are the search terms, number of web page results to look
#at, the number of iterations,output file and the "true" indicates that the
#diagnostic data should be stored in the file "results.txt"
$results=$google->Algorithm1(@terms,10,25,1,"results.txt","true");
print $results;
WebService::GoogleHack is a PERL package that interacts with the Google API, and implements basic functions that allow the user to interact with Google and retrieve results in an easy to use format. GoogleHack also implements and extends a number of Natural Language Processing by using the World Wide Web as a source of information.
Main features:
- Issue queries to Google (WebService::GoogleHack, WebService::GoogleHack::Search)
- Retrieve Spelling suggestions from Google (WebService::GoogleHack, WebService::GoogleHack::Spelling)
- Find the Pointwise Mututal Information (PMI) measure between two words (WebService::GoogleHack,WebService::GoogleHack::Rate)
- Given a paragraph find if the paragraph has a positive or negative semantic orientation.(WebService::GoogleHack,WebService::GoogleHack::Rate)
- Given a set of words along with a positively oriented word such as "excellent" and a negatively oriented word such as "poor", find if the word has a positive or negative semantic orientation.(WebService::GoogleHack,WebService::GoogleHack::Rate)
- Given a set of phrases along with a positively oriented word such as "excellent" and a negatively oriented word such as "poor", predict if the given phrases are positive or negative in sentiment.(WebService::GoogleHack,WebService::GoogleHack::Rate)
- Given two or more words finds a set of related words. (WebService::GoogleHack)

SAGA.M31 - Galaxy - project lets you create a Web Service to your enterprise data within 15 minutes. All you need is a Servlet Container, a Database and a Browser.

The information can be accessed either via a SOAP Document/Literal Style Web Service or a simple XML-Request/Response structure.

A free download and license is available as also a free Eclipse Plugin that lets you implement the data into your business application.

The data is secured by userid / role permissions. The WSDL for the Web Service can be public or private so you decide who accesses your data.

Data consistency over platforms is provided by an independency layer that makes it easy to migrate the underlying data to another source.

SAGA.M31 - Galaxy - is a service to provide Data access. This section explains the features that are already available in SAGA.M31 - Galaxy -. No future selling, but real information. The Functionality of SAGA.M31 - Galaxy - is strong oriented to provide access to the most important Information sources without any programming knowledge.

This separates the business logic from the data access logic and helps to improve performance by having database experts building the data structure and definition and application programmer focussing on the business logic.

Because we permanently enhance the feature sets, we ask you to visit this site regular. As an alternate option you can use our RSS Feed to be informed automatically. Subscribing to our newsletter is very welcome, so you will get first hand information.