butek 02/03/11 06:51:36
Modified: java/docs user-guide.html
java/src/org/apache/axis/utils resources.properties
java/src/org/apache/axis/wsdl WSDL2Java.java
Log:
WSDL2Java --skeletonDeploy used to require --server-side. Now it assumes
it, so you don't have to explicitly specify --server-side if you speclfy
--skeletonDeploy.
Revision Changes Path
1.41 +41 -42 xml-axis/java/docs/user-guide.html
Index: user-guide.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/user-guide.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- user-guide.html 9 Mar 2002 20:14:02 -0000 1.40
+++ user-guide.html 11 Mar 2002 14:51:36 -0000 1.41
@@ -251,7 +251,7 @@
(You'll find this file in <a
href="../samples/userguide/example1/TestClient.java">samples/userguide/example1/TestClient.java</a>)
<p>Assuming you have a network connection active, this program can be run
as follows:
-<pre>% java samples.userguide.example1.TestClient
+<pre class="example">% java samples.userguide.example1.TestClient
Sent 'Hello!', got 'Hello!'
%</pre>
So what's happening here? On lines 11 and 12 we create new Service and
@@ -383,7 +383,7 @@
SOAP calls correctly into Java invocations of your service class. Try it
out - there's a calculator client in samples/userguide/example2/CalcClient.java,
which you can use like this:
-<pre>% java samples.userguide.example2.CalcClient -p8080 add 2 5
+<pre class="example">% java samples.userguide.example2.CalcClient -p8080 add 2 5
Got result : 7
% java samples.userguide.example2.CalcClient -p8080 subtract 10 9
Got result : 1
@@ -435,11 +435,11 @@
actually deploy the described service. We do this with the AdminClient,
or the "org.apache.axis.client.AdminClient" class. An invocation of the
AdminClient looks like this:
-<pre>% java org.apache.axis.client.AdminClient deploy.wsdd
+<pre class="example">% java org.apache.axis.client.AdminClient deploy.wsdd
<Admin>Done processing</Admin></pre>
This command has now made our service accessible via SOAP. Check it out
by running the Client class - it should look like this:
-<pre>% java samples.userguide.example3.Client "test me!"
+<pre class="example">% java samples.userguide.example3.Client "test me!"
You typed : test me!
%</pre>
If you want to prove to yourself that the deployment really worked, try
@@ -449,7 +449,7 @@
Client again and see what happens.
<p>You can also use the AdminClient to get a listing of all the deployed
components in the server:
-<pre>% java org.apache.axis.client.AdminClient list
+<pre class="example">% java org.apache.axis.client.AdminClient list
<big XML document returned here></pre>
In there you'll see services, handlers, transports, etc. Note that this
listing is an exact copy of the server's "server-config.wsdd" file, which
@@ -462,25 +462,24 @@
do just this. To use a handler class like this, you first need to deploy
the Handler itself, and then use the name that you give it in deploying
a service. Here's a sample deploy.wsdd file (this is example 4 in
samples/userguide):
-<div class="example"><pre><deployment xmlns="http://xml.apache.org/axis/wsdd/";
-
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
-
- <!-- define the logging handler configuration -->
- <handler name="track" type="java:samples.userguide.example4.LogHandler">
- <parameter name="filename" value="MyService.log"/>
- </handler>
-
- <!-- define the service, using the log handler we just defined -->
- <service name="LogTestService"<b> </b>provider="java:RPC">
- <requestFlow>
- <handler type="track"/>
- </requestFlow>
-
- <parameter name="className" value="samples.userguide.example4.Service"/>
- <parameter name="allowedMethods" value="*"/>
- </service>
-</deployment></pre></div>
-The first section defines a Handler called "track" that is implemented
+<div class="example"><br><deployment xmlns="http://xml.apache.org/axis/wsdd/";
+<br>
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
+<br> <!-- define the logging handler configuration -->
+<br> <handler name="track"
type="java:samples.userguide.example4.LogHandler">
+<br> <parameter name="filename" value="MyService.log"/>
+<br> </handler>
+<br>
+<br> <!-- define the service, using the log handler we just defined -->
+<br> <service name="LogTestService"<b> </b>provider="java:RPC">
+<br> <requestFlow>
+<br> <handler type="track"/>
+<br> </requestFlow>
+<br>
+<br> <parameter name="className"
value="samples.userguide.example4.Service"/>
+<br> <parameter name="allowedMethods" value="*"/>
+<br> </service>
+<br></deployment></div>
+<p>The first section defines a Handler called "track" that is implemented
by the class samples.userguide.example4.LogHandler. We give this Handler
an option to let it know which file to write its messages into.
<p>Then we define a service, LogTestService, which is an RPC service just
@@ -497,12 +496,12 @@
to <b>true</b>. To do this, find the "server-config.wsdd" file in your
webapp's WEB-INF directory. In it, you'll see a deployment for the AdminService.
Add an option as follows:
-<pre><service name="AdminService" provider="java:MSG">
- <parameter name="className" value="org.apache.axis.util.Admin"/>
- <parameter name="methodName" value="*"/>
- <b><parameter name="enableRemoteAdmin" value="true"/>
-</b></service></pre>
-<b>WARNING: enabling remote administration may give unauthorized parties
+<div class="example"><br><service name="AdminService" provider="java:MSG">
+<br> <parameter name="className" value="org.apache.axis.util.Admin"/>
+<br> <parameter name="allowedMethods" value="*"/>
+<br> <b><parameter name="enableRemoteAdmin" value="true"/>
+<br></b></service></div>
+<p><b>WARNING: enabling remote administration may give unauthorized parties
access to your machine. If you do this, please make sure to add security
to your configuration!</b>
<h2>
@@ -562,18 +561,19 @@
Now that you've built your serializers and deserializers, you need to tell
Axis which types they should be used for. You do this with a typeMapping
tag in WSDD, which looks like this:
-<pre class="xml"><typeMapping qname="ns:local" xmlns:ns="someNamespace"
-
languageSpecificType="java:my.java.thingy"
-
serializer="my.java.Serializer"
-
deserializer="my.java.DeserializerFactory"/></pre>
-This looks a lot like the <beanMapping> tag we saw earlier, but there
-are two extra attributes. One, <b>serializer</b>, is the Java class name
+<div class="example"><br><typeMapping qname="ns:local" xmlns:ns="someNamespace"
+<br>
languageSpecificType="java:my.java.thingy"
+<br>
serializer="my.java.Serializer"
+<br>
deserializer="my.java.DeserializerFactory"
+<br>
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/></div>
+<p>This looks a lot like the <beanMapping> tag we saw earlier, but there
+are three extra attributes. One, <b>serializer</b>, is the Java class name
of the Serializer class which should be used to write the specified Java
-class (i.e. my.java.thingy) into XML. The other, <b>deserializer</b>, is
+class (i.e. my.java.thingy) into XML. Two, <b>deserializer</b>, is
the class name of a Deserializer <i>factory</i> that generates Deserializers
-which can be used to unmarshall XML into the correct Java class.
+which can be used to unmarshall XML into the correct Java class. Finally, the
encoding style, which is SOAP encoding.
<p>(The <beanMapping> tag is really just shorthand for a <typeMapping>
-tag with serializer="org.apache.axis.encoding.BeanSerializer" and
deserializer="org.apache.axis.encoding.BeanSerializer$BeanDeserFactory",
+tag with serializer="org.apache.axis.encoding.BeanSerializer",
deserializer="org.apache.axis.encoding.BeanSerializer$BeanDeserFactory", and
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";,
but clearly it can save a lot of typing!)
<h2>
<a NAME="WSDL"></a>Using WSDL with Axis</h2>
@@ -962,7 +962,7 @@
<br>
deploy skeleton (true) or implementation (false) in deploy.wsdd.
<br>
-Default is true. Only valid with --server-side.
+Default is true. Assumes --server-side.
<br> -N, --NStoPkg
<argument>=<value>
<br>
mapping of namespace to package
@@ -1039,8 +1039,7 @@
<br> <parameter name="className"
value="samples.addr.AddressBookSOAPBindingImpl"/>
<br> ...
<br> </service></font></div>
-<p>The default for this option is true. This option is only valid
-with the --server-side option.
+<p>The default for this option is true. When you use this option, the
--server-side option is assumed, so you don't have to explicitly specify --server-side
as well.
<h4>
-N, --NStoPkg <argument>=<value></h4>
By default, package names are generated from the namespace strings in the
1.66 +1 -1 xml-axis/java/src/org/apache/axis/utils/resources.properties
Index: resources.properties
===================================================================
RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/utils/resources.properties,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- resources.properties 5 Mar 2002 14:52:05 -0000 1.65
+++ resources.properties 11 Mar 2002 14:51:36 -0000 1.66
@@ -630,7 +630,7 @@
j2woptstopClass00=space or comma separated list of class names which will stop
inheritance search if --all switch is given
# NOTE: in optionSkeletonDeploy00, do not translate "--server-side".
-optionSkeletonDeploy00=deploy skeleton (true) or implementation (false) in
deploy.wsdd. Default is true. Only valid with --server-side.
+optionSkeletonDeploy00=deploy skeleton (true) or implementation (false) in
deploy.wsdd. Default is true. Assumes --server-side.
j2wMissingLocation00=The -l <location> option must be specified if the full wsdl or
the implementation wsdl is requested.
invalidSolResp00={0} is a solicit-response style operation and is unsupported.
1.11 +4 -5 xml-axis/java/src/org/apache/axis/wsdl/WSDL2Java.java
Index: WSDL2Java.java
===================================================================
RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/wsdl/WSDL2Java.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- WSDL2Java.java 5 Mar 2002 14:52:05 -0000 1.10
+++ WSDL2Java.java 11 Mar 2002 14:51:36 -0000 1.11
@@ -460,17 +460,16 @@
wsdl2java.verbose(true);
break;
- case SERVER_OPT:
- bServer = true;
- wsdl2java.generateServerSide(true);
- break;
-
case SKELETON_DEPLOY_OPT:
skeletonDeploy = option.getArgument(0);
if (skeletonDeploy.equalsIgnoreCase("true"))
wsdl2java.deploySkeleton(true);
else
wsdl2java.deploySkeleton(false);
+
+ case SERVER_OPT:
+ bServer = true;
+ wsdl2java.generateServerSide(true);
break;
case NAMESPACE_OPT:
