toshi 2004/06/17 04:20:16
Modified: targets/axis site.html ref.pdf ref.html Log: for http://issues.apache.org/jira/browse/AXIS-1398 Revision Changes Path 1.19 +46 -36 ws-site/targets/axis/site.html Index: site.html =================================================================== RCS file: /home/cvs/ws-site/targets/axis/site.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- site.html 12 May 2004 06:39:59 -0000 1.18 +++ site.html 17 Jun 2004 11:20:15 -0000 1.19 @@ -279,12 +279,17 @@ </div> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>NEWS (May 07, 2004) : Axis C++<a href="#http://ws.apache.org/axis/cpp/download.html";>1.1.1 +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>NEWS (June 15, 2004) : Axis C++<a href="#http://ws.apache.org/axis/cpp/download.html";>1.2 Alpha </a> is now available! </p> <hr xmlns:cinclude="http://apache.org/cocoon/include/1.0";> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>NEWS (May 07, 2004) : Axis C++<a href="#http://ws.apache.org/axis/cpp/download.html";>1.1.1 + </a> is now available! +</p> + + <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>NEWS (April 16, 2004) : Axis C++<a href="#http://ws.apache.org/axis/cpp/download.html";>1.1 </a> is now available! </p> @@ -391,6 +396,9 @@ </div> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>(June 15, 2004) : Axis C++ <a href="http://www.apache.org/dist/ws/axis-c/";><b>1.2 Alpha is available!</b></a> +</p> + <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>(May 07, 2004) : Axis C++ <a href="http://www.apache.org/dist/ws/axis-c/";><b>1.1.1 is available!</b></a> </p> @@ -566,7 +574,7 @@ <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> Anyone can checkout source code from our anonymous CVS server. To do so, simply use the following commands (if you - are using a GUI CVS client, configure it appropriatly): + are using a GUI CVS client, configure it appropriately): </p> <blockquote xmlns:cinclude="http://apache.org/cocoon/include/1.0";> @@ -597,7 +605,7 @@ If you are a <i xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Committer</i> and have a login on the Apache development server, this section is for you. If you are not a Committer, but you want to submit patches or even request - commit privelages, please see the <a href="#http://jakarta.apache.org/site/guidelines.html";>Jakarta + commit privileges, please see the <a href="#http://jakarta.apache.org/site/guidelines.html";>Jakarta GuideLines</a> page (we follow the same rules) for more information. <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> @@ -866,7 +874,7 @@ <b><a href="#http://www.cvshome.org/docs/manual/cvs.html";>Version Management with CVS</a></b> -<br>Written by Per Cederqvist at al, this is the main manual for CVS. It +<br>Written by Per Cederqvist et al, this is the main manual for CVS. It provides details on all documented CVS features. </p> @@ -1129,7 +1137,7 @@ <div class="h5"> <h5>Tomcat 4.x and Java 1.4</h5> </div> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Java 1.4 changed the rules as to to how packages beginning in java.* and javax.* get loaded. Specifically, they only get loaded from <em>endorsed</em> directories. jaxrpc.jar and saaj.jar contain javax packages, so they may not get picked up. If happyaxis.jsp (see below) cannot find the relevant packages, copy them from axis/WEB-INF/lib to CATALINA_HOME/common/lib and restart Tomcat. </p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Java 1.4 changed the rules as to how packages beginning in java.* and javax.* get loaded. Specifically, they only get loaded from <em>endorsed</em> directories. jaxrpc.jar and saaj.jar contain javax packages, so they may not get picked up. If happyaxis.jsp (see below) cannot find the relevant packages, copy them from axis/WEB-INF/lib to CATALINA_HOME/common/lib and restart Tomcat. </p> <div class="h5"> <h5>Step 3: starting the web server</h5> </div> @@ -1158,7 +1166,7 @@ <div class="h5"> <h5>Look for some services</h5> </div> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>From the start page, select <em>View the list of deployed Web services</em>. This will list all registered Web Services, unless the servlet is configured not to do so. On this page, You should be able to click on <em>(wsdl)</em> for each deployed Web service to make sure that your web service is up and running.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>From the start page, select <em>View the list of deployed Web services</em>. This will list all registered Web Services, unless the servlet is configured not to do so. On this page, you should be able to click on <em>(wsdl)</em> for each deployed Web service to make sure that your web service is up and running.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note that the 'instant' JWS Web Services that Axis supports are not listed in this listing here. The install guide covers this topic in detail.</p> <div class="h5"> <h5>Test a SOAP Endpoint</h5> @@ -1186,12 +1194,12 @@ <h5>Step 5: Installing new Web Services</h5> </div> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>So far you have got Axis installed and working--now it is time to add your own Web Service.</p> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>The process here boils down to (1) get the classes and libraries of your new service into the Axis WAR directory tree, and (2) tell the AxisEngine about the new file. The latter is done by submitting an XML deployment descriptor to the service via the Admin web service, which is usually done with the AdminClient program or the <axis-admin> Ant task. Both of these do the same thing: they run the Axis SOAP client to talk to the Axis adminstration service, which is a SOAP service in its own right. It's also a special SOAP service in one regard--it is restricted to local callers only (not remote access) and is password protected to stop random people from administrating your service. There is a default password that the client knows; if you change it then you need to pass the new password to the client.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>The process here boils down to (1) get the classes and libraries of your new service into the Axis WAR directory tree, and (2) tell the AxisEngine about the new file. The latter is done by submitting an XML deployment descriptor to the service via the Admin web service, which is usually done with the AdminClient program or the <axis-admin> Ant task. Both of these do the same thing: they run the Axis SOAP client to talk to the Axis administration service, which is a SOAP service in its own right. It's also a special SOAP service in one regard--it is restricted to local callers only (not remote access) and is password protected to stop random people from administrating your service. There is a default password that the client knows; if you change it then you need to pass the new password to the client.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>The first step is to add your code to the server.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>In the WEB-INF directory, look for (or create) a "classes" directory (i.e. axis/WEB-INF/classes ). In this directory, copy the compiled Java classes you wish to install, being careful to preserve the directory structure of the Java packages.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>If your classes services are already packaged into JAR files, feel free to drop them into the WEB-INF/lib directory instead. Also add any third party libraries you depend on into the same directory.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>After adding new classes or libraries to the Axis webapp, you must restart the webapp. This can be done by restarting your application server, or by using a server-specific mechanism to restart a specific webapp.</p> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note:Note: If your web service uses the simple authorization handlers provided with xml-axis (this is actually <u>not</u> recommended as these are merely illustrations of how to write a handler than intended for production use), then you will need to copy the corresponding users.lst file into the WEB-INF directory.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note: If your web service uses the simple authorization handlers provided with xml-axis (this is actually <u>not</u> recommended as these are merely illustrations of how to write a handler than intended for production use), then you will need to copy the corresponding users.lst file into the WEB-INF directory.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <a name="java/install.html#deploy"></a> </p> @@ -1207,7 +1215,7 @@ <br> On Windows, this can be done via the following. For this document we assume that you have installed Axis in C:\axis. To store this information permanently in WinNT/2000/XP you will need to right click on "My Computer" and select "Properties". Click the "Advanced" tab and create the new environmental variables. It is often better to use WordPad to create the variable string and then paste it into the appropriate text field.</p> <pre xmlns:cinclude="http://apache.org/cocoon/include/1.0"; class="xml"> set AXIS_HOME=c:\axis<br> set AXIS_LIB=%AXIS_HOME%\lib<br> set AXISCLASSPATH=%AXIS_LIB%\axis.jar;%AXIS_LIB%\commons-discovery.jar;<br> %AXIS_LIB%\commons-logging.jar;%AXIS_LIB%\jaxrpc.jar;%AXIS_LIB%\saaj.jar;<br> %AXIS_LIB%\log4j-1.2.8.jar;%AXIS_LIB%\xml-apis.jar;%AXIS_LIB%\xercesImpl.jar </pre> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Unix users have to do something similar. Below we have installed AXIS into /usr/axis and are using the bash shell. See your shell's documentation for differences. To make variables permenate you will need to add them to your shell's startup (dot) files. Again, see your shell's documentation.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Unix users have to do something similar. Below we have installed AXIS into /usr/axis and are using the bash shell. See your shell's documentation for differences. To make variables permeate you will need to add them to your shell's startup (dot) files. Again, see your shell's documentation.</p> <pre xmlns:cinclude="http://apache.org/cocoon/include/1.0"; class="xml"> set AXIS_HOME=/usr/axis<br> set AXIS_LIB=$AXIS_HOME/lib<br> set AXISCLASSPATH=$AXIS_LIB/axis.jar:$AXIS_LIB/commons-discovery.jar:<br> $AXIS_LIB/commons-logging.jar:$AXIS_LIB/jaxrpc.jar:$AXIS_LIB/saaj.jar:<br> $AXIS_LIB/log4j-1.2.8.jar:$AXIS_LIB/xml-apis.jar:$AXIS_LIB/xercesImpl.jar<br> export AXIS_HOME; export AXIS_LIB; export AXISCLASSPATH </pre> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>To use Axis client code, you can select AXISCLASSPATH when invoking Java by entering</p> @@ -1234,7 +1242,7 @@ org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy.wsdd</pre> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>If you get some java client error (like ClassNotFoundException), then you haven't set up your AXISCLASSPATH (or CLASSPATH) variable right, mistyped the classname, or did some other standard error. Tracking down such problems are foundational Java development skills--if you don't know how to do these things, learn them now!</p> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note:Note: You may need to replace localhost with your host name, and 8080 with the port number used by your web server. If you have renamed the web application to something other than "axis" change the URL appropriately.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note: You may need to replace localhost with your host name, and 8080 with the port number used by your web server. If you have renamed the web application to something other than "axis" change the URL appropriately.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>If you get some AxisFault listing, then the client is working, but the deployment was unsuccessful. This is where the knowledge of the sockets API to TCP and the basics of the HTTP that Web Service development requires begins to be needed. If you got some socket error like connection refused, the computer at the far end isn't talking to you, so find the cause of that and fix it. If you get an HTTP error code back find out what the error means and correct the problem. These skills are fundamental to using web services.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>The <a href="#user-guide.html">user's guide</a> covers the AdminClient in more detail, and there is also an <a href="#ant/axis-admin.html">Ant task</a> to automate the use of Axis in your Ant build scripts.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> @@ -1255,7 +1263,7 @@ </li> <li>You should get back "55.25" as a result.</li> </ul> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note:Note: Again, you may need to replace localhost with your host name, and 8080 with the port number used by your web server. If you have renamed the web application to something other than "axis" change the URL appropriately.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Note: Again, you may need to replace localhost with your host name, and 8080 with the port number used by your web server. If you have renamed the web application to something other than "axis" change the URL appropriately.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <a name="java/install.html#advanced"></a> </p> @@ -1287,8 +1295,8 @@ <li>Post meaningful subject lines. You want your message read, not deleted unread. A subject line of 'Axis problem', 'Help with Axis', etc. is not meaningful, and is not likely to get many readers.</li> <li>Search the <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=49";>mailing list archives</a> FIRST to see if someone had the same problem. This list is searchable--and may save you much time in getting an answer to your problem.</li> <li>Use the <a href="http://issues.apache.org/jira/";>jira</a> database to search for Axis bugs, both open and closed.</li> -<li>Consult the <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages";>Axis Wiki</a> For its Frequently Asked Questions (FAQ), installation notes, interoperability issues lists, and other useful information.</li> -<li>Don't email people for help directly, unless you know them. It's rude and presumptious. Messages sent over the mail list benefit the whole community--both the original posters and people who search the list. Personal messages just take up the recipients time, and are unwelcome. Usually, if not ignored outright, recipients of personal requests will just respond 'ask the mail list' anyway!</li> +<li>Consult the <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages";>Axis Wiki</a> for its Frequently Asked Questions (FAQ), installation notes, interoperability issues lists, and other useful information.</li> +<li>Don't email people for help directly, unless you know them. It's rude and presumptuous. Messages sent over the mail list benefit the whole community--both the original posters and people who search the list. Personal messages just take up the recipients time, and are unwelcome. Usually, if not ignored outright, recipients of personal requests will just respond 'ask the mail list' anyway!</li> <li>Know that configuration problems are hard to replicate, and so can be difficult to get help on. We have tried with the happyaxis.jsp demo to automate the diagnostics gathering for you, but it can be hard for people to be of help here, especially for obscure platforms.</li> <li>Keep up to date with Axis releases, even the beta copies of forthcoming releases. You wouldn't want your problem to be a bug that was already known and fixed in a more recent release. Often the common response to any question is 'have you tried the latest release'.</li> <li>Study and use the source, and fix it when you find defects. Even fix the documentation when you find defects. It is only through the participation of Axis' users that it will ever get better.</li> @@ -2530,7 +2538,7 @@ <li>error - Other runtime errors or unexpected conditions. Expect these to be immediately visible on a console, and MUST be internationalized.</li> <li style="list-style: none"> <br> </li> -<li>warn - Use of deprecated APIs, poor use of API, Almost errors, other runtime situations that are undesirable or unexpected, but not necessarily "wrong". Expect these to be immediately visible on a console, and MUST be internationalized.</li> +<li>warn - Use of deprecated APIs, poor use of API, almost errors, other runtime situations that are undesirable or unexpected, but not necessarily "wrong". Expect these to be immediately visible on a console, and MUST be internationalized.</li> <li style="list-style: none"> <br> </li> <li>info - Interesting runtime events (startup/shutdown). Expect these to be immediately visible on a console, so be conservative and keep to a minimum. These MUST be internationalized.</li> @@ -2666,7 +2674,7 @@ <li> <h3>Primary Rule: Only Catch An Exception If You Know What To Do With It</h3> </li> -<li style="list-style: none">If code catches an exception, it should know what to do with it at that point in the program. Any exception to this rule must be documented with a GOOD reason. Code reviewers are invited to put on their vulture beaks and peck away... <p>There are a few corrollaries to this rule.</p> +<li style="list-style: none">If code catches an exception, it should know what to do with it at that point in the program. Any exception to this rule must be documented with a GOOD reason. Code reviewers are invited to put on their vulture beaks and peck away... <p>There are a few corollaries to this rule.</p> <ul> <li> <h4>Handle Specific Exceptions in Inner Code</h4> @@ -2906,7 +2914,7 @@ <tt>java org.apache.axis.wsdl.Wsdl2java -t -s SequenceTest.wsdl</tt> </p> <ol> -<li>The -t option causes the emitter to generate a *TestCase.java file that hooks into the test harness. This file is operational without any additional changes. Copy the *TestCase.java file into the same directory as your wsdl file. (Ideally only the Java files that are changed need to be in your directory. So this file is not needed, but please make sure to modify your <wsdl2java ...> clause (described below) to emit a testcase.</li> +<li>The -t option causes the emitter to generate a *TestCase.java file that hooks into the test harness. This file is operational without any additional changes. Copy the *TestCase.java file into the same directory as your wsdl file. (Ideally only the Java files that are changed need to be in your directory.) So this file is not needed, but please make sure to modify your <wsdl2java ...> clause (described below) to emit a testcase.</li> <li>The -s option causes the emitter to generate a *SOAPBindingImpl.java file. The Java file contains empty methods for the service. You probably want to fill them in with your own logic. Copy the *SOAPBindingImpl.java file into the same directory as your wsdl file. (If no changes are needed in the Java file, you don't need to save it. But you will need to make sure that your <wsdl2java ...> clause generates a skeleton).</li> <li>Remove all of the Java files that don't require modification. So you should have three files in your directory (wsdl file, *TestCase.java, and *SOAPBindingImpl.java). My sequence test has an another file due to some additional logic that I needed.</li> </ol> @@ -2961,7 +2969,7 @@ </div> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>If you are debugging code that is running as a web application using a web application server (such as Tomcat) then you may also use the SOAP Monitor utility to view the SOAP request and response messages.<br> Start up the SOAP monitor utility by loading the SOAP monitor applet in your web browser window:</p> <pre class="code">http://localhost:<port>/axis/SOAPMonitor</pre> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>. As you run your tests, the SOAP messages should appear in the SOAP monitor window.</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>As you run your tests, the SOAP messages should appear in the SOAP monitor window.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <span class="codefrag">SOAP Monitor</span> is described in more detail in the <a href="#user-guide.html#soapmon">Axis User's Guide</a>.</p> <div class="h5"> @@ -3041,7 +3049,7 @@ <li>Each test or group of related tests should have its own directory in the <tt>xml-axis/java/test</tt> directory</li> </ul> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> -<br> One way to build a test is to "cut and paste" and existing tests, and then modify the test to suit your needs. This approach is becoming more complicated as the different kinds of tests grow.</p> +<br> One way to build a test is to "cut and paste" the existing tests, and then modify the test to suit your needs. This approach is becoming more complicated as the different kinds of tests grow.</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>A good "non-wsdl" test for reference is test/saaj.</p> <div class="h5"> <h5>Test Structure</h5> @@ -3364,7 +3372,7 @@ <span class="codefrag">EngineCongfiguration config = factory.getClientEngineConfig();</span> <br> <span class="codefrag">AxisClient = new AxisClient(config);</span> -<br> The details may vary (server versus client, whether other factories are involved, etc). Regardless, the point is that integration code is responsible for calling <span class="codefrag">EngineConfigurationFactoryFinder(someContext)</span> and ensuring that the results are handed to Axis. <span class="codefrag">someContext</span> is key to how the factory finder locates the appropariate implementation of EngineConfigurationFactory to be used, if any. <p>EngineConfigurationFactoryFinder works as follows:<br> </p> +<br> The details may vary (server versus client, whether other factories are involved, etc). Regardless, the point is that integration code is responsible for calling <span class="codefrag">EngineConfigurationFactoryFinder(someContext)</span> and ensuring that the results are handed to Axis. <span class="codefrag">someContext</span> is key to how the factory finder locates the appropriate implementation of EngineConfigurationFactory to be used, if any. <p>EngineConfigurationFactoryFinder works as follows:<br> </p> <ul> <li>Obtain a list of classes that implement <span class="codefrag">org.apache.axis.EngineConfigurationFactory</span>, in the following order: <ul> <li>The value of the system property <span class="codefrag">axis.EngineConfigFactory</span>.</li> @@ -3689,7 +3697,7 @@ <br> <tt>}</tt> </p> -<p>The GeneratorFactory interface defines a set of methods that the parser uses to get generators. There should be a generator for each of the WSDL constructs (message, portType, etc - note that these depend on the WSDL4J classes: javax.xml.Message, javax.xml.PortType, etc); a generator for schema types; and a generator for the WSDL Definition itself. This last generator is used to generate anything that doesn't fit into the previous categories</p> +<p>The GeneratorFactory interface defines a set of methods that the parser uses to get generators. There should be a generator for each of the WSDL constructs (message, portType, etc - note that these depend on the WSDL4J classes: javax.xml.Message, javax.xml.PortType, etc); a generator for schema types; and a generator for the WSDL Definition itself. This last generator is used to generate anything that doesn't fit into the previous categories.</p> <p>In addition to the getGeneratorMethods, the GeneratorFactory defines a generatorPass method which provides the factory implementation a chance to walk through the symbol table to do any preprocessing before the actual generation begins.</p> <p>Accessors for the base type mapping are also defined. These are used to translate QNames to base types in the given target mapping.<br> </p> </li> @@ -3996,7 +4004,7 @@ </p> <p>Let's go through this one method at a time.</p> <ul> -<li>constructor - this constructor adds the new option --song rum|work. (the abbreviated version of this option is "-g", rather an odd abbreviation, but "-s" is the abbreviation for --serverSide and "-S" is the abbreviation for --skeletonDeploy. Bummer. I just picked some other letter.</li> +<li>constructor - this constructor adds the new option --song rum|work. (the abbreviated version of this option is "-g", rather an odd abbreviation, but "-s" is the abbreviation for --serverSide and "-S" is the abbreviation for --skeletonDeploy. Bummer. I just picked some other letter.)</li> <li>createParser - we've got to provide a means by which the parent class can get our Parser extension.</li> <li>parseOption - this method processes our new option. If the given option isn't ours, just let super.parseOption do its work.</li> <li>main - this main is actually simpler than the first example's main. The first main had to add our generator to the list of generators. In this example, the factory already did that, so all that this main must do is instantiate itself and run itself.</li> @@ -4422,7 +4430,7 @@ <tt>Generate code for all elements, even unreferenced ones. By default, WSDL2Java only generates code for those elements in the WSDL file that are referenced.</tt> </p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> -<tt>A note about what it means to be referenced. We cannot simply say: start with the services, generate all bindings referenced by the service, generated all portTypes referenced by the referenced bindings, etc. What if we're generating code from a WSDL file that only contains portTypes, messages, and types? If WSDL2Java used service as an anchor, and there's no service in the file, then nothing will be generated. So the anchor is the lowest element that exists in the WSDL file in the order:</tt> +<tt>A note about what it means to be referenced. We cannot simply say: start with the services, generate all bindings referenced by the service, generate all portTypes referenced by the referenced bindings, etc. What if we're generating code from a WSDL file that only contains portTypes, messages, and types? If WSDL2Java used service as an anchor, and there's no service in the file, then nothing will be generated. So the anchor is the lowest element that exists in the WSDL file in the order:</tt> </p> <ol xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <li> @@ -4538,8 +4546,8 @@ -u, --use <argument> The use of items in the binding, either LITERAL or ENCODED -e, --extraClasses <argument> - A space or comma separated list of class names to be added tO - The type section. + A space or comma separated list of class names to be added to + the type section. Details: portType element name= <--portTypeName value> OR <class-of-portType name> binding element name= <--bindingName value> OR <--servicePortName value>Soap @@ -4571,11 +4579,11 @@ </p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <tt><strong>-P, --portTypeName <name></strong> -<br> Indicates the name to use use for the portType element. If not specified, the class-of-portType name is used.</tt> +<br> Indicates the name to use for the portType element. If not specified, the class-of-portType name is used.</tt> </p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <tt><strong>-b, --bindingName <name></strong> -<br> Indicates the name to use use for the binding element. If not specified, the value of the --servicePortName + "SoapBinding" is used.</tt> +<br> Indicates the name to use for the binding element. If not specified, the value of the --servicePortName + "SoapBinding" is used.</tt> </p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <tt><strong>-S, --serviceElementName <name></strong> @@ -4607,7 +4615,7 @@ </p> <ul xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <li> -<tt>All --- (default) Generates wsld containing both interface and implementation WSDL constructs.</tt> +<tt>All --- (default) Generates wsdl containing both interface and implementation WSDL constructs.</tt> </li> <li> <tt>Interface --- Generates a WSDL containing the interface constructs (no service element).</tt> @@ -4658,7 +4666,7 @@ </p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <tt><strong>-e, --extraClasses <argument></strong> -<br> Specify a space or comma seperated list of class names which should be included in the <strong>types</strong> section of the WSDL document. This is useful in the case where your service interface references a base class and you would like your WSDL to contain XML Schema type defintions for these other classes. The -extraClasses option can be specified duplicate times. Each specification results in the additional classes being added to the list.</tt> +<br> Specify a space or comma seperated list of class names which should be included in the <strong>types</strong> section of the WSDL document. This is useful in the case where your service interface references a base class and you would like your WSDL to contain XML Schema type defintions for these other classes. The --extraClasses option can be specified duplicate times. Each specification results in the additional classes being added to the list.</tt> </p> <div class="h5"> <h5>Deployment (WSDD) Reference</h5> @@ -5023,7 +5031,7 @@ <li> <a href="#http://www.sosnoski.com/presents/java-xml/axis/axis-monitor.html";>Enabling SOAPMonitor in Axis 1.0</a>.<br> Dennis Sosnoski on how to turn the SOAP monitor on and off, and use it to log your application.</li> <li> -<a href="http://macromedia.com/support/jrun/extend/using_web_services/";>Axis in JRrun</a> +<a href="http://macromedia.com/support/jrun/extend/using_web_services/";>Axis in JRun</a> <br> Macromedia authored coverage of using Axis from inside JRun.</li> <li> <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-eight/";>Ask the magic eight ball</a> @@ -5151,7 +5159,7 @@ </ol> <div class="h2"> -<h2>Axis requirements &amp; status</h2> +<h2>Axis requirements & status</h2> </div> <div class="h5"> <h5>Requirements</h5> @@ -6009,7 +6017,7 @@ <td>144b</td><td>Include a WSDL implementation of the SD layer <strong>[High]</strong> </td><td> <br> <br> -</td><td><strong>NYI</strong> - Lance &amp; HP contribution?<br> +</td><td><strong>NYI</strong> - Lance & HP contribution?<br> </td><td> <br> </td><td>X</td><td>X</td><td> @@ -6033,7 +6041,7 @@ <td>144d</td><td>Tools and/or run-time support for proxy generation from WSDL and/or WSDD</td><td> <br> <br> -</td><td><strong>NYI</strong> - Lance &amp; HP?<br> +</td><td><strong>NYI</strong> - Lance & HP?<br> </td><td> <br> </td><td> @@ -6266,7 +6274,7 @@ <tr class="a"> <td>174</td><td>Product-level testing</td><td> <br> -</td><td>getting there, with functional &amp; unit tests<br> +</td><td>getting there, with functional & unit tests<br> </td><td> <br> </td><td> @@ -6432,12 +6440,12 @@ </div> <div class="h2"> -<h2>Axis C++ 1.1.1 Available!</h2> +<h2>Axis C++ 1.2 Alpha is Available!</h2> </div> <div class="h5"> -<h5>Axis C++ 1.1.1 Available!</h5> +<h5>Axis C++ 1.2 Alpha is Available!</h5> </div> -<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>(May 07, 2004)</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>(June 15, 2004)</p> <p xmlns:cinclude="http://apache.org/cocoon/include/1.0";> <br> </p> @@ -6467,6 +6475,8 @@ <h5>Axis c++ Documentation</h5> </div> <br xmlns:cinclude="http://apache.org/cocoon/include/1.0";> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Documentation for building and running the latest source on windows can be found in the "Windows Developers Guide" in the CVS</p> +<p xmlns:cinclude="http://apache.org/cocoon/include/1.0";>Documentation for building and running the latest source on Linux can be found in the "Linux Installation Guide " and "Linux User Guide in the CVS</p> <div class="h5"> <h5>Linux Documentation</h5> </div> 1.4 +19 -19 ws-site/targets/axis/ref.pdf <<Binary file>> 1.14 +1 -1 ws-site/targets/axis/ref.html Index: ref.html =================================================================== RCS file: /home/cvs/ws-site/targets/axis/ref.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- ref.html 12 May 2004 09:49:45 -0000 1.13 +++ ref.html 17 Jun 2004 11:20:15 -0000 1.14 @@ -362,7 +362,7 @@ <b><a href="http://www.cvshome.org/docs/manual/cvs.html";>Version Management with CVS</a></b> -<br>Written by Per Cederqvist at al, this is the main manual for CVS. It +<br>Written by Per Cederqvist et al, this is the main manual for CVS. It provides details on all documented CVS features. </p>
