nmukhi 2002/12/16 10:42:15 Modified: java/doc quick-start.html user-guide.html Added: java/doc bugs.html customising.html Log: Fixed broken links, added more docs Revision Changes Path 1.2 +7 -7 xml-axis-wsif/java/doc/quick-start.html Index: quick-start.html =================================================================== RCS file: /home/cvs/xml-axis-wsif/java/doc/quick-start.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- quick-start.html 16 Dec 2002 18:29:05 -0000 1.1 +++ quick-start.html 16 Dec 2002 18:42:15 -0000 1.2 @@ -3,25 +3,25 @@ <meta name="Author" content="Aleksander Slominski"> <meta http-equiv="Content-Style-Type" content="text/css"><title>Web Services Invocation Framework: Quick Start</title> -<link rel="stylesheet" href="doc/wsif.css" type="text/css"></head> +<link rel="stylesheet" href="wsif.css" type="text/css"></head> <body alink="#0000ff" bgcolor="#ffffff" leftmargin="2" topmargin="2" marginwidth="2" marginheight="2"> <h2>Web Services Invocation Framework: Quick Start</h2> <p><b>Preliminaries</b>: Download the WSIF distribution from <a href="http://cvs.apache.org/dist/axis/wsif/";> -http://cvs.apache.org/dist/axis/wsif/</a>. It comes in three flavors: the binary distribution ("bin"), the source-only distribution ("src%quot;) or everything +http://cvs.apache.org/dist/axis/wsif/</a>. It comes in three flavors: the binary distribution ("bin"), the source-only distribution ("src") or everything included ("all"). If you are familiar with CVS and -want to work with the latest code <a href="doc/cvs.html">use cvs</a>. Using CVS +want to work with the latest code <a href="cvs.html">use cvs</a>. Using CVS you can also retrieve any past release by using tag (for example WSIF_2_0_ALPHA2).</p> <p><b>Getting started: </b>If you have downloaded binary package then you are ready to use WSIF: the very first thing to do is to check provided samples. However before you start -please read <a href="doc/faq.htm">WSIF FAQ</a>. Then read about <a href="doc/samples.html"> +please read <a href="faq.htm">WSIF FAQ</a>. Then read about <a href="samples.html"> how to run the samples</a>. Otherwise if you downloaded source code or accessed it from CVS you will need -to build WSIF. To do this, first <a href="doc/requirements.html">check that all -prerequisites</a> are available. Then <a href="doc/build.htm">proceed with +to build WSIF. To do this, first <a href="requirements.html">check that all +prerequisites</a> are available. Then <a href="build.htm">proceed with building</a>.</p> <p>After you have successfully downloaded and installed WSIF, you - can test your installation by <a href="doc/samples.html">running the + can test your installation by <a href="samples.html">running the samples</a>. If you are able to run all the samples successfully you should have a very good idea of what you can do with WSIF. Essentially once you have a WSDL file with a binding 1.2 +6 -12 xml-axis-wsif/java/doc/user-guide.html Index: user-guide.html =================================================================== RCS file: /home/cvs/xml-axis-wsif/java/doc/user-guide.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- user-guide.html 16 Dec 2002 18:29:05 -0000 1.1 +++ user-guide.html 16 Dec 2002 18:42:15 -0000 1.2 @@ -13,8 +13,7 @@ <ul> <li><a href="#whatisit">What is WSIF?</a></li> <li><a href="#usingit">How to I use WSIF to invoke various WSDL-described services, including SOAP services, EJBs, JMS, and legacy apps via the java connector framework?</a></li> - <li><a href="bugs.html">Reporting Bugs</a></li> - <li><a href="mail.html">Mailing lists</a></li> + <li><a href="bugs.html">Reporting Bugs and getting help</a></li> </ul> <hr> <a name="whatisit"><h2>What is WSIF?</h2></a> @@ -29,21 +28,16 @@ <p>WSIF is capable of invoking any WSDL-described service. The <a href="http://www.w3.org/TR/wsdl12/";>WSDL 1.2 specification</a> defines the current WSDL standard, and an associated document, <a href="http://www.w3.org/TR/2002/WD-wsdl12-bindings-20020709/";>WSDL 1.2 bindings</a>, defines standard binding extensions that describe how to use the SOAP, HTTP and MIME protocols to invoke services described using WSDL.</p> <p>WSIF defines additional binding extensions so that EJBs, local java classes, software accessible over message queues using the JMS API and software that can be invoked using the Java Connector architecture can also be described in WSDL. WSIF is packaged with providers that allow transparent invocation of such software given the corresponding WSDL description. Here are the documents that describe these bindings: <ul> - <li><a href="wsdl_extensions/java_extensions.htm">Local java binding extensions for WSDL</a></li> - <li><a href="wsdl_extensions/ejb_extensions.htm">EJB binding extensions for WSDL</a></li> + <li><a href="wsdl_extensions/java_extension.htm">Local java binding extensions for WSDL</a></li> + <li><a href="wsdl_extensions/ejb_extension.htm">EJB binding extensions for WSDL</a></li> <li><a href="wsdl_extensions/jms_bindings.htm">JMS binding extensions for WSDL</a></li> <li><a href="wsdl_extensions/j2c_extensions/wsif_j2c_extensions.htm">JCA binding extensions for WSDL</a></li> </ul> </p> - <p>The WSIF distribution includes samples that show you how to invoke such services using the WSIF API. The <a href="saples.html">Samples documentation</a> describes them.</p> + <p>The WSIF distribution includes samples that show you how to invoke such services using the WSIF API. The <a href="samples.html">Samples documentation</a> describes them.</p> <hr> - <a name="reportingbugs"><h2>Bugs</h2> - <p>You can find a list of outstanding bugs from <a - href="http://nagoya.apache.org/bugzilla/buglist.cgi?long_desc=wsif&long_desc_type=allwordssubstr";>Bugzilla</a>.</p> - <p>You can get yourself a Bugzilla login and register a new bug using the same web site.</p> + <a name="reportingbugs"><h2>Reporting bugs and getting help</h2> + <p>You can report bugs using Apache'sBugzilla system, as described <a href="bugs.html">here</a>. Post to the axis-user mailing list for help, as described <a href="mail.html">here</a>.</p> <hr> - <a name="mailinglist"><h2>Getting help</h2> - <P>WSIF shares the Apache AXIS <a href="http://xml.apache.org/axis/mail.html";>mailing list</a> -axis-user. To aid identifying posts about WSIF, the prefix <b>[wsif]</b> should be added to each posts subject line.</P> <hr width="100%"> </body></html> 1.1 xml-axis-wsif/java/doc/bugs.html Index: bugs.html =================================================================== <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Author" content="Aleksander Slominski, Nirmal Mukhi"> <meta http-equiv="Content-Style-Type" content="text/css"> <title>Web Services Invocation Framework: Bugs</title> <link rel="stylesheet" href="wsif.css" type="text/css"></head> <body alink="#0000ff" bgcolor="#ffffff" leftmargin="2" topmargin="2" marginwidth="2" marginheight="2"> <table width=100%><tr bgcolor="#82ADF6"><td> <b><font size=+2> Bugs </font></b> </td></tr> </table> <p> New WSIF bugs should be reported using <a href="http://nagoya.apache.org/bugzilla"; target="_top">Bugzilla</a> (the Apache bug database). <ul> <li>Please report bugs against the newest release.</li> <li> To avoid duplicate bug reports, please query Bugzilla to see whether the bug has already been reported (and perhaps fixed). Click on <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?long_desc=wsif&long_desc_type=allwordssubstr";> WSIF open bugs</a> for a list with links to each bug report.</li> <li>If you can't find your bug in the database, it would help if you could check out WSIF from CVS, and build it locally to verify that the bug still exists.</li> <li>If you have found a new bug, please enter a WSIF bug report in Bugzilla. Remember to include the following information: <ul> <li>Version number of WSIF <li>Version number of JDK (enter "java -fullversion") <li>Instructions for how to reproduce the problem, ideally including a small testcase. </ul> <p> <i>Before you can enter your first bug report, you must submit your email address to Bugzilla and receive a password.</i> </ul> <p>For more information visit the following links:</p> <ul> <li><a href="http://nagoya.apache.org/bugzilla/";>Apache Bugzilla</a></li> <li><a href="http://www.mozilla.org/bugs/";>General Bugzilla information</a></li> </ul> <p>We also encourage you to write patches for problems you find and submit them to the <a href="mailto:[EMAIL PROTECTED]";>axis-dev</a> mailing list (prefix your message with <tt>[wsif]</tt>). If we agree the problem is a bug and the patch fixes it and does not break something else, we are likely to include the patch in the next release. <hr width="100%"> </body></html> 1.1 xml-axis-wsif/java/doc/customising.html Index: customising.html =================================================================== <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Author" content="Aleksander Slominski, Nirmal Mukhi"> <meta http-equiv="Content-Style-Type" content="text/css"> <title>Web Services Invocation Framework: Customising your WSIF installation</title> <link rel="stylesheet" href="wsif.css" type="text/css"></head> <body alink="#0000ff" bgcolor="#ffffff" leftmargin="2" topmargin="2" marginwidth="2" marginheight="2"> <p>This part of documentation is meant to help developers who want to modify WSIF by adding or changing its providers and implementing new protocols.</p> <p>There are many points within the WSIF API that allow for customization. <a href="doc/samples.html">An advanced WSIF sample</a> demonstrates how to write your own WSIF service factory so that dynamic binding selection follows your own customized algorithm. The user can discover other customization points by examining <a href="http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/docs/apidocs/index.html";>WSIF's core API</a>.</p> <p>Larger scale customization involves finding ways to expose software that uses your proprietary protocols through WSDL, so that you can then access this software using WSIF's APIs. To do this, you need to take care of the following:</p> <ol> <li><a href="doc/how_to_wsdl_extensions.htm">Writing your own WSDL extensions to support new protocols</a></li> <li><a href="doc/how_to_provider.htm">Writing your own WSIF providers to support customized WSIF extensions</a></li> </ol> <p>WSIF defines binding extensions so that EJBs, local java classes, software accessible over message queues using the JMS API and software that can be invoked using the Java Connector architecture can also be described in WSDL. WSIF is packaged with providers that allow transparent invocation of such software given the corresponding WSDL description. Here are the documents that describe these bindings: <ul> <li><a href="wsdl_extensions/java_extensions.htm">Local java binding extensions for WSDL</a></li> <li><a href="wsdl_extensions/ejb_extensions.htm">EJB binding extensions for WSDL</a></li> <li><a href="wsdl_extensions/jms_bindings.htm">JMS binding extensions for WSDL</a></li> <li><a href="wsdl_extensions/j2c_extensions/wsif_j2c_extensions.htm">JCA binding extensions for WSDL</a></li> </ul> <p>You may find also useful to read about using <a href="doc/mime_attachments.htm">Soap Attachments using WSIF</a> and always important when debugging - <a href="doc/trace.htm"> how to use tracing in WSIF</a>.<BR> <BR>
