Google Git
Sign in
apache / axis-axis1-java / c07d27c2476597f249055e05820a28af042fba60 / . / docs / developers-guide.html
blob: 45e8f5604f7f2241d3d767c43efd4943c44a4ac8 [file] [log] [blame]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Axis Developer's Guide</title>
<link href="axis.css" rel=stylesheet type=text/css>
</head>
<body text="#000000" bgcolor="#FFFFFF">
<center>
<h1>
<img SRC="images/axis.jpg" height=96 width=176></h1></center>
<h1>
Axis Developer's Guide</h1>
<i>1.2 Version</i>
<br><i>Feedback: <a href="mailto:axis-dev@ws.apache.org">axis-dev@ws.apache.org</a></i>
<h3>
Table of Contents</h3>
<a href="#Introduction">Introduction</a>
<br><a href="#General Guidelines">General Guidelines</a>
<br><a href="#Development Environment">Development Environment</a>
<br><a href="#Pluggable-Components">Pluggable-Components</a>
<br>&nbsp;&nbsp;&nbsp;<a href="#Discovery">Discovery</a>
<br>&nbsp;&nbsp;&nbsp;<a href="#Logging/Tracing">Logging/Tracing</a>
<br>&nbsp;&nbsp;&nbsp;<a href="#Axis Servlet Query String Plug-ins">Axis Servlet Query String Plug-ins</a>
<br><a href="#Configuration Properties">Configuration Properties</a>
<br><a href="#Exception Handling">Exception Handling</a>
<br><a href="#Compile And Run">Compile and Run</a>
<br><a href="#Internationalization">Internationalization</a>
<br>&nbsp;&nbsp;&nbsp;<a href="#Extending Message Files">Extending Message Files</a>
<br><a href="#Adding Testcases">Adding Testcases</a>
<br><a href="#TestStructure">Test and Samples Structure</a>
<br><a href="#CodeChecks">Adding Source Code Checks</a>
<br><a href="#JUnit">JUnit and Axis</a>
<br><a href="#Debugging">Debugging</a>
<br><a href="#TCK">Running the JAX-RPC Compatibility Tests</a>
<br>&nbsp;
<h2>
<a NAME="Introduction"></a>Introduction</h2>
This guide is a collection of topics related to developing code for Axis.
<h2>
<a NAME="General Guidelines"></a>General Guidelines</h2>
<ul>
<li>
Axis specific information (cvs repository access, mailing list info, etc.)
can be found on the <a href="http://ws.apache.org/axis/index.html">Axis
Home Page</a>.</li>
<li>
Axis uses the <a href="http://jakarta.apache.org/site/guidelines.html">Jakarta
Project Guidelines.</a></li>
<li>
Code changes should comply with <a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">"Code
Conventions for the Java Programming Language"</a></li>
<li>
When fixing a <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Axis&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">
"Axis Bugzilla Bug"</a> include the href of the
bug in the cvs commit message.</li>
<li>
Incompatible changes to
<a href="user-guide.html#published interfaces">published Axis interfaces</a>
should be avoided where possible.
When changes are necessary, for example to maintain or improve the overall
modularity of Axis, the
impact on users must be considered and, preferably, documented.</li>
<li>
If you are making a big change that may affect interoperability, please
run the <a href="http://xml.apache.org/~rubys/echotest.pl">echotest2 round 2 interop test</a> to ensure that your change does not result in any new interop failures. You will also need the <a href="http://xml.apache.org/~rubys/client_deploy.wsdd">client_deploy.wsdd</a>. Here are the <a href="http://xml.apache.org/~rubys/ApacheClientInterop.html">nightly interop test results</a>.
</ul>
<h2>
<a NAME="Development Environment"></a>Development Environment</h2>
The following packages are required for axis development:
<ul>
<li>
<a href="http://jakarta.apache.org/ant/index.html">ant </a>- Java based build tool. <B>Please Note: Version 1.5 OR HIGHER is required</B></li>
<li>
<a href="http://www.junit.org">junit</a> - testing package</li>
<li>
<a href="http://xml.apache.org/dist/xerces-j">xerces</a> - xml processor</li>
<li>
Install Java 1.3.1 JDK (or later).</li>
</ul>
<p><br>The Axis jar files are built in the <tt>xml-axis/java/build/lib</tt>
directory.&nbsp;&nbsp; Here is an example CLASSPATH, which I use when developing
code:
<blockquote>
<blockquote><tt><font color="#009900">D:\\xerces\\xerces-1_4_2\\xerces.jar</font></tt>
<br><tt><font color="#009900">G:\\junit3.7\\junit.jar</font></tt>
<br><tt><font color="#009900">G:\\xml-axis\\java\\build\\lib\\commons-discovery.jar</font></tt>
<br><tt><font color="#009900">G:\\xml-axis\\java\\build\\lib\\commons-logging.jar</font></tt>
<br><tt><font color="#009900">G:\\xml-axis\\java\\build\\lib\\wsdl4j.jar</font></tt>
<br><tt><font color="#009900">G:\\xml-axis\\java\\build\\lib\\axis.jar</font></tt>
<br><tt><font color="#009900">G:\\xml-axis\\java\\build\\lib\\log4j-1.2.8.jar</font></tt>
<br><tt><font color="#009900">G:\\xml-axis\\java\\build\\classes</font></tt></blockquote>
</blockquote>
If you access the internet via a proxy server, you'll need to set an environment
variable so that the Axis tests do the same. Set ANT_OPTS to, for example:
<blockquote>
<blockquote><tt><font color="#009900">-Dhttp.proxyHost=proxy.somewhere.com
-Dhttp.proxyPort=80 -Dhttp.nonProxyHosts="localhost"</font></tt></blockquote>
</blockquote>
<h2>
<a NAME="Pluggable-Components"></a>Pluggable-Components</h2>
The <a href="architecture-guide.html">Axis Architecture Guide</a>
explains the requirements for pluggable components.
<h3>
<a NAME="Discovery"></a>Discovery</h3>
An Axis-specific component factory should be created of the form:
<ol>
org.apache.axis.components.&lt;componentType>.&lt;factoryClassName>
</ol>
For example, <code>org.apache.axis.components.logger.LogFactory</code> is the factory,
or discovery mechanism, for the logger component/service.
<p>
The <code>org.apache.axis.components.image</code> package demonstrates
both a factory, and supporting classes for different image tools used
by Axis. This is representative of a pluggable component that uses
external tooling, isolating it behind a 'thin' wrapper to Axis that
provides only a limited interface to meet Axis minimal requirements.
This allows future designers
and implementors to gain an explicit understanding of the Axis's
specific requirements on these tools.
<h3>
<a NAME="Logging/Tracing"></a>Logging/Tracing</h3>
Axis logging and tracing is based on the Logging component of the
<a href="http://jakarta.apache.org/commons/index.html">Jakarta Commons</a>
project, or the Jakarta Commons Logging (JCL) SPI.
The JCL provides a Log interface with thin-wrapper implementations for
other logging tools, including
<a href="http://jakarta.apache.org/log4j/docs/index.html">Log4J</a>,
<a href="http://jakarta.apache.org/avalon/logkit/index.html">Avalon LogKit</a>,
and
<a>JDK 1.4</a>.
The interface maps closely to Log4J and LogKit.
<h4>Using the Logger SPI</h4>
<p>
To use the JCL SPI from a Java class,
include the following import statements:
<ul>
<code>
import org.apache.commons.logging.Log;
<br>
import org.apache.axis.components.logger.LogFactory;
<br>&nbsp;
</code>
</ul>
For each class definition, declare and initialize a
<code>log</code> attribute as follows:
<ul>
<code>
public class CLASS
<br>{
<br>&nbsp;&nbsp;&nbsp;private static Log log = LogFactory.getLog(CLASS.class);
<br>&nbsp;&nbsp;&nbsp;...
<br>&nbsp;
</code>
</ul>
<p>
Messages are logged to a <i>logger</i>, such as <code>log</code>
by invoking a method corresponding to <i>priority</i>:
The <code>Log</code> interface defines the following methods for use
in writing log/trace messages to the log:
<ul>
<code>
log.fatal(Object message);
<br>log.fatal(Object message, Throwable t);
<br>log.error(Object message);
<br>log.error(Object message, Throwable t);
<br>log.warn(Object message);
<br>log.warn(Object message, Throwable t);
<br>log.info(Object message);
<br>log.info(Object message, Throwable t);
<br>log.debug(Object message);
<br>log.debug(Object message, Throwable t);
<br>log.trace(Object message);
<br>log.trace(Object message, Throwable t);
</code>
</ul>
While semantics for these methods are ultimately
defined by the implementation of the Log interface,
it is expected that the severity of messages is ordered
as shown in the above list.
<p>
In addition to the logging methods, the following are provided:
<ul>
<code>
log.isFatalEnabled();
<br>log.isErrorEnabled();
<br>log.isWarnEnabled();
<br>log.isInfoEnabled();
<br>log.isDebugEnabled();
<br>log.isTraceEnabled();
</code>
</ul>
These are typically used to guard code that
only needs to execute in support of logging,
and that introduces undesirable runtime overhead
in the general case (logging disabled).
<h4>Guidelines</h4>
<h5>Message Priorities</h5>
It is important to ensure that log message are
appropriate in content and severity.
The following guidelines are suggested:
<ul>
<li>fatal - Severe errors that cause the Axis server to terminate prematurely.
Expect these to be immediately visible on a console,
and MUST be internationalized.</li>
<br>&nbsp;
<li>error - Other runtime errors or unexpected conditions.
Expect these to be immediately visible on a console,
and MUST be internationalized.</li>
<br>&nbsp;
<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>
<br>&nbsp;
<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>
<br>&nbsp;
<li>debug - detailed information on flow of through the system.
Expect these to be written to logs only.
These NEED NOT be internationalized, but it never hurts...</li>
<br>&nbsp;
<li>trace - more detailed information.
Expect these to be written to logs only.
These NEED NOT be internationalized, but it never hurts...</li>
</ul>
<h4><a NAME="Configuring the Logger">Configuring the Logger</a></h4>
The Jakarta Commons Logging (JCL) SPI
can be configured to use different logging toolkits.
To configure which logger is used by the JCL, see the
<a href="integration-guide.html">Axis System Integration Guide</a>.
<p>
Configuration of the behavior of the JCL ultimately depends upon the
logging toolkit being used.
The JCL SPI (and hence Axis) uses
<a href="http://jakarta.apache.org/log4j/docs/index.html">Log4J</a>
by default if it is available (in the CLASSPATH).
<h5>Log4J</h5>
As
<a href="http://jakarta.apache.org/log4j/docs/index.html">Log4J</a>
is the prefered/default logger for Axis,
a <i>few</i> details are presented herein to get the developer going.
<p>
Configure Log4J using system properties and/or a properties file:
<ul>
<li><strong>log4j.configuration=<i>log4j.properties</i></strong>
<p>
Use this system property to specify the name of a Log4J configuration file.
If not specified, the default configuration file is <i>log4j.properties</i>.
A <i>log4j.properties</i> file is provided in <code>axis.jar</code>.
<p>This properties file can sometimes be overridden by placing a file of
the same name so as to appear before <code>axis.jar</code> in the CLASSPATH.
However, the precise behaviour depends on the classloader that is in use
at the time, so we don't recommend this technique.
<p>
A safe way of overriding the properties file is to replace it in axis.jar.
However, this isn't very convenient, especially if you want to tweak the
properties during a debug session to filter out unwanted log entries.
A more convenient alternative is to use an absolute file path to specify
the properties file. This will even ignore web app's and their classloaders.
So, for example on Linux, you could specify the system property:
<pre>
log4j.configuration=file:/home/fred/log4j.props
</pre>
</li>
<li><strong>log4j.debug</strong>
A good way of telling where log4j is getting its configuration from is to
set this system property and look at the messages on standard output.
<br>&nbsp;
</li>
<li><strong>log4j.rootCategory=<i>priority</i> [, <i>appender</i>]*</strong>
Set the default (root) logger priority.
<br>&nbsp;
</li>
<li><strong>log4j.logger.<i>logger.name</i>=<i>priority</i></strong>
Set the priority for the named logger
and all loggers hierarchically lower than, or below, the
named logger.
<i>logger.name</i> corresponds to the parameter of
<code>LogFactory.getLog(<i>logger.name</i>)</code>,
used to create the logger instance. Priorities are:
<code>DEBUG</code>,
<code>INFO</code>,
<code>WARN</code>,
<code>ERROR</code>,
or <code>FATAL</code>.
<p>
Log4J understands hierarchical names,
enabling control by package or high-level qualifiers:
<code>log4j.logger.org.apache.axis.encoding=DEBUG</code>
will enable debug messages for all classes in both
<code>org.apache.axis.encoding</code>
and
<code>org.apache.axis.encoding.ser</code>.
Likewise, setting
<code>log4j.logger.org.apache.axis=DEBUG</code>
will enable debug message for all Axis classes,
but not for other Jakarta projects.
<p>
A combination of settings will enable you to see the log events that
you are interested in and omit the others.
For example, the combination:
<pre>
log4j.logger.org.apache.axis=DEBUG
log4j.logger.org.apache.axis.encoding=INFO
log4j.logger.org.apache.axis.utils=INFO
log4j.logger.org.apache.axis.message=INFO
</pre>
cuts down the number of a log entries produced by a single request to
a manageable number.
<br>&nbsp;
</li>
<li><strong>log4j.appender.<i>appender</i>.Threshold=<i>priority</i></strong>
Log4J <i>appenders</i> correspond to different output devices:
console, files, sockets, and others.
If appender's <i>threshold</i>
is less than or equal to the message priority then
the message is written by that appender.
This allows different levels of detail to be appear
at different log destinations.
<p>
For example: one can capture DEBUG (and higher) level information in a logfile,
while limiting console output to INFO (and higher).
</li>
</ul>
<h3>
<a name="Axis Servlet Query String Plug-ins">Axis Servlet Query String Plug-ins</h3>
Any servlet that is derived from the <code>org.apache.axis.transport.http.AxisServlet</code> class
supports a number of standard query strings (<i>?list</i>, <i>?method</i>, and <i>?wsdl</i>) that
provide information from or perform operations on a web service (for instance, <i>?method</i> is
used to invoke a method on a web service and <i>?wsdl</i> is used to retrieve the WSDL document for
a web service). Axis servlets are not limited to these three query strings and developers may
create their own &quot;plug-ins&quot; by implementing the <code>org.apache.axis.transport.http.QSHandler</code>
interface. There is one method in this interface that must be implemented, with the following signature:
<pre>
public void invoke (MessageContext msgContext) throws AxisFault;
</pre>
The <code>org.apache.axis.MessageContext</code> instance provides the developer with a number of useful
objects (such as the Axis engine instance, and HTTP servlet objects) that are accessible by its
<code>getProperty</code> method. The following constants can be used to retrieve various objects provided
by the Axis servlet invoking the query string plug-in:
<ul>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_NAME</strong><br>
A <code>String</code> containing the name of the query string plug-in. For instance, if the query string <i>?wsdl</i> is
provided, the name of the plugin is <i>wsdl</i>.
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_SERVICE_NAME</strong><br>
A <code>String</code> containing the name of the Axis servlet that inovked the query string plug-in.
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_IS_DEVELOPMENT</strong><br>
A <code>Boolean</code> containing <code>true</code> if this version of Axis is considered to be in development
mode, <code>false</code> otherwise.
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_ENABLE_LIST</strong><br>
A <code>Boolean</code> containing <code>true</code> if listing of the Axis server configuration is allowed,
<code>false</code> otherwise.
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_ENGINE</strong><br>
A <code>org.apache.axis.server.AxisServer</code> object containing the engine for the Axis server.
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.MC_HTTP_SERVLETREQUEST</strong><br>
The <code>javax.servlet.http.HttpServletRequest</code> object from the Axis servlet that invoked the
query string plug-in
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.MC_HTTP_SERVLETRESPONSE</strong><br>
The <code>javax.servlet.http.HttpServletResponse</code> object from the Axis servlet that invoked the
query string plug-in
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_WRITER</strong><br>
The <code>java.io.PrintWriter</code> object from the Axis servlet that invoked the
query string plug-in
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_LOG</strong><br>
The <code>org.apache.commons.logging.Log</code> object from the Axis servlet that invoked the query
string plug-in, which is used to log messages.
<br><br>
</li>
<li><strong>org.apache.axis.transport.http.HTTPConstants.PLUGIN_EXCEPTION_LOG</strong><br>
The <code>org.apache.commons.logging.Log</code> object from the Axis servlet that invoked the query
string plug-in, which is used to log exceptions.
<br><br>
</li>
</ul>
Query string plug-in development is much like normal servlet development since the same basic
information and methods of output are available to the developer. Below is an example query string
plug-in which simply displays the value of the system clock (<code>import</code> statements have been
omitted for brevity):
<pre>
public class QSClockHandler implements QSHandler {
public void invoke (MessageContext msgContext) throws AxisFault {
PrintWriter out = (PrintWriter) msgContext.getProperty (HTTPConstants.PLUGIN_WRITER);
HttpServletResponse response = (HttpServletResponse) msgContext.getProperty (HTTPConstants.MC_HTTP_SERVLETRESPONSE);
response.setContentType ("text/html");
out.println ("&lt;HTML&gt;&lt;BODY&gt;&lt;H1&gt;" + System.currentTimeMillis() + "&lt;/H1&gt;&lt;/BODY&gt;&lt;/HTML&gt;");
}
}
</pre>
Once a query string plug-in class has been created, the Axis server must be set up to recognize the
query string which invokes it. See the section <a href="reference.html#Deployment">Deployment (WSDD) Reference</a> in the
<a href="reference.html">Axis Reference Guide</a> for information on how the HTTP transport section of the Axis server configuration
file must be set up.
<h2>
<a NAME="Configuration Properties"></a>Configuration Properties</h2>
Axis is in the process of moving away from using system properties
as the primary point of internal configuration.
Avoid calling <code>System.getProperty()</code>,
and instead call <code>AxisProperties.getProperty</code>.
<code>AxisProperties.getProperty</code> will
call <code>System.getProperty</code>, and will (eventually)
query other sources of configuration information.
<p>
Using this central point of access will allow the
global configuration system to be redesigned
to better support multiple Axis engines in a
single JVM.
<h2>
<a NAME="Exception Handling"></a>Exception Handling</h2>
Guidelines for Axis exception handling are based on best-practices
for exception handling.
While there are details specific to Axis in these guidelines,
they apply in principle to any project;
they are included here for two reasons.
First, because they are not listed elsewhere in the
Apache/Jakarta guidelines (or haven't been found).
Second, because adherence to these guidelines is
considered crucial to enterprise ready middleware.
<p>
These guidelines are fundamentally independent of programming language.
They are based on experience, but proper credit must be given to
<i>More Effective C++</i>, by Scott Meyers,
for opening the eyes of the innocent(?) many years ago.
<p>
Finally, these are guidelines.
There will always be exceptions to these guidelines,
in which case all that can be asked (as per these guidelines)
is that they be logged in the form of comments in the code.
<p>
<ul>
<li><h3>Primary Rule: Only Catch An Exception If You Know What To Do With It</h3></li>
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>
<ul>
<li><h4>Handle Specific Exceptions in Inner Code</h4></li>
Inner code is code <i>deep</i> within the program.
Such code should catch specific exceptions,
or categories of exceptions (parents in exception hierarchies),
<u>if and only if</u> the exception can be resolved
and normal flow restored to the code.
Note that behaviour of this sort may be significantly
different between non-interactive code versus an interactive tool.
<p>
<li><h4>Catch All Exceptions in Outermost Flow of Control</h4></li>
Ultimately, all exceptions must be dealt with at one level or another.
For command-line tools, this means the <code>main</code>
method or program.
For a middleware component, this is the entry point(s) into the component.
For Axis this is <code>AxisServlet</code> or equivalent.
<p>
After catching specific exceptions which can be resolved internally,
the outermost code must ensure that all internally generated exceptions
are caught and handled.
While there is generally not much that can be done,
at a minimum the code should <u>log the exception</u>.
In addition to logging, the Axis Server wraps all such exceptions
in AxisFaults and returns them
to the client code.
<p>
This may seem contrary to the primary rule,
but in fact we are claiming that Axis does know
what to do with this type of exception:
exit gracefully.
</ul>
<p>
<li><h3>Catching and Logging Exceptions</h3></li>
When an Exception is going to cross a component boundry
(client/server, or system/business logic),
the exception must be caught and logged by the
throwing component.
It may then be rethrown, or wrapped, as described below.
<p>
When in doubt, log the exception.
<p>
<ul>
<li><h4>Catch and Throw</h4></li>
If an exception is caught and rethrown (unresolved),
logging of the exception is at the discretion of the coder and reviewers.
If any comments are logged, the exception should also be logged.
<p>
When in doubt, log the exception and any related local information
that can help to identify the complete context of the exception.
<p>
Log the exception as an <i>error</i> (<code>log.error()</code>)
if it is known to be an unresolved or unresolvable error,
otherwise log it at the <i>informative</i> level (<code>log.info()</code>).
<p>
<li><h4>Catch and Wrap</h4></li>
When exception <code>e</code> is caught and wrapped
by a new exception <code>w</code>,
log exception <code>e</code> before throwing <code>w</code>.
<p>
Log the exception as an <i>error</i> (<code>log.error()</code>)
if it is known to be an unresolved or unresolvable error,
otherwise log it at the <i>informative</i> level (<code>log.info()</code>).
<p>
<li><h4>Catch and Resolve</h4></li>
When exception <code>e</code> is caught and resolved,
logging of the exception is at the discretion of the coder and reviewers.
If any comments are logged, the exception should also be logged (<code>log.info()</code>).
Issues that must be balanced are performance and problem resolvability.
<p>
Note that in many cases, ignoring the exception may be appropriate.
<p>
</ul>
<li><h3>Respect Component Boundries</h3></li>
There are multiple aspects of this guideline.
On one hand, this means that business logic
should be isolated from system logic.
On the other hand, this means that
client's should have limited exposure/visibility to
implementation details of a server - particularly
when the server is published to outside parties.
This implies a well designed server interface.
<p>
<ul>
<li><h4>Isolate System Logic from Business Logic</h4></li>
Exceptions generated by the Axis runtime
should be handled, where possible,
within the Axis runtime.
In the worst case the details of an exception are to be logged
by the Axis runtime,
and a generally descriptive Exception raised to the Business Logic.
<p>
Exceptions raised in the business logic
(this includes the server and Axis handlers)
must be delivered to the client code.
<p>
<li><h4>Protect System Code from User Code</h4></li>
Protect the Axis runtime from uncontrolled user business logic.
For Axis, this means that dynamically configurable
<code>handlers</code>, <code>providers</code> and other
user controllable hook-points must be guarded
by <code>catch(Exception ...)</code>.
Exceptions generated by user code and caught by system code should be:
<ul>
<li>Logged, and</li>
<li>Delivered to the client program</li>
</ul>
<p>
<li><h4>Isolate Visibility into Server from Client</h4></li>
Specific exceptions should be logged at the server side,
and a more general exception thrown to the client.
This prevents clues as to the nature of the server
(such as handlers, providers, etc)
from being revealed to client code.
The Axis component boundries that should be respected are:
<ul>
<li>Client Code <--> AxisClient</li>
<li>AxisClient <--> AxisServlet (AxisServer/AxisEngine)</li>
<li>AxisServer/AxisEngine <--> Web Service</li>
</ul>
</ul>
<p>
<li><h3>Throwing Exceptions in Constructors</h3></li>
Before throwing an exception in a constructor,
ensure that any resources owned by the object are cleaned up.
For objects holding resources,
this requires catching <u>all</u> exceptions thrown by methods called
within the constructor, cleaning up, and rethrowing the exceptions.
<p>
</ul>
</ul>
<h2>
<a NAME="Compile And Run"></a>Compile and Run</h2>
The <tt>xml-axis/java/build.xml</tt> file is the primary 'make' file used
by ant to build the application and run the tests.&nbsp; The <tt>build.xml</tt>
file defines ant build <i>targets</i>.&nbsp; Read the build.xml file for
more information.&nbsp; Here are some of the useful targets:
<br>&nbsp;
<ul>
<li>
<tt>compile -> compiles the source and creates xml-axis/java/build/lib/axis.jar</tt></li>
<li>
<tt>javadocs -> creates the javadocs in xml-axis/java/build/javadocs</tt></li>
<li>
<tt>functional-tests -> compiles and runs the functional tests</tt></li>
<li>
<tt>all-tests -> compiles and runs all of the tests</tt></li>
<br>&nbsp;</ul>
To compile the source code:
<blockquote><tt>cd xml-axis/java</tt>
<br><tt>ant compile</tt></blockquote>
To run the tests:
<blockquote><tt>cd xml-axis/java</tt>
<br><tt>ant functional-tests</tt></blockquote>
<b>Note: </b>these tests start a server on port 8080. If this clashes with
the port used by your web application server (such as Tomcat), you'll need
to change one of the ports or stop your web application server when running
the tests.
<p><b>Please run <tt><font color="#009900">ant functional-tests</font></tt>
and <tt><font color="#009900">ant all-tests</font></tt> before checking
in new code.</b>
<h2>
<a NAME="Internationalization"></a>Internationalization</h2>
If you make changes to the source code that results in the generation of
text (error messages or debug information), you must follow the following
guidelines to ensure that your text is properly translated.
<h3>
<a NAME="Developer Guidelines"></a>Developer Guidelines</h3>
<ol>
<li>
Your text string should be added as a property to the resource.properties
file (xml-axis/java/src/org/apache/axis/i18n/resource.properties).&nbsp;
Note that some of the utility applications (i.e. tcpmon) have their own
resource property files (tcpmon.properties).
</li>
<br>&nbsp;
<li>
The resource.properties file contains translation and usage instructions.&nbsp;
Entries in a message resource file are of the form
<font color="#009900">&lt;key&gt;=&lt;message&gt;</font>.
Here is an example message:</li>
<p>
<p><font color="#009900">sample00=My name is {0}, and my title is {1}.</font>
<br>&nbsp;
<ol>
<li>
sample00 is the key that the code will use to access this message.</li>
<li>
The text after the = is the message text.</li>
<li>
The <font color="#009900">{<i>number</i>}</font> syntax defines the location
for inserts.</li>
<p>
</ol>
<li>
The code should use the
static method org.apache.axis.i18n.Messages.getMessage
to obtain the text and add inserts.&nbsp; Here is an example usage:</li>
<p>
<p><font color="#009900">Messages.getMessage("sample00", "Rich Scheuerle",
"Software Developer");</font>
<br>&nbsp;
<li>
<font color="#000000">All keys in the properties file should use the syntax
&lt;string>&lt;2-digit-suffix>.</font></li>
<br>&nbsp;
<ol>
<li>
<font color="#000000"><b>Never change the message text in the properties
file. </b>The message may be used in multiple places in the code.&nbsp;
Plus translation is only done on new keys.</font></li>
<br>&nbsp;
<li>
<font color="#000000">If a code change requires a change to a message,
create a new entry with an incremented 2-digit suffix.</font></li>
<br>&nbsp;
<li>
<font color="#000000">All new entries should be placed at the bottom of
the file to ease translation.</font></li>
<br>&nbsp;
<li>
<font color="#000000">We may occasionally want to trim the properties file of old data, but this should only be done on major releases. </font></li>
</ol>
</ol>
<h4>
<a NAME="Example"></a>Example</h4>
Consider the following statement:
<p><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
if ( operationName == null )</code>
<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
throw new AxisFault( "No operation name specified" );</code>
<p>
We will add an entry into
org/apache/axis/i18n/resource.properties:
<p><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;noOperation=No operation name specified.</code>
<p>And change the code to read:
<p><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
if ( operationName == null )</code>
<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
throw new AxisFault(Messages.getMessage("noOperation"));</code>
<h3>
<a NAME="Interface"></a>Interface</h3>
Axis uses the standard Java internationalization class
<code>java.util.ResourceBundle</code>
to access property files and message strings,
and uses <code>java.text.MessageFormat</code>
to format the strings using variables.
Axis provides a single class <code>org.apache.axis.i18n.Messages</code>
that manages both ResourceBundle and MessageFormat classes.
Messages methods are:
<p><code>public static java.util.ResourceBundle getResourceBundle();</code>
<p><code>public static String getMessage(String key) throws java.util.MissingResourceException;</code>
<p><code>public static String getMessage(String key, String var) throws java.util.MissingResourceException;</code>
<p><code>public static String getMessage(String key, String var1, String var2) throws java.util.MissingResourceException;</code>
<p><code>public static String getMessage(String key, String[] vars) throws java.util.MissingResourceException;</code>
<p>Axis programmers can work with the resource bundle directly via a call
to <code>Messages.getResourceBundle()</code>,
but the <code>getMessage()</code>
methods should be used instead for two reasons:
<ol>
<li>
It's a shortcut. It is cleaner to call</li>
<ol><code>Messages.getMessage("myMsg00");</code></ol>
than
<ol><code>Messages.getResourceBundle().getString("myMsg00");</code></ol>
<br>
<li>
The <code>getMessage</code> methods enable messages with variables.</li>
</ol>
<h4>
The getMessage methods</h4>
If you have a message with no variables
<ol><code>myMsg00=This is a string.</code></ol>
then simply call
<ol><code>Messages.getMessage("myMsg00");</code></ol>
<p><br>If you have a message with variables, use the syntax
<font face="Courier New,Courier">"{X}"</font>
where <code>X</code> is
the number of the variable, starting at 0. For example:
<ol><code>myMsg00=My {0} is {1}.</code></ol>
then call:
<ol><code>Messages.getMessage("myMsg00","name", "Russell");</code></ol>
and the resulting string will be:&nbsp; "My name is Russell."
<p>You could also call the String array version of <font face="Courier New,Courier"><font size=-1>getMessage</font></font>:
<ol><code>Messages.getMessage("myMsg00", new String[] {"name", "Russell"});</code></ol>
<p><br>The String array version of <font face="Courier New,Courier"><font size=-1>getMessage</font></font>
is all that is necessary, but the vast majority of messages will have 0,
1 or 2 variables, so the other <font face="Courier New,Courier"><font size=-1>getMessage</font></font>
methods are provided as a convenience to avoid the complexity of the String
array version.
<p>Note that the <font face="Courier New,Courier"><font size=-1>getMessage</font></font>
methods throw <font face="Courier New,Courier"><font size=-1>MissingResourceException</font></font>
if the resource cannot be found.&nbsp; And ParseException if there are
more {X} entries than arguments.&nbsp; These exceptions are <font face="Courier New,Courier"><font size=-1>RuntimeException'</font></font>s,
so the caller doesn't have to explicitly catch them.
<p>The resource bundle properties file is org/apache/axis/i18n/resource.properties.
<h3>
<a NAME="Extending Message Files"></a>Extending Message Files</h3>
Generally,
within Axis all messages are placed in
org.apache.axis.i18n.resource.properties.
There are facilities for extending the messages without
modifying this file for integration or 3rd party extensions to Axis.
See the <a href="integration-guide.html#Extending Message Files"/>Integration Guide</a> for details.
<h2>
<a NAME="Adding Testcases"></a><font color="#000000">Adding Testcases</font></h2>
<P>See Also: <a href="#TestStructure">Test and Samples Structure</a></P>
<font color="#000000"><b>Editor's Note: </b>We need more effort to streamline
and simplify the addition of tests.&nbsp; We also need to think about categorizing
tests as the test bucket grows.</font>
<br>&nbsp;
<p><font color="#000000">If you make changes to Axis, please add a test
that uses your change.&nbsp; Why?</font>
<ul>
<li>
<font color="#000000">The test validates that your new code works.</font></li>
<li>
<font color="#000000">The test protects your change from bugs introduced
by future code changes.</font></li>
<li>
<font color="#000000">The test is an example to users of the features of
Axis.</font></li>
<li>
<font color="#000000">The test can be used as a starting point for new
development.</font></li>
</ul>
<p><br><font color="#000000">Some general principles:</font>
<ul>
<li>
<font color="#000000">Tests should be self-explanatory.</font></li>
<li>
<font color="#000000">Tests should not generate an abundance of output</font></li>
<li>
<font color="#000000">Tests should hook into the existing junit framework.</font></li>
<li>
<font color="#000000">Each test or group of related tests should have its
own directory in the <tt>xml-axis/java/test</tt> directory</font></li>
</ul>
<p><br><font color="#000000">One way to build a test is to "cut and paste"
and existing tests, and then modify the test to suit your needs.&nbsp;
This approach is becoming more complicated as the different kinds of tests
grow.</font>
<P>
A good "non-wsdl" test for reference is test/saaj.
</P>
<h4>
<font color="#000000">Creating a WSDL Test</font></h4>
<font color="#000000">Here are the steps that I used to create the <tt>sequence</tt>
test, which generates code from a wsdl file and runs a sequence validation
test:</font>
<br>&nbsp;
<ol>
<li>
<font color="#000000">Created a <tt>xml-axis/java/test/wsdl/sequence</tt>
directory.</font></li>
<br>
<li>
<font color="#000000">Created a <tt>SequenceTest.wsdl</tt> file defining
the webservice.</font></li>
<BR>
<li>
<font color="#000000">Ran the Wsdl2java emitter to create Java files:</font></li>
<p><tt><font color="#993366">java org.apache.axis.wsdl.Wsdl2java -t -s
SequenceTest.wsdl</font></tt>
<br>
<ol>
<li>
<font color="#000000">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.&nbsp; Copy the *TestCase.java file into the same
directory as your wsdl file.&nbsp; (Ideally only the Java files that are
changed need to be in your directory.&nbsp; So this file is not needed,
but please make sure to modify your &lt;wsdl2java ...> clause (described
below) to emit a testcase.</font></li>
<li>
<font color="#000000">The -s option causes the emitter to generate a *SOAPBindingImpl.java
file.&nbsp; The Java file contains empty methods for the service.&nbsp;
You probably want to fill them in with your own logic.&nbsp; Copy the *SOAPBindingImpl.java
file into the same directory as your wsdl file.&nbsp; (If no changes are
needed in the Java file, you don't need to save it.&nbsp; But you will
need to make sure that your &lt;wsdl2java ...> clause generates a skeleton).</font></li>
<li>
<font color="#000000">Remove all of the Java files that don't require modification.&nbsp;
So you should have three files in your directory (wsdl file, *TestCase.java,
and *SOAPBindingImpl.java).&nbsp; My sequence test has an another file
due to some additional logic that I needed.</font></li>
</ol>
<tt><font color="#993366"></font></tt>
<BR>
<li>
<font color="#000000">The <tt>test/wsdl/sequence/build.xml</tt> file
controls the building of this test.&nbsp; Locate the "compile" target.&nbsp;
Add a clause that runs the Wsdl2java code. I would recommend stealing something from the
test/wsdl/roundtrip/build.xml file (it does a LOT of wsdl2java and java2wsdl calls).
Here is the one for SequenceTest:</font></li>
<p><tt><font color="#663366">&nbsp;&nbsp;&nbsp; </font><font color="#993366">&lt;!--
Sequence Test --></font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp; &lt;wsdl2java url="${axis.home}/test/wsdl/sequence/SequenceTest.wsdl"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
output="${axis.home}/build/work"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
deployscope="session"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
skeleton="yes"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
messagecontext="no"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
noimports="no"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
verbose="no"</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
testcase="no"></font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;mapping namespace="urn:SequenceTest2" package="test.wsdl.sequence"/&gt;</font></tt>
<br><tt><font color="#993366">&nbsp;&nbsp;&nbsp; &lt;/wsdl2java></font></tt>
<br>
<li>
<font color="#000000">Enable the <font color="#993366">run</font><font color="#000000"> target in the new
build.xml file.</font> You need to choose from the execute-Component and the (soon to be introduced)
execute-Simple-Test target. These control HOW the test is invoked when run as a single component.
The <font color="#993366">execute-Component</font> sets up the tcp-server and http-server prior to running the test, as
well as handles deploying and services that may be needed. The <font color="#993366">execute-Simple-test</font>
simply invokes the raw test class file.<BR>
<BR>
<li>
<font color="#000000">Done.&nbsp; Run </font><tt><font color="#993366">ant
functional-tests</font><font color="#000000"> </font></tt><font color="#000000">to
verify.&nbsp; Check in your test.</font></li>
<br>&nbsp;</ol>
<h2><a NAME="TestStructure"></a>Test Structure</H2>
<a href="AxisTestRedesign.html">The Test and Samples Redesign Document is here</a><BR>
<P>
As of Axis 1.0, RC1, we have moved to a "componentized" test structure. Instead of having one high-level large
recursive function, there are smaller, simple "component" build.xml files in the leaf level of the test/** and
samples/** trees.</P>
<P>
These "component" files have a common layout. Their primary targets are:<BR>
<UL>
<LI>clean - reset the build destination(s)
<LI>compile - javac, wsdl2java, java2wsdl instructions
<LI>run - "executes" the test
</UL>
</P>
<P>A "sample" test xml file can be found in test/templateTest</P>
<h2>
<a NAME="CodeChecks"></a>Adding Source Code Checks</h2>
The Axis build performs certain automated checks of the files in the
source directory (java/src) to make sure certain conventions are
followed such as using internationalised strings when issuing messages.
<p>
If a convention can be reduced to a regular expression match,
it can be enforced at build time by updating
java/test/utils/TestSrcContent.java.
<p>
All that is necessary is to add a pattern to the static FileNameContentPattern
array.
Each pattern has three parameters:
<ol>
<li>a pattern that matches filenames that are to be checked,</li>
<li>a pattern to be searched for in the chosen files, and</li>
<li>a boolean indicating whether the pattern is to be allowed
(typically false indicating not allowed).</li>
</ol>
<p>
A reasonable summary of the regular expression notation is provided in
the <a href="http://jakarta.apache.org/oro/api/org/apache/oro/text/regex/package-summary.html">Jakarta ORO javadocs</a>.
<h2>
<a NAME="JUnit"></a>JUnit and Axis</h2>
<p>
You try to run some JUnit tests on an Axis client that invokes a web service,
and you always get this exception:
<pre>
java.lang.ExceptionInInitializerError
at org.apache.axis.client.Service.<init>(Service.java:108)
...
Caused by: org.apache.commons.logging.LogConfigurationException: ...
org.apache.commons.logging.impl.Jdk14Logger does not implement Log
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance
(LogFactoryImpl.java:555)
...
</pre>
<p>
Actually, the Jdk14Logger does implement Log. What you have is a JUnit classloading
issue. JUnit's graphical TestRunner has a feature where it will dynamically
reload modified classes every time the user presses the "Run" button. This way,
the user doesn't need to relaunch the TestRunner after every edit. For this,
JUnit uses its own classloader, junit.runner.TestCaseClassLoader. As of JUnit
3.8.1, confusion can arise between TestCaseClassLoader and the system class
loader as to which loader did or should load which classes.
<p>
There are two ways to avoid this problem.
<ul>
<li>Sure and simple fix. Turn off dynamic class reloading by running
junit.swingui.TestRunner with the -noloading argument.
</li>
<p>
<li>Finicky and fancy fix, only necessary if you want dynamic class reloading.
Tell TestCaseClassLoader to ignore certain packages and their sub-packages,
deferring them to the system classloader. You can do this using a file located
in junit.jar, junit/runner/excluded.properties. Its content appears as follows:
<pre>
#
# The list of excluded package paths for the TestCaseClassLoader
#
excluded.0=sun.*
excluded.1=com.sun.*
excluded.2=org.omg.*
excluded.3=javax.*
excluded.4=sunw.*
excluded.5=java.*
excluded.6=org.w3c.dom.*
excluded.7=org.xml.sax.*
excluded.8=net.jini.*
</pre></li>
</ul>
<p>
Copy this file, preserving the directory path, into another location, e.g.
deployDir. So the copied properties file's path will be
deployDir/junit/runner/excluded.properties. Add an extra entry to the end of
this file:
<pre>
excluded.9=org.apache.*
</pre>
<p>
Edit your classpath so that deployDir appears before junit.jar. This way, the
modified excluded.properties will be used, rather than the default. (Don't add
the path to excluded.properties itself to the classpath.)
<p>
This fix will prevent the commons-logging exception. However, other
classloading problems might still arise. For example:
<pre>
Dec 10, 2002 7:16:16 PM org.apache.axis.encoding.ser.BeanPropertyTarget set
SEVERE: Could not convert [Lfoo.bar.Child; to bean field 'childrenAsArray',
type [Lfoo.bar.Child;
Dec 10, 2002 7:16:16 PM org.apache.axis.client.Call invoke
SEVERE: Exception:
java.lang.IllegalArgumentException: argument type mismatch
at org.apache.axis.encoding.ser.BeanPropertyTarget.set
(BeanPropertyTarget.java:182)
at org.apache.axis.encoding.DeserializerImpl.valueComplete
(DeserializerImpl.java:284)
...
</pre>
<p>
In this case, you have no choice but to give up on dynamic class reloading and
use the -noloading argument.
<p>
One other heads-up about JUnit testing of an Axis web service. Suppose you have
run JUnit tests locally on the component that you want to expose as a web
service. You press the "Run" button to initiate a series of tests. Between each
test, all your data structures are re-initialized. Your tests produce a long
green bar. Good.
<p>
Suppose you now want to run JUnit tests on an Axis client that is connecting to
an application server running the Axis web application and with it your web
service. Between each test, JUnit will automatically re-initialize your client.
<p>
Your server-side data structures are a different matter. If you're checking
your server data at the end of each test (as you should be) and you run more
than one test at a time, the second and later tests will fail because they are
generating cumulative data on the Axis server based on preceding tests rather
than fresh data based only on the current one.
<p>
This means that, for each test, you must manually re-initialize your web
service. One way to accomplish this is to add to your web service interface a
re-initialize operation. Then have the client call that operation at the start
of each test.
<h2>
<a NAME="Debugging"></a>Debugging</h2>
<h4>Using <code>tcpmon</code> to Monitor Functional Tests.</h4>
<p>
Here is an easy way to monitor the messages while running
<code>functional-tests</code> (or <code>all-tests</code>).
<br>Start up tcpmon listening on 8080 and forwarding to a different port:
<blockquote><tt>java org.apache.axis.utils.tcpmon 8080 localhost 8011</tt></blockquote>
Run your tests, but use the forwarded port for the SimpleAxisServer, and
indicate that functional-tests should continue if a failure occurs.
<blockquote><tt>ant functional-tests -Dtest.functional.SimpleAxisPort=8011
-Dtest.functional.fail=no</tt></blockquote>
The SOAP messages for all of the tests should appear in the tcpmon window.
<p>
<code>tcpmon</code> is described in more detail in the
<a href="user-guide.html#tcpmon">Axis User's Guide</a>.
<h4>Using <code>SOAP Monitor</code> to Monitor Functional Tests.</h4>
<p>
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:
<blockquote><tt>http://localhost:&lt;port&gt;/axis/SOAPMonitor</tt></blockquote>.
As you run your tests, the SOAP messages should appear in the SOAP
monitor window.
<p>
<code>SOAP Monitor</code> is described in more detail in the
<a href="user-guide.html#soapmon">Axis User's Guide</a>.
<h4>Running a Single Functional Test</h4>
In one window start the server:
<br>
<blockquote><tt>java org.apache.axis.transport.http.SimpleAxisServer -p 8080</tt></blockquote>
In another window, first deploy the service you're testing:
<blockquote><tt>java org.apache.axis.client.AdminClient deploy.wsdd</tt></blockquote>
Then bring up the JUnit user interface with your test. For example, to run the the multithread test case:
<blockquote><tt>java junit.swingui.TestRunner -noloading test.wsdl.multithread.MultithreadTestCase</tt></blockquote>
<h4>Turning on Debug Output</h4>
This section is oriented to the Axis default logger: Log4J.
For additional information on Log4J, see the section
<a href="#Configuring the Logger">Configuring the Logger</a>.
<p>
<ul>
<li><h5>Overriding Log4J properties</h5></li>
The <code>log4j.properties</code> file
is packaged in <code>axis.jar</code> with reasonable
default settings.
Subsequent items presume changes to these settings.
There are multiple options open to the developer,
most of which involve
extracting <code>log4j.properties</code> from <code>axis.jar</code>
and modifying as appropriate.
<ul>
<p>
<li>
If you are building and executing <code>Java</code> programs from
a command line or script file,
include the JVM option
<code>-Dlog4j.configuration=<i>yourConfigFile</i></code>.
</li>
<p>
<li>
Set <code>CLASSPATH</code> such that
your version of <code>log4j.properties</code> appears
prior to <code>axis.jar</code> in the <code>CLASSPATH</code>.
</li>
<p>
<li>
If you are building and executing your programs using <code>ant</code>
(this includes building Axis and running it's tests),
set the environment variable <code>ANT_OPTS</code> to <code>-Dlog4j.configuration=<i>yourConfigFile</i></code>.
</li>
<p>
<li>
If you are building Axis, you can change <code>src/log4j.properties</code>
directly. Be sure NOT to commit your change(s).
</li>
</ul>
<br>
<li><h5>Turning on ALL DEBUG Output</h5></li>
<ul>
<li>
Set the <code>log4j.rootCategory</code> <i>priority</i> to
<code>DEBUG</code>.
</li>
<p>
<li>
Set the <i>priority</i> threshold for an appender to <code>DEBUG</code>
(The <code>log4j.properties</code> file in Axis defines two appenders:
<code>CONSOLE</code> and <code>LOGFILE</code>).
</li>
</ul>
<br>
<li><h5>Selective DEBUG Output</h5></li>
<ul>
<li>
Set the <code>log4j.rootCategory</code> <i>priority</i> to
<code>INFO</code> or higher.
</li>
<p>
<li>
Set the <code>log4j.logger.<i>logger.name</i></code> <i>priority</i> to
<code>DEBUG</code> for the loggers that you are interested in.
</li>
<p>
<li>
Set the <i>priority</i> threshold for an appender to <code>DEBUG</code>
(The <code>log4j.properties</code> file in Axis defines two appenders:
<code>CONSOLE</code> and <code>LOGFILE</code>).
</li>
<p>
<li>
If you are still seeing more than you want to see,
you will need to use other tools to extract the information
you are interested in from the log output.
Use appropriate key words in log messages
and use tools such as <code>grep</code> to
search for them in log messages.
</li>
</ul>
</ul>
<h4>Writing Temporary Output</h4>
Remember that Axis is targeted for use in a number
of open-source and other web applications,
and so it needs to be a good citizen.
Writing output using <code>System.out.println</code> or
<code>System.err.println</code>
should be avoided.
<p>
Developers may be tempted to use <code>System.out.println</code>
while debugging or analyzing a system.
If you choose to do this, you will need to disable the
<code>util/TestSrcContent</code> test,
which enforces avoidance of
<code>System.out.println</code> and <code>System.err.println</code>.
It follows that you will need to remove your statements
before checking the code back in.
<p>
As an alternative,
we strongly encourage you to
take a few moments and introduce debug statements:
<code>log.debug("reasonably terse and meaningful message")</code>.
If a debug message is useful for understanding a problem now,
it may be useful again in the future to you or a peer.
<h2>
<a NAME="TCK"></a>Running the JAX-RPC Compatibility Tests</h2>
As well as a specification, JAX-RPC has a Technology Compatibility Kit (TCK)
which is available to members of the JAX-RPC Expert Group (and others?).
<p>
The kit comes as a zip file which you should unzip into a directory of your
choosing.
The installation instructions are in the JAX-RPC Release Notes document which
is stored in the docs directory.
If you open the index.html file in the docs directory using a web browser,
you'll see a list of all the documents supplied with the kit.
<p>
Note that the kit includes the JavaTest test harness which is used for running
the compatibility tests.
<p>
If any more information is needed about running these tests, please add
it here!
</body>
</html>