[wsf-c-dev] svn commit r716 - wsf/php/src/xdocs
svn at wso2.com
svn at wso2.com
Mon Feb 5 01:19:43 PST 2007
Author: marietta
Date: Mon Feb 5 01:19:31 2007
New Revision: 716
Modified:
wsf/php/src/xdocs/index.html
wsf/php/src/xdocs/install_guide.html
wsf/php/src/xdocs/manual_content.html
wsf/php/src/xdocs/manual_toc.html
wsf/php/src/xdocs/wsdl_generation_api.html
Log:
Made minor changes.
Modified: wsf/php/src/xdocs/index.html
==============================================================================
--- wsf/php/src/xdocs/index.html (original)
+++ wsf/php/src/xdocs/index.html Mon Feb 5 01:19:31 2007
@@ -5,16 +5,18 @@
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<title>WSO2 WSF for PHP</title>
+ <link href="style/api_style.css" rel="stylesheet" type="text/css"
+ media="all" />
</head>
<body xml:lang="en">
-<h1>WSO2 Web Services Framework for PHP</h1>
+<h1>WSO2 Web Services Framework/PHP</h1>
-<p>WSO2 Web Services Framework for PHP is a next generation SOAP stack, based
-on <a href="http://ws.apache.org/axis2/c/index.html">Apache Axis2 C</a>, for
-providing and consuming Web Services in PHP.</p>
+<p>WSO2 Web Services Framework/PHP (WSO2 WSF/PHP) is a next generation SOAP
+stack, based on <a href="http://ws.apache.org/axis2/c/index.html">Apache
+Axis2 C</a>, for providing and consuming Web Services in PHP.</p>
-<p>WSO2 WSF for PHP supports both <a
+<p>WSO2 WSF/PHP supports both <a
href="http://www.w3.org/TR/soap12-part1/">SOAP 1.2</a> and <a
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">SOAP 1.1</a> as well as
some of the WS-* stack specifications: <a
@@ -39,9 +41,9 @@
<h2>Latest Release</h2>
-<h3>25th October 2006, WSO2 WSF for PHP 1.0alpha1 Released</h3>
+<h3>25th October 2006, WSO2 WSF/PHP 1.0alpha1 Released</h3>
<b><a href="http://dist.wso2.net/products/wsf/php/1.0alpha1">Download WSO2
-WSF for PHP 1.0alpha1</a></b>
+WSF/PHP 1.0alpha1</a></b>
<h4>Key Features</h4>
<ol>
Modified: wsf/php/src/xdocs/install_guide.html
==============================================================================
--- wsf/php/src/xdocs/install_guide.html (original)
+++ wsf/php/src/xdocs/install_guide.html Mon Feb 5 01:19:31 2007
@@ -1,241 +1,240 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html>
-<head>
- <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
- <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
- <title>WSO2 WSF Installation Guide</title>
-</head>
-
-<body>
-<h1>WSO2 WSF for PHP Installation Guide</h1>
-
-<p>This document will guide you on how to install WSO2 Web Services Framework
-for PHP extension and run the server and client samples on Linux and
-Microsoft Windows operating systems.</p>
-
-<p>Please send your feedback to the user mailing list: <a
-href="mailto:wsf-php-user at lists.wso2.net">wsf-php-user at lists.wso2.net</a>.
-Kindly see <a
-href="https://www-lk.wso2.com/repo/wso2/php_axis2/extension/xdocs/index.html#mail">Home
-page</a> for subscription.</p>
-
-<h2>Contents</h2>
-<ul>
- <li><a href="#Common Installation Instructions">Common Installation
- Instructions</a></li>
- <li><a href="#1.Installing and Running on Linuxs">Installing and Running on
- Linux</a></li>
- <li><a
- href="#2.Installing and Running on Microsoft Windows (win32)">Installing
- and Running on Microsoft Windows (win32)</a>
- <ul>
- <li><a href="#Build PHP on Windows">Build PHP on MS Windows</a></li>
- <li><a href="#Build WSO2 WSF for C on Windows from Source">Build WSO2
- WSF for C on MS Windows from Source</a>
- <ul>
- <li><a href="#Requirements">Requirements</a></li>
- <li><a href="#Using the Command Prompt">Using the Command
- Prompt</a></li>
- </ul>
- </li>
- <li><a
- href="#Building WSO2 WSF for PHP on Windows from Source">Building
- WSO2 WSF for PHP on MS Windows from Source</a></li>
- <li><a href="#Installing WSO2 WSF As a PHP Extension">Installing WSO2
- WSF As a PHP Extension</a></li>
- </ul>
- </li>
-</ul>
-
-<a id="Common Installation Instructions"></a>
-<h2>Common Installation Instructions</h2>
-
-<p>To get the distributions working, you need the following installed in your
-system.</p>
-<ul>
- <li>PHP 5.1.1 or later, which can be downloaded from <a
- href="http://www.php.net/">PHP </a> official Web site. Please refer to
- the additional note on installing PHP as a DSO module to Apache2 Web
- server.
- <p>If you are using a pre-installed version of PHP, please make sure that
- you have the developer version installed, so that you can compile
- WSO2 WSF for PHP source.</p></li>
- <li>libxml2, which can be downloaded from <a
- href="http://xmlsoft.org/downloads.html">here</a> (NOTE: Most Linux
- systems have libxml2 by default.)</li>
-</ul>
-
-<a id="1.Installing and Running on Linuxs"></a>
-<h2>1. Installing and Running on Linux</h2>
-
-
-<p>1. Go to the directory where you have extracted the source distribution.
-Run the following:</p>
-<ul>
- <li>./configure</li>
- <li>make</li>
- <li>make install</li>
-</ul>
-
-<p>Note: You may require super user privileges to run 'make install' on your
-system.</p>
-
-<p>2. After installing the extension, you have to edit the php.ini file and
-add the following line to the php.ini file:<br />
-<b><i>extension=wsf.so</i></b></p>
-
-<p>Now you are ready to use WSO2 WSF for PHP.</p>
-
-<p>3. Copy the wsf.php script to your Web server's document root.</p>
-
-<p>4. Also copy all the samples to your Web server's document root.</p>
-
-<p>5. Test with a Web browser; as an example access <h
-href=http://localhost/echo_client.php>http://localhost/echo_client.php</h></p>
-
-<p><i>NOTES:</i></p>
-<ul>
- <li><i>You may run './configure --help' for more information on configure
- options.</i></li>
- <li><i>If you don't provide the --prefix configure option, WSO2 WSF for PHP
- will by default be installed into the PHP extensions directory.</i></li>
- <li><i>If you provide the --prefix configure option you will have to edit
- the php.ini file in your system and add the following entry.</i></li>
- <li><i>Note that WSO2 WSF for C would be installed to a folder named
- "wsf_c" in the prefix folder.<br />
- <b>[wsf] wsf.home="path to your wsf_c installation directory"</b><br />
- </i></li>
-</ul>
-
-<a id="2.Installing and Running on Microsoft Windows (win32)"></a>
-<h2>2. Installing and Running on Microsoft Windows (win32)</h2>
-
-<a id="Build PHP on Windows"></a>
-<h3>Build PHP on MS Windows</h3>
-
-<p>Please refer to README.WIN32-BUILD-SYSTEM file that comes with PHP source
-distribution.</p>
-
-<a id="Build WSO2 WSF for C on Windows from Source"></a>
-<h3>Build WSO2 WSF for C on
-MS Windows from Source</h3>
-
-<a id="Requirements"></a>
-<h4>Requirements</h4>
-
-<p>You need to download following:</p>
-<ul>
- <li>libxml2 binary distribution</li>
- <li>zlib binary distribution</li>
- <li>iconv binary distribution</li>
-</ul>
-
-<a id="Using the Command Prompt"></a>
-<h4>Using the Command Prompt</h4>
-
-<p>1. If you have Visual Studio command prompt, open it and change directory
-to "wsf_c/axis2c/build/win32" of the extract folder.<br />
-</p>
-
-<p>2. If not, create a new shortcut and set target to:<br />
-<b> %comspec% /k "C:\Program Files\Microsoft Visual Studio .NET
-2003\Vc7\bin\vcvars32.bat"</b><br />
-</p>
-
-<p>3. Now change directory to "wsf_c/axis2c/build/win32" and edit the
-configure.in file and set your binary installation locations of libxml2, zlib
-and iconv libraries.<br />
-</p>
-
-<p>4. "nmake dist" will build the binary under "wsf_c/axis2c/build"
-directory.</p>
-
-<a id="Building WSO2 WSF for PHP on Windows from Source"></a>
-<h3>Building WSO2 WSF for PHP on MS Windows from Source</h3>
-
-<p>1. Before trying this, please refer README.WIN32-BUILD-SYSTEM file in PHP
-source distribution and build PHP source under MS Windows.</p>
-
-<p>2. Create a bat file named wsfvars.bat with following entries using your
-directory locations.<br />
-</p>
-<pre> @SET PATH=%PATH%;<path_to_extract_folder>\axis2c\build\wsf_c\lib;
- @SET INCLUDE=%INCLUDE%;<path_to_extract_folder>\wsf_c\axis2c\build\wsf_c\include;
- @SET LIB=%LIB%;<path_to_extract_folder>\wsf_c\axis2c\build\wsf_c\lib;</path_to_extract_folder></path_to_extract_folder></path_to_extract_folder></pre>
-
-<p>3. Then using the same command prompt used to build the PHP source, run
-the wsfvars.bat file.<br />
-</p>
-
-<p>4. Copy wsf_php folder to php_source/ext directory.<br />
-</p>
-
-<p>5. Run "buildconf.bat" to rebuild the configre.js file.<br />
-</p>
-
-<p>6. "cscript /nologo configure.js --help" will give the configuration
-options. You will find the option --with-wsf.<br />
-</p>
-
-<p>7. Use "cscript configure.js --with-wsf=shared" to configure the wsf
-extension as a dll<br />
-</p>
-
-<p>8. "nmake" will build wsf extension.<br />
-</p>
-
-<a id="Installing WSO2 WSF As a PHP Extension"></a>
-<h3>Installing WSO2 WSF As a PHP
-Extension</h3>
-
-<p>1. If you have built from the source you should now have the wsf_c binary
-and the php_wsf.dll.<br />
-</p>
-
-<p>2. If you have extracted the binary you should have the following
-structure.</p>
-<pre> wso2_wsf_1.0.alpha1-bin
- |
- +-- wsf_c
- |
- +-- php_wsf.dll</pre>
-
-<p>3. Copy php_wsf.dll to PHP installation directory.</p>
-
-<p>4. Add wsf_c\lib directory to path.</p>
-
-<p>5. Add the following entries to your php.ini file which is in your PHP
-installation location.<br />
-</p>
-<pre> [wsf]
- wsf.home="<path_to_extract_folder>\wsf_c"
- wsf.log_path="<path_to_extract_folder>\wsf_c\logs"
-
- extension=php_wsf.dll</path_to_extract_folder></path_to_extract_folder></pre>
-
-<p>6. Create an environment variable PHPRC to point to your php.ini file
-location.</p>
-
-<p>7. Configure the Apache2 Web server with PHP as follows.<br />
-</p>
-
-<p>8. Copy php5apache2.dll to Apache2/modules directory. Add following
-entries in httpd.conf file.<br />
-</p>
-
-<p>9. LoadModule php5_module modules/php5apache2.dll <br />
-</p>
-
-<p>10. AddType application/x-httpd-php .php .phtml<br />
-</p>
-
-<p>11. AddType application/x-httpd-php-source .phps<br />
-</p>
-
-<p>12. Copy the wsf.php script and all the samples to your Web server's
-document root</p>
-
-<p>Now you should be able to run the samples in samples directory.</p>
-</body>
-</html>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html>
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
+ <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
+ <title>WSO2 WSF Installation Guide</title>
+<link href="style/api_style.css" rel="stylesheet" type="text/css" media="all" />
+</head>
+
+<body>
+<h1>WSO2 WSF/PHP Installation Guide</h1>
+
+<p>This document will guide you on how to install WSO2 Web Services
+Framework/PHP extension and run the server and client samples on Linux and
+Microsoft Windows operating systems.</p>
+
+<p>Please send your feedback to the user mailing list: <a
+href="mailto:wsf-php-user at lists.wso2.net">wsf-php-user at lists.wso2.net</a>.
+Kindly see <a
+href="https://www-lk.wso2.com/repo/wso2/php_axis2/extension/xdocs/index.html#mail">Home
+page</a> for subscription.</p>
+
+<h2>Contents</h2>
+<ul>
+ <li><a href="#Common Installation Instructions">Common Installation
+ Instructions</a></li>
+ <li><a href="#1.Installing and Running on Linuxs">Installing and Running on
+ Linux</a></li>
+ <li><a
+ href="#2.Installing and Running on Microsoft Windows (win32)">Installing
+ and Running on Microsoft Windows (win32)</a>
+ <ul>
+ <li><a href="#Build PHP on Windows">Build PHP on MS Windows</a></li>
+ <li><a href="#Build WSO2 WSF for C on Windows from Source">Build WSO2
+ WSF/C on MS Windows from Source</a>
+ <ul>
+ <li><a href="#Requirements">Requirements</a></li>
+ <li><a href="#Using the Command Prompt">Using the Command
+ Prompt</a></li>
+ </ul>
+ </li>
+ <li><a
+ href="#Building WSO2 WSF for PHP on Windows from Source">Building
+ WSO2 WSF/PHP on MS Windows from Source</a></li>
+ <li><a href="#Installing WSO2 WSF As a PHP Extension">Installing WSO2
+ WSF As a PHP Extension</a></li>
+ </ul>
+ </li>
+</ul>
+<a id="Common Installation Instructions"></a>
+
+<h2>Common Installation Instructions</h2>
+
+<p>To get the distributions working, you need the following installed in your
+system.</p>
+<ul>
+ <li>PHP 5.1.1 or later, which can be downloaded from <a
+ href="http://www.php.net/">PHP </a> official Web site. Please refer to
+ the additional note on installing PHP as a DSO module to Apache2 Web
+ server.
+ <p>If you are using a pre-installed version of PHP, please make sure that
+ you have the developer version installed, so that you can compile WSO2
+ WSF/PHP source.</p>
+ </li>
+ <li>libxml2, which can be downloaded from <a
+ href="http://xmlsoft.org/downloads.html">here</a> (NOTE: Most Linux
+ systems have libxml2 by default.)</li>
+</ul>
+<a id="1.Installing and Running on Linuxs"></a>
+
+<h2>1. Installing and Running on Linux</h2>
+
+<p>1. Go to the directory where you have extracted the source distribution.
+Run the following:</p>
+<ul>
+ <li>./configure</li>
+ <li>make</li>
+ <li>make install</li>
+</ul>
+
+<p>Note: You may require super user privileges to run 'make install' on your
+system.</p>
+
+<p>2. After installing the extension, you have to edit the php.ini file and
+add the following line to the php.ini file:<br />
+<b><i>extension=wsf.so</i></b></p>
+
+<p>Now you are ready to use WSO2 WSF/PHP.</p>
+
+<p>3. Copy the wsf.php script to your Web server's document root.</p>
+
+<p>4. Also copy all the samples to your Web server's document root.</p>
+
+<p>5. Test with a Web browser; as an example access <h
+href=http://localhost/echo_client.php>http://localhost/echo_client.php</h></p>
+
+<p><i>NOTES:</i></p>
+<ul>
+ <li><i>You may run './configure --help' for more information on configure
+ options.</i></li>
+ <li><i>If you don't provide the --prefix configure option, WSO2 WSF/PHP
+ will by default be installed into the PHP extensions directory.</i></li>
+ <li><i>If you provide the --prefix configure option you will have to edit
+ the php.ini file in your system and add the following entry.</i></li>
+ <li><i>Note that WSO2 WSF/C would be installed to a folder named "wsf_c" in
+ the prefix folder.<br />
+ <b>[wsf] wsf.home="path to your wsf_c installation directory"</b><br />
+ </i></li>
+</ul>
+<a id="2.Installing and Running on Microsoft Windows (win32)"></a>
+
+<h2>2. Installing and Running on Microsoft Windows (win32)</h2>
+<a id="Build PHP on Windows"></a>
+
+<h3>Build PHP on MS Windows</h3>
+
+<p>Please refer to README.WIN32-BUILD-SYSTEM file that comes with PHP source
+distribution.</p>
+<a id="Build WSO2 WSF for C on Windows from Source"></a>
+
+<h3>Build WSO2 WSF/C on MS Windows from Source</h3>
+<a id="Requirements"></a>
+
+<h4>Requirements</h4>
+
+<p>You need to download following:</p>
+<ul>
+ <li>libxml2 binary distribution</li>
+ <li>zlib binary distribution</li>
+ <li>iconv binary distribution</li>
+</ul>
+<a id="Using the Command Prompt"></a>
+
+<h4>Using the Command Prompt</h4>
+
+<p>1. If you have Visual Studio command prompt, open it and change directory
+to "wsf_c/axis2c/build/win32" of the extract folder.<br />
+</p>
+
+<p>2. If not, create a new shortcut and set target to:<br />
+<b> %comspec% /k "C:\Program Files\Microsoft Visual Studio .NET
+2003\Vc7\bin\vcvars32.bat"</b><br />
+</p>
+
+<p>3. Now change directory to "wsf_c/axis2c/build/win32" and edit the
+configure.in file and set your binary installation locations of libxml2, zlib
+and iconv libraries.<br />
+</p>
+
+<p>4. "nmake dist" will build the binary under "wsf_c/axis2c/build"
+directory.</p>
+<a id="Building WSO2 WSF for PHP on Windows from Source"></a>
+
+<h3>Building WSO2 WSF/PHP on MS Windows from Source</h3>
+
+<p>1. Before trying this, please refer README.WIN32-BUILD-SYSTEM file in PHP
+source distribution and build PHP source under MS Windows.</p>
+
+<p>2. Create a bat file named wsfvars.bat with following entries using your
+directory locations.<br />
+</p>
+<pre> @SET PATH=%PATH%;<path_to_extract_folder>\axis2c\build\wsf_c\lib;
+ @SET INCLUDE=%INCLUDE%;<path_to_extract_folder>\wsf_c\axis2c\build\wsf_c\include;
+ @SET LIB=%LIB%;<path_to_extract_folder>\wsf_c\axis2c\build\wsf_c\lib;</path_to_extract_folder></path_to_extract_folder></path_to_extract_folder></pre>
+
+<p>3. Then using the same command prompt used to build the PHP source, run
+the wsfvars.bat file.<br />
+</p>
+
+<p>4. Copy wsf_php folder to php_source/ext directory.<br />
+</p>
+
+<p>5. Run "buildconf.bat" to rebuild the configre.js file.<br />
+</p>
+
+<p>6. "cscript /nologo configure.js --help" will give the configuration
+options. You will find the option --with-wsf.<br />
+</p>
+
+<p>7. Use "cscript configure.js --with-wsf=shared" to configure the wsf
+extension as a dll<br />
+</p>
+
+<p>8. "nmake" will build wsf extension.<br />
+</p>
+<a id="Installing WSO2 WSF As a PHP Extension"></a>
+
+<h3>Installing WSO2 WSF As a PHP Extension</h3>
+
+<p>1. If you have built from the source you should now have the wsf_c binary
+and the php_wsf.dll.<br />
+</p>
+
+<p>2. If you have extracted the binary you should have the following
+structure.</p>
+<pre> wso2_wsf_1.0.alpha1-bin
+ |
+ +-- wsf_c
+ |
+ +-- php_wsf.dll</pre>
+
+<p>3. Copy php_wsf.dll to PHP installation directory.</p>
+
+<p>4. Add wsf_c\lib directory to path.</p>
+
+<p>5. Add the following entries to your php.ini file which is in your PHP
+installation location.<br />
+</p>
+<pre> [wsf]
+ wsf.home="<path_to_extract_folder>\wsf_c"
+ wsf.log_path="<path_to_extract_folder>\wsf_c\logs"
+
+ extension=php_wsf.dll</path_to_extract_folder></path_to_extract_folder></pre>
+
+<p>6. Create an environment variable PHPRC to point to your php.ini file
+location.</p>
+
+<p>7. Configure the Apache2 Web server with PHP as follows.<br />
+</p>
+
+<p>8. Copy php5apache2.dll to Apache2/modules directory. Add following
+entries in httpd.conf file.<br />
+</p>
+
+<p>9. LoadModule php5_module modules/php5apache2.dll <br />
+</p>
+
+<p>10. AddType application/x-httpd-php .php .phtml<br />
+</p>
+
+<p>11. AddType application/x-httpd-php-source .phps<br />
+</p>
+
+<p>12. Copy the wsf.php script and all the samples to your Web server's
+document root</p>
+
+<p>Now you should be able to run the samples in samples directory.</p>
+</body>
+</html>
Modified: wsf/php/src/xdocs/manual_content.html
==============================================================================
--- wsf/php/src/xdocs/manual_content.html (original)
+++ wsf/php/src/xdocs/manual_content.html Mon Feb 5 01:19:31 2007
@@ -5,21 +5,22 @@
<title></title>
<meta name="CREATED" content="20061009;17484000">
<meta name="CHANGED" content="20061011;10243100">
-<link href="style/api_style.css" rel="stylesheet" type="text/css" media="all" />
+ <link href="style/api_style.css" rel="stylesheet" type="text/css"
+ media="all">
</head>
<body lang="en-US" dir="ltr">
-<h1>WSO2 WSF for PHP Manual</h1>
+<h1>WSO2 WSF/PHP Manual</h1>
<h2><a name="Introduction">1. Introduction</a></h2>
-<p>WSO2 Web Services Framework for PHP is a PHP extension that could be used
-to provide and consume Web services. It supports SOAP 1.1, SOAP 1.2, MTOM,
+<p>WSO2 Web Services Framework/PHP is a PHP extension that could be used to
+provide and consume Web services. It supports SOAP 1.1, SOAP 1.2, MTOM,
WS-Addressing, WS-Security UsernameToken as well as REST style invocation.</p>
<h2><a name="Requirements">2. Requirements</a></h2>
-<p>WSO2 Web Services Framework (WSF) for PHP makes use of <a
+<p>WSO2 Web Services Framework/PHP (WSO2 WSF/PHP) makes use of <a
href="http://www.xmlsoft.org/">GNOME XML library</a>.</p>
<h2><a name="Installation">3. Installation</a></h2>
@@ -41,7 +42,7 @@
are required.</p>
<table border="1">
- <caption>WSO2 WSF for PHP Configuration Options</caption>
+ <caption>WSO2 WSF/PHP Configuration Options</caption>
<tbody>
<tr>
<th>Name</th>
@@ -54,15 +55,15 @@
<td>wsf.home</td>
<td>string</td>
<td>"/path_to_php_ext/wsf_c"</td>
- <td>Path to where you have WSO2 WSF for C installed.</td>
+ <td>Path to where you have WSO2 WSF/C installed.</td>
<td>PHP_INI_ALL</td>
</tr>
<tr>
<td>wsf.log_path</td>
<td>string</td>
<td>"/tmp"</td>
- <td>Path to the folder into which the WSO2 WSF for PHP log
- file is to be written. <br>
+ <td>Path to the folder into which the WSO2 WSF/PHP log file is to be
+ written. <br>
A log file named wsf.log will be written to this given location.</td>
<td>PHP_INI_ALL</td>
</tr>
@@ -75,10 +76,9 @@
<h2><a name="Quick">5. Quick Start Guide</a></h2>
<p>This section is aimed to help you to get a Web service up in quick time
-using WSO2 WSF for PHP and consume that service using a WSO2 WSF for PHP
-client.</p>
+using WSO2 WSF/PHP and consume that service using a WSO2 WSF/PHP client.</p>
-<p>First follow the install guide and get WSO2 WSF for PHP working on your
+<p>First follow the install guide and get WSO2 WSF/PHP working on your
machine. Once you have installed the extension, you should be able to run the
php scripts written using classes supported by WSO2 WSF, by dropping them
into Apache2's htdocs folder, or where ever you have your web server root.<br>
@@ -122,12 +122,11 @@
</p>
<p>The following sections detail how to write a simple service and a client
-with WSO2 WSF for PHP.</p>
+with WSO2 WSF/PHP.</p>
<h2 class="western"><a name="5.1.">5.1. Hello Service</a></h2>
-<p>Lets see how you could write your first Web service with WSO2 WSF for PHP
-.</p>
+<p>Lets see how you could write your first Web service with WSO2 WSF/PHP .</p>
<p>The first service that we are going to write is named "hello" and would
have a single operation named "greet". This "greet" operation, when invoked
@@ -147,7 +146,7 @@
<br>
-<p>The steps to be followed when implementing a service with WSO2 WSF for PHP
+<p>The steps to be followed when implementing a service with WSO2 WSF/PHP
include:</p>
<ol>
<li><b>Write the functions corresponding to the operations of the
@@ -169,7 +168,7 @@
</li>
</ol>
-<h3 class="western"><a name="5.1.1."/>5.1.1. Operation Implementation</h3>
+<h3 class="western"><a name="5.1.1.">5.1.1. Operation Implementation</a></h3>
<p>Following is the implementation of the greet operation:</p>
<!--code -->
@@ -191,7 +190,8 @@
Basically this function receives the request payload as a WSMessage object
instance, prepares the response and returns as a WSMessage instance.</p>
-<h3 class="western"><a name="5.1.2."/>5.1.2. Service Instance Creation with Operations</h3>
+<h3 class="western"><a name="5.1.2.">5.1.2. Service Instance Creation with
+Operations</a></h3>
<p>A service could be created, specifying the operations as shown below:</p>
<pre><span style="color: rgb(0, 0, 255);">$service</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSService<span style="color: rgb(102, 204, 102);">(</span><a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"operations"</span> => <a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"greet"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
@@ -204,21 +204,21 @@
<br>
-<h3><a name="5.1.3."/>5.1.3. Replying to Service Invocations</h3>
+<h3><a name="5.1.3.">5.1.3. Replying to Service Invocations</a></h3>
<pre><span style="color: rgb(0, 0, 255);">$service</span>-><span style="color: rgb(0, 102, 0);">reply</span><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
<p>The reply() method of the service has to be called by all service
implementations. This call would trigger the request processing on server
side and prepare the response to be sent to client.</p>
-<h3><a name="5.1.4."/>5.1.4. Full Source</h3>
+<h3><a name="5.1.4.">5.1.4. Full Source</a></h3>
<p>Here is the complete source code for the service : <a
href="samples/hello_service.html">hello_service.php</a></p>
<br>
-<h3><a name="5.1.5."/>5.1.5. Deploying the Service</h3>
+<h3><a name="5.1.5.">5.1.5. Deploying the Service</a></h3>
<p>In order to make the service available to be consumed by clients, we have
to deploy the service. To deploy the service, you just have to copy the php
@@ -240,13 +240,13 @@
<h2 class="western" style="margin-top: 0in; margin-bottom: 0in"><a
name="5.2.">5.2. Hello Client</a></h2>
-<p>Now that you know how to write a service with WSO2 WSF for PHP , let's see
-how you could write a client to consume that service. The request payload
-that the client would be sending to the service was described in the previous
+<p>Now that you know how to write a service with WSO2 WSF/PHP , let's see how
+you could write a client to consume that service. The request payload that
+the client would be sending to the service was described in the previous
section. The client has to prepare the payload, send a request to the service
and then receive and process the response.</p>
-<p>The steps to be followed when implementing a client with WSO2 WSF for PHP
+<p>The steps to be followed when implementing a client with WSO2 WSF/PHP
include:</p>
<ol>
<li><b>Create a WSMessage instance with desired request payload and
@@ -268,7 +268,7 @@
Process the response in line with the client business logic.</li>
</ol>
-<h3><a name="5.2.1."/>5.2.1. Preparing Request Message</h3>
+<h3><a name="5.2.1.">5.2.1. Preparing Request Message</a></h3>
<pre> <span style="color: rgb(0, 0, 255);">$message</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSMessage<span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(0, 0, 255);">$requestPayloadString</span>,
<a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"to"</span> => <span style="color: rgb(255, 0, 0);">"http://localhost/hello_service.php"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
@@ -280,7 +280,7 @@
<br>
-<h3><a name="5.2.2."/>5.2.2. Sending Request and Receiving Response</h3>
+<h3><a name="5.2.2.">5.2.2. Sending Request and Receiving Response</a></h3>
<pre> <span style="color: rgb(0, 0, 255);">$client</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSClient<span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(102, 204, 102);">)</span>;
<span style="color: rgb(0, 0, 255);">$response</span> = <span style="color: rgb(0, 0, 255);">$client</span>-><span style="color: rgb(0, 102, 0);">request</span><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(0, 0, 255);">$message</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
@@ -297,14 +297,14 @@
<p>In our client sample we access the response payload as a string from the
returned message instance and echo it.</p>
-<h3><a name="5.2.3."/>5.2.3. Full Source</h3>
+<h3><a name="5.2.3.">5.2.3. Full Source</a></h3>
<p>Here is the complete source code for the client : <a
href="samples/hello_client.html">hello_client.html</a></p>
<br>
-<h3><a name="5.2.4."/>5.2.4. Running the Client</h3>
+<h3><a name="5.2.4.">5.2.4. Running the Client</a></h3>
<p>To run the client, copy the client php script to the Web root of your Web
server, as done for the service script, and access the client from the Web
@@ -312,8 +312,8 @@
<h2><a name="Consuming">6. Consuming Web Services</a></h2>
-<p>For consuming Web services with WSO2 WSF for PHP, using the XML in/out
-model, you need to first find out the request payload format and the response
+<p>For consuming Web services with WSO2 WSF/PHP, using the XML in/out model,
+you need to first find out the request payload format and the response
payload format. You also need to know the service endpoint URI.<br>
Once those information is available, you can construct a WSMessage instance
with the payload and service endpoint URI information. These are the minimum
@@ -329,7 +329,7 @@
<p>The following sections explain how you can achieve more with the options
available for WSMessage and WSClient.</p>
-<h3><a name="6.1."/>6.1. Using SOAP</h3>
+<h3><a name="6.1.">6.1. Using SOAP</a></h3>
<p>You can use the "useSOAP" option at client level to specify the SOAP
version to be used. If this option is not set, the default SOAP version used
@@ -351,10 +351,10 @@
<p>There is another option named "HTTPMethod", that you could use to specify
the HTTP method to be used. When SOAP is in use, the default HTTP method used
would be "POST" all the time. If you specify "GET" when SOAP is in use, then
-no request would be sent, because WSO2 WSF for PHP does not support SOAP with
+no request would be sent, because WSO2 WSF/PHP does not support SOAP with
HTTP GET.</p>
-<h3><a name="6.2."/>6.2. Using REST</h3>
+<h3><a name="6.2.">6.2. Using REST</a></h3>
<p>If you want to consume Web services using REST style calls, that can be
done by setting the "useSOAP" option to false. In case of REST style of
@@ -374,15 +374,15 @@
<br>
-<h3><a name="6.3."/>6.3. Payload Formats</h3>
+<h3><a name="6.3.">6.3. Payload Formats</a></h3>
-<p>When invoking Web services, WSO2 WSF for PHP extension allows you to
-provide the message payload either directly as an XML string or as a
-WSMessage instance with the XML string stored inside it. In the future, you
-would be able to pass the payload in SimpleXMLElement and domDocument formats
-to the send() and request() methods of WSClient class. If you want to use
-those formats of XML as payload with this current release, you have to use
-the functions ws_request() and ws_send().</p>
+<p>When invoking Web services, WSO2 WSF/PHP extension allows you to provide
+the message payload either directly as an XML string or as a WSMessage
+instance with the XML string stored inside it. In the future, you would be
+able to pass the payload in SimpleXMLElement and domDocument formats to the
+send() and request() methods of WSClient class. If you want to use those
+formats of XML as payload with this current release, you have to use the
+functions ws_request() and ws_send().</p>
<p>Using a string as the request payload:</p>
<pre><span style="color: rgb(0, 0, 255);">$reqPayloadString</span> = <<<XML
@@ -412,18 +412,18 @@
<span style="color: rgb(0, 0, 255);">$resMessage</span> = <span style="color: rgb(0, 0, 255);">$client</span>-><span style="color: rgb(0, 102, 0);">request</span><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(0, 0, 255);">$reqMessage</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
-<p>WSO2 WSF for PHP extension only supports the XML in/out model for
-consuming services currently. Data binding for PHP would be supported in a
-future release. <br>
+<p>WSO2 WSF/PHP extension only supports the XML in/out model for consuming
+services currently. Data binding for PHP would be supported in a future
+release. <br>
</p>
-<h3><a name="6.4."/>6.4. Attachments with MTOM/XOP</h3>
+<h3><a name="6.4.">6.4. Attachments with MTOM/XOP</a></h3>
-<p>WSO2 WSF for PHP allows you to send and receive binary data with SOAP
-messages using MTOM/XOP conventions. When sending attachments, you have to
-use a WSMessage instance to represent the payload, and give the binary data
-as an array. When receiving attachments, you can get the attachments received
-from the attachments array of the WSMessage instance returned.</p>
+<p>WSO2 WSF/PHP allows you to send and receive binary data with SOAP messages
+using MTOM/XOP conventions. When sending attachments, you have to use a
+WSMessage instance to represent the payload, and give the binary data as an
+array. When receiving attachments, you can get the attachments received from
+the attachments array of the WSMessage instance returned.</p>
<p><br>
For sending an attachment, you need to specify the element where the
@@ -472,18 +472,18 @@
<br>
-<h3><a name="6.5."/>6.5. Using WS-Addressing</h3>
+<h3><a name="6.5.">6.5. Using WS-Addressing</a></h3>
<p><a href="http://www.w3.org/2002/ws/addr/">WS-Addressing</a> provides
-mechanisms to address Web services and messages. With WSO2 WSF for PHP, you
-can use both WS-Addressing <a
-href="http://www.w3.org/TR/ws-addr-core/">version 1.0</a> as well as the <a
+mechanisms to address Web services and messages. With WSO2 WSF/PHP, you can
+use both WS-Addressing <a href="http://www.w3.org/TR/ws-addr-core/">version
+1.0</a> as well as the <a
href="http://www.w3.org/Submission/ws-addressing/">submission version</a>.</p>
<p>There are two basic requirements for using WS-Addressing on client side
-with WSO2 WSF for PHP. One is that you have to provide a WS-Addressing action
-at message level. The other is that you have to enable the use of
-WS-Addressing at client level.</p>
+with WSO2 WSF/PHP. One is that you have to provide a WS-Addressing action at
+message level. The other is that you have to enable the use of WS-Addressing
+at client level.</p>
<pre>
<span style="color: rgb(0, 0, 255);">$reqMessage</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSMessage<span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(0, 0, 255);">$reqPayloadString</span>,
<a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"to"</span>=><span style="color: rgb(255, 0, 0);">"http://localhost/echo_service_addr.php"</span>,
@@ -507,7 +507,7 @@
<span style="color: rgb(0, 0, 255);">$client</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSClient<span style="color: rgb(102, 204, 102);">(</span><a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"useWSA"</span> => <span style="color: rgb(255, 0, 0);">"submission"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
<p>In addition to the action, there are other WS-Addressing related SOAP
-headers that could be sent in a message. WSO2 WSF for PHP has support to set
+headers that could be sent in a message. WSO2 WSF/PHP has support to set
those headers as properties at the message level or as options at the client
level. An example is shown below.</p>
<pre> <span style="color: rgb(0, 0, 255);">$reqMessage</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSMessage<span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(0, 0, 255);">$reqPayloadString</span>,
@@ -527,7 +527,7 @@
manage the order process, with replies and faults being directed to
differently addressed endpoints.</p>
-<h3><a name="6.6."/>6.6. WS-Security UsernameToken</h3>
+<h3><a name="6.6.">6.6. WS-Security UsernameToken</a></h3>
<p>With WSClient, you can use WS-Security usernameTokens, along with
timestamp, time-to-live and digest support. The simplest form of using
@@ -552,7 +552,7 @@
<span style="color: rgb(255, 0, 0);">"timeToLive"</span> => <span style="color: rgb(255, 0, 0);">"5m"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;
</pre>
-<h3><a name="6.7."/>6.7. One-Way Clients</h3>
+<h3><a name="6.7.">6.7. One-Way Clients</a></h3>
<p>The request() method of WSClient that you have seen in the samples so far
adheres to the out-in message exchange patterns. That means, when the client
@@ -572,9 +572,9 @@
client and consumes it, and would not send any response. The return type of
send() is void. In case of errors, it would throw a fault.</p>
-<h3><a name="6.8."/>6.8. Consuming Web Services using Function API</h3>
+<h3><a name="6.8.">6.8. Consuming Web Services using Function API</a></h3>
-<p>WSO2 WSF for PHP provides a function based API, in addition to the object
+<p>WSO2 WSF/PHP provides a function based API, in addition to the object
oriented API that you have already seen, to provide and consume services.
There are two functions that you can use on client side, ws_request() and
ws_send().</p>
@@ -632,15 +632,15 @@
<h2><a name="Providing">7. Providing Web Services</a></h2>
-<p>For providing Web services with WSO2 WSF for PHP, using the XML in/out
-model, you need to first define the request payload format and the response
-payload format for each operation of the services that you intend to provide.
-For each operation in a service, once those payload formats are defined, you
-have to implement the functions that process the incoming request and
-generate the response message corresponding to each operation. When invoking
-a function mapped to a service operation, WSO2 WSF passes a WSMessage object
-instance to that function and expects that function to return a WSMessage
-object instance.<br>
+<p>For providing Web services with WSO2 WSF/PHP, using the XML in/out model,
+you need to first define the request payload format and the response payload
+format for each operation of the services that you intend to provide. For
+each operation in a service, once those payload formats are defined, you have
+to implement the functions that process the incoming request and generate the
+response message corresponding to each operation. When invoking a function
+mapped to a service operation, WSO2 WSF passes a WSMessage object instance to
+that function and expects that function to return a WSMessage object
+instance.<br>
Hence the API for a user implemented function mapping to a service operation
is as follows.</p>
<pre> <b>WSMessage user_defined_operation(WSMessage payload)</b></pre>
@@ -663,7 +663,7 @@
are multiple ways of specifying this mapping.<br>
The simplest form is to use the "operations" option and just give the
function name. You have to keep in mind that if you give only the function
-name, WSO2 WSF for PHP would assume the operation name to be the same as the
+name, WSO2 WSF/PHP would assume the operation name to be the same as the
function name. <br>
</p>
<pre><span style="color: rgb(0, 0, 255);">$server</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSService<span style="color: rgb(102, 204, 102);">(</span><a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"operations"</span> => <a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"echoFunction"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
@@ -698,9 +698,9 @@
<pre><span style="color: rgb(0, 0, 255);">$server</span> = <span style="color: rgb(0, 0, 0); font-weight: bold;">new</span> WSService<span style="color: rgb(102, 204, 102);">(</span><a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"actions"</span> => <a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"echoFunction"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
<p><br>
-In the context of WSO2 WSF for PHP, a single PHP script with WSService
-processing logic would be treated as a single service. Therefore in a service
-PHP script, there has to be only one call to the reply() method on top of a
+In the context of WSO2 WSF/PHP, a single PHP script with WSService processing
+logic would be treated as a single service. Therefore in a service PHP
+script, there has to be only one call to the reply() method on top of a
WSService instance. The reply() method triggers the service to start
processing the request and prepare the response.</p>
<pre><span style="color: rgb(128, 128, 128); font-style: italic;">// create service object instance</span>
@@ -713,14 +713,14 @@
server, that associated URL would naturally become the service endpoint of
that PHP script implementing the service logic.</p>
-<p>As in the case of client side, WSO2 WSF for PHP extension supports more
-than just SOAP on server side as well. You can use WS-Addressing, XOP/MTOM
-and WS-Security UsernameToken when providing and consuming Web services.</p>
+<p>As in the case of client side, WSO2 WSF/PHP extension supports more than
+just SOAP on server side as well. You can use WS-Addressing, XOP/MTOM and
+WS-Security UsernameToken when providing and consuming Web services.</p>
<p>The following sections explains how you can achieve more with the options
available for WSService.</p>
-<h3><a name="7.1."/>7.1. Using SOAP</h3>
+<h3><a name="7.1.">7.1. Using SOAP</a></h3>
<p>On the server side, you do not have to specify any options to use SOAP,
rather based on the version of SOAP used in the client request, service would
@@ -728,14 +728,14 @@
you do not have to bother about the SOAP version. <br>
</p>
-<h3><a name="7.2."/>7.2. Using REST</h3>
+<h3><a name="7.2.">7.2. Using REST</a></h3>
<p>There is no REST support in the current version of WSO2 WSF, however, it
this support would be available in a future release.</p>
-<h3><a name="7.3."/>7.3. Payload Formats</h3>
+<h3><a name="7.3.">7.3. Payload Formats</a></h3>
-<p>As mentioned earlier, the WSO2 WSF for PHP engine invokes the user defined
+<p>As mentioned earlier, the WSO2 WSF/PHP engine invokes the user defined
function mapping to the operation with an instance of a WSMessage object. The
function implementation representing the service's operation can choose to
consume the request in whatever format supported by the WSMessage class. <br>
@@ -743,7 +743,7 @@
service's operation can choose to represent the response in whatever format
supported by the WSMessage class.</p>
-<h3><a name="7.4."/>7.4. Attachments with MTOM/XOP</h3>
+<h3><a name="7.4.">7.4. Attachments with MTOM/XOP</a></h3>
<p>When sending attachments, as in the case of client side, you have to use a
WSMessage instance to represent payload, and give the binary data as an array
@@ -831,7 +831,7 @@
it is a JPEG file. Once saved, it responds to the invoking client with the
response payload.</p>
-<h3><a name="7.5."/>7.5. Using WS-Addressing</h3>
+<h3><a name="7.5.">7.5. Using WS-Addressing</a></h3>
<p>Unlike on the client side, there is no need to enable WS-Addressing
explicitly on server side. If the client request uses WS-Addressing, then the
@@ -860,7 +860,7 @@
the incoming message, the reply would be sent to the specified replyTo
endpoint.</p>
-<h3><a name="7.6."/>7.6. One-Way Operations</h3>
+<h3><a name="7.6.">7.6. One-Way Operations</a></h3>
<p>You can make your service operations adhere to either in-out message
exchange pattern or in-only message exchange pattern. If a function mapped to
@@ -880,7 +880,7 @@
<p>In the above sample, the notify function accepts the payload sent by the
client and consumes it, and would not send any response.</p>
-<h3><a name="7.7."/>7.7. Providing Web Services using Function API</h3>
+<h3><a name="7.7.">7.7. Providing Web Services using Function API</a></h3>
<p>The function based API has a function, namely ws_reply() that you can use
on a service script to reply to client requests.</p>
@@ -894,8 +894,6 @@
<p>Once that file is included, you are ready to use the reply function.<br>
The following code fragment shows how you could specify the operation mapping
to use the function.</p>
-<pre>
-ws_reply<span style="color: rgb(102, 204, 102);">(</span><a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"operations"</span> => <a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"echoString"</span> => <span style="color: rgb(255, 0, 0);">"echoFunction"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;
-</pre>
+<pre>ws_reply<span style="color: rgb(102, 204, 102);">(</span><a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"operations"</span> => <a href="http://www.php.net/array"><span style="color: rgb(0, 0, 102);">array</span></a><span style="color: rgb(102, 204, 102);">(</span><span style="color: rgb(255, 0, 0);">"echoString"</span> => <span style="color: rgb(255, 0, 0);">"echoFunction"</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span><span style="color: rgb(102, 204, 102);">)</span>;</pre>
</body>
</html>
Modified: wsf/php/src/xdocs/manual_toc.html
==============================================================================
--- wsf/php/src/xdocs/manual_toc.html (original)
+++ wsf/php/src/xdocs/manual_toc.html Mon Feb 5 01:19:31 2007
@@ -5,188 +5,231 @@
<title></title>
<meta name="CREATED" content="20061009;17484000">
<meta name="CHANGED" content="20061011;10243100">
-<link href="style/api_style.css" rel="stylesheet" type="text/css" media="all" />
+ <link href="style/api_style.css" rel="stylesheet" type="text/css"
+ media="all">
</head>
<body lang="en-US" dir="ltr">
-<h1>WSO2 WSF for PHP Manual</h1>
+<h1>WSO2 WSF/PHP Manual</h1>
+
<table width="100%">
-<tr>
-<td width="20">1.</td>
-<td><a href="manual_content.html#Introduction" target="mainFrame">Introduction</a></td>
-</tr>
-<tr>
-<td width="20">2.</td>
-<td><a href="manual_content.html#Requirements" target="mainFrame">Requirements</a></td>
-</tr>
-<tr>
-<td width="20">3.</td>
-<td><a href="manual_content.html#Installation" target="mainFrame">Installation</a></td>
-</tr>
-<tr>
-<td width="20">4.</td>
-<td><a href="manual_content.html#Runtime" target="mainFrame">Runtime Configuration</a></td>
-</tr>
-<tr>
-<td width="20">5.</td>
-<td><a href="manual_content.html#Quick" target="mainFrame">Quick Start Guide</a></td>
-</tr>
-<tr>
-<td></td>
-<td>
-<table>
-<tr>
-<td width="20">5.1.</td>
-<td><a href="manual_content.html#5.1." target="mainFrame">Hello Service</a></td>
-</tr>
-<tr>
-<td></td>
-<td>
-<table>
-<tr>
-<td width="20">5.1.1.</td>
-<td><a href="manual_content.html#5.1.1." target="mainFrame">Operation Implementation</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.1.2.</td>
-<td><a href="manual_content.html#5.1.2." target="mainFrame">Service Instance Creation with Operations</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.1.3.</td>
-<td><a href="manual_content.html#5.1.3." target="mainFrame"> Replying to Service Invocations</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.1.4.</td>
-<td><a href="manual_content.html#5.1.4." target="mainFrame">Full Source</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.1.5.</td>
-<td><a href="manual_content.html#5.1.5." target="mainFrame">Deploying the Service</a>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td>5.2.</td>
-<td><a href="manual_content.html#5.2." target="mainFrame">Hello Client</a></td>
-</tr>
-<tr>
-<td></td>
-<td>
-<table>
-<tr>
-<td width="20">5.2.1.</td>
-<td><a href="manual_content.html#5.2.1." target="mainFrame">Preparing Request Message</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.2.2.</td>
-<td><a href="manual_content.html#5.2.2." target="mainFrame">Sending Request and Receiving Response</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.2.3.</td>
-<td><a href="manual_content.html#5.2.3." target="mainFrame">Full Source</a>
-</td>
-</tr>
-<tr>
-<td width="20">5.2.4.</td>
-<td><a href="manual_content.html#5.2.4." target="mainFrame">Running the Client</a>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td>6.</td>
-<td><a href="manual_content.html#Consuming" target="mainFrame">Consuming Web Services</a></td>
-</tr>
-<tr>
-<td></td>
-<td>
-<table>
-<tr>
-<td width="20">6.1.</td>
-<td><a href="manual_content.html#6.1." target="mainFrame">Using SOAP</a></td>
-</tr>
-<tr>
-<td width="20">6.2.</td>
-<td><a href="manual_content.html#6.2." target="mainFrame">Using REST</a></td>
-</tr>
-<tr>
-<td width="20">6.3.</td>
-<td><a href="manual_content.html#6.3." target="mainFrame">Payload Formats</a></td>
-</tr>
-<tr>
-<td width="20">6.4.</td>
-<td><a href="manual_content.html#6.4." target="mainFrame">Attachments with MTOM/XOP</a></td>
-</tr>
-<tr>
-<td width="20">6.5.</td>
-<td><a href="manual_content.html#6.5." target="mainFrame">Using WS-Addressing</a></td>
-</tr>
-<tr>
-<td width="20">6.6.</td>
-<td><a href="manual_content.html#6.6." target="mainFrame">WS-Security UsernameToken</a></td>
-</tr>
-<tr>
-<td width="20">6.7.</td>
-<td><a href="manual_content.html#6.7." target="mainFrame">One-Way Clients</a></td>
-</tr>
-<tr>
-<td width="20">6.8.</td>
-<td><a href="manual_content.html#6.8." target="mainFrame">Consuming Web Services using Function API</a></td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td>7.</td>
-<td><a href="manual_content.html#Providing" target="mainFrame">Providing Web Services</a></td>
-</tr>
-<tr>
-<td></td>
-<td>
-<table>
-<tr>
-<td width="20">7.1.</td>
-<td><a href="manual_content.html#7.1." target="mainFrame">Using SOAP</a></td>
-</tr>
-<tr>
-<td width="20">7.2.</td>
-<td><a href="manual_content.html#7.2." target="mainFrame">Using REST</a></td>
-</tr>
-<tr>
-<td width="20">7.3.</td>
-<td><a href="manual_content.html#7.3." target="mainFrame">Payload Formats</a></td>
-</tr>
-<tr>
-<td width="20">7.4.</td>
-<td><a href="manual_content.html#7.4." target="mainFrame">Attachments with MTOM/XOP</a></td>
-</tr>
-<tr>
-<td width="20">7.5.</td>
-<td><a href="manual_content.html#7.5." target="mainFrame">Using WS-Addressing</a></td>
-</tr>
-<tr>
-<td width="20">7.6.</td>
-<td><a href="manual_content.html#7.6." target="mainFrame">One-Way Operations</a></td>
-</tr>
-<tr>
-<td width="20">7.7.</td>
-<td><a href="manual_content.html#7.7." target="mainFrame">Providing Web Services using Function API</a></td>
-</tr>
-</table>
-</td>
-</tr>
+ <tbody>
+ <tr>
+ <td width="20">1.</td>
+ <td><a href="manual_content.html#Introduction"
+ target="mainFrame">Introduction</a></td>
+ </tr>
+ <tr>
+ <td width="20">2.</td>
+ <td><a href="manual_content.html#Requirements"
+ target="mainFrame">Requirements</a></td>
+ </tr>
+ <tr>
+ <td width="20">3.</td>
+ <td><a href="manual_content.html#Installation"
+ target="mainFrame">Installation</a></td>
+ </tr>
+ <tr>
+ <td width="20">4.</td>
+ <td><a href="manual_content.html#Runtime" target="mainFrame">Runtime
+ Configuration</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.</td>
+ <td><a href="manual_content.html#Quick" target="mainFrame">Quick Start
+ Guide</a></td>
+ </tr>
+ <tr>
+ <td></td>
+ <td>
+ <table>
+ <tbody>
+ <tr>
+ <td width="20">5.1.</td>
+ <td><a href="manual_content.html#5.1." target="mainFrame">Hello
+ Service</a></td>
+ </tr>
+ <tr>
+ <td></td>
+ <td>
+ <table>
+ <tbody>
+ <tr>
+ <td width="20">5.1.1.</td>
+ <td><a href="manual_content.html#5.1.1."
+ target="mainFrame">Operation Implementation</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.1.2.</td>
+ <td><a href="manual_content.html#5.1.2."
+ target="mainFrame">Service Instance Creation with
+ Operations</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.1.3.</td>
+ <td><a href="manual_content.html#5.1.3."
+ target="mainFrame">Replying to Service
+ Invocations</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.1.4.</td>
+ <td><a href="manual_content.html#5.1.4."
+ target="mainFrame">Full Source</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.1.5.</td>
+ <td><a href="manual_content.html#5.1.5."
+ target="mainFrame">Deploying the Service</a></td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td>5.2.</td>
+ <td><a href="manual_content.html#5.2." target="mainFrame">Hello
+ Client</a></td>
+ </tr>
+ <tr>
+ <td></td>
+ <td>
+ <table>
+ <tbody>
+ <tr>
+ <td width="20">5.2.1.</td>
+ <td><a href="manual_content.html#5.2.1."
+ target="mainFrame">Preparing Request Message</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.2.2.</td>
+ <td><a href="manual_content.html#5.2.2."
+ target="mainFrame">Sending Request and Receiving
+ Response</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.2.3.</td>
+ <td><a href="manual_content.html#5.2.3."
+ target="mainFrame">Full Source</a></td>
+ </tr>
+ <tr>
+ <td width="20">5.2.4.</td>
+ <td><a href="manual_content.html#5.2.4."
+ target="mainFrame">Running the Client</a></td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td>6.</td>
+ <td><a href="manual_content.html#Consuming"
+ target="mainFrame">Consuming Web Services</a></td>
+ </tr>
+ <tr>
+ <td></td>
+ <td>
+ <table>
+ <tbody>
+ <tr>
+ <td width="20">6.1.</td>
+ <td><a href="manual_content.html#6.1." target="mainFrame">Using
+ SOAP</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.2.</td>
+ <td><a href="manual_content.html#6.2." target="mainFrame">Using
+ REST</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.3.</td>
+ <td><a href="manual_content.html#6.3."
+ target="mainFrame">Payload Formats</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.4.</td>
+ <td><a href="manual_content.html#6.4."
+ target="mainFrame">Attachments with MTOM/XOP</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.5.</td>
+ <td><a href="manual_content.html#6.5." target="mainFrame">Using
+ WS-Addressing</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.6.</td>
+ <td><a href="manual_content.html#6.6."
+ target="mainFrame">WS-Security UsernameToken</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.7.</td>
+ <td><a href="manual_content.html#6.7."
+ target="mainFrame">One-Way Clients</a></td>
+ </tr>
+ <tr>
+ <td width="20">6.8.</td>
+ <td><a href="manual_content.html#6.8."
+ target="mainFrame">Consuming Web Services using Function
+ API</a></td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td>7.</td>
+ <td><a href="manual_content.html#Providing"
+ target="mainFrame">Providing Web Services</a></td>
+ </tr>
+ <tr>
+ <td></td>
+ <td>
+ <table>
+ <tbody>
+ <tr>
+ <td width="20">7.1.</td>
+ <td><a href="manual_content.html#7.1." target="mainFrame">Using
+ SOAP</a></td>
+ </tr>
+ <tr>
+ <td width="20">7.2.</td>
+ <td><a href="manual_content.html#7.2." target="mainFrame">Using
+ REST</a></td>
+ </tr>
+ <tr>
+ <td width="20">7.3.</td>
+ <td><a href="manual_content.html#7.3."
+ target="mainFrame">Payload Formats</a></td>
+ </tr>
+ <tr>
+ <td width="20">7.4.</td>
+ <td><a href="manual_content.html#7.4."
+ target="mainFrame">Attachments with MTOM/XOP</a></td>
+ </tr>
+ <tr>
+ <td width="20">7.5.</td>
+ <td><a href="manual_content.html#7.5." target="mainFrame">Using
+ WS-Addressing</a></td>
+ </tr>
+ <tr>
+ <td width="20">7.6.</td>
+ <td><a href="manual_content.html#7.6."
+ target="mainFrame">One-Way Operations</a></td>
+ </tr>
+ <tr>
+ <td width="20">7.7.</td>
+ <td><a href="manual_content.html#7.7."
+ target="mainFrame">Providing Web Services using Function
+ API</a></td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ </tbody>
</table>
</body>
</html>
Modified: wsf/php/src/xdocs/wsdl_generation_api.html
==============================================================================
--- wsf/php/src/xdocs/wsdl_generation_api.html (original)
+++ wsf/php/src/xdocs/wsdl_generation_api.html Mon Feb 5 01:19:31 2007
@@ -5,7 +5,8 @@
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<title>WS02 WSF WSDL generation API</title>
- <meta name="generator" content="amaya 9.52, see http://www.w3.org/Amaya/" />
+ <meta name="generator" content="amaya 9.2.1, see http://www.w3.org/Amaya/"
+ />
</head>
<body>
@@ -13,8 +14,8 @@
<p></p>
-<p>WSDL Generation in WSF for PHP is done using PHP reflection and an
-annotation parser. In order to generate a WSDL from a given WSF for PHP
+<p>WSDL Generation in WSO2 WSF/PHP is done using PHP reflection and an
+annotation parser. In order to generate a WSDL from a given WSO2 WSF/PHP
service, a ?wsdl request should be sent to the server. For example, if you
want to generate the WSDL for the service echoService.php, a request should
be sent as,</p>
@@ -131,8 +132,8 @@
<td>float</td>
</tr>
<tr>
- <td>int </td>
- <td>int </td>
+ <td>int</td>
+ <td>int</td>
</tr>
<tr>
<td>integer</td>
@@ -155,7 +156,7 @@
<td>string</td>
</tr>
<tr>
- <td>anyType </td>
+ <td>anyType</td>
<td>soap var object</td>
</tr>
<tr>
@@ -179,11 +180,11 @@
<td>string</td>
</tr>
<tr>
- <td>unsignedLong </td>
+ <td>unsignedLong</td>
<td>int</td>
</tr>
<tr>
- <td>unsignedInt </td>
+ <td>unsignedInt</td>
<td>int</td>
</tr>
<tr>
@@ -287,10 +288,9 @@
<td>string</td>
</tr>
<tr>
- <td>token </td>
+ <td>token</td>
<td>string</td>
</tr>
-
</tbody>
</table>
More information about the Wsf-c-dev
mailing list