You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by er...@apache.org on 2006/11/04 00:11:19 UTC
svn commit: r471043 - in /incubator/cxf/trunk/distribution/src/main/release:
./ docs/ samples/callback/ samples/dispatch_provider/ samples/handlers/
samples/hello_world/ samples/hello_world_RPCLit/ samples/hello_world_async/
samples/hello_world_xml_bar...
Author: ericjohnson
Date: Fri Nov 3 15:11:18 2006
New Revision: 471043
URL: http://svn.apache.org/viewvc?view=rev&rev=471043
Log:
Edited most of the readmes and other files for clarity and style.
Modified:
incubator/cxf/trunk/distribution/src/main/release/BUILDING.txt
incubator/cxf/trunk/distribution/src/main/release/README
incubator/cxf/trunk/distribution/src/main/release/docs/release_notes.txt
incubator/cxf/trunk/distribution/src/main/release/samples/callback/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/dispatch_provider/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/handlers/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/hello_world/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_RPCLit/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_async/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_bare/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_wrapped/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/jms_queue/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/js_provider/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/mtom/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/restful/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/soap12/README.txt
incubator/cxf/trunk/distribution/src/main/release/samples/soap_header/README.txt
Modified: incubator/cxf/trunk/distribution/src/main/release/BUILDING.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/BUILDING.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/BUILDING.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/BUILDING.txt Fri Nov 3 15:11:18 2006
@@ -5,36 +5,37 @@
-------------
1) Install J2SE 5.0 SDK, which can be downloaded from
- http://java.sun.com/j2se/1.5.0/download.jsp, use version of 1.5.0_06 JDK.
+ http://java.sun.com/j2se/1.5.0/download.jsp. Use version of 1.5.0_06 JDK.
-2) Make sure your JAVA_HOME environment variable is set to newly installed
- JDK location, and your PATH includes %JAVA_HOME%\bin (windows) or
- $JAVA_HOME$/bin (unix) directory.
+2) Make sure that your JAVA_HOME environment variable is set to the newly installed
+ JDK location, and that your PATH includes %JAVA_HOME%\bin (windows) or
+ $JAVA_HOME$/bin (unix).
3) Install Maven 2.0.4, which can be downloaded from
http://maven.apache.org/download.html. Make sure that your PATH includes
- MVN_HOME/bin directory.
+ the MVN_HOME/bin directory.
Building
--------
1) Change to the top level directory of Apache CXF source distribution.
-2) run
- $> mvn
- which will compile Apache CXF and run all tests under Apache CXF source
- distribution. Alternatively, you can also run
- $> mvn -Pfastinstall
- which will compile Apache CXF without running all tests and takes short
- time to build. Depending on the load of remote Maven 2.0 repositories,
- you may have to run "mvn" several times util required dependencies are
- all located in your local maven repository. It usually takes some for
+2) Run
+ $> mvn.
+ This will compile Apache CXF and run all of the tests in the Apache CXF source
+ distribution. Alternatively, you can run
+ $> mvn -Pfastinstall.
+ This will compile Apache CXF without running the tests and takes less
+ time to build.
+ Depending on the load of remote Maven 2.0 repositories, you may have
+ to run "mvn" several times utill the required dependencies are
+ all located in your local maven repository. It usually takes some time for
maven to download required dependencies in the first build.
Building kit
------------
-1) change to the "distribution" directory of Apache CXF source distribution.
-2) run
+1) Change to the "distribution" directory of Apache CXF source distribution.
+2) Run
$> mvn
- which will build Apache CXF distribution kit under "distribution/target"
+ This will build an Apache CXF distribution kit under "distribution/target"
directory.
Modified: incubator/cxf/trunk/distribution/src/main/release/README
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/README?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/README (original)
+++ incubator/cxf/trunk/distribution/src/main/release/README Fri Nov 3 15:11:18 2006
@@ -1,31 +1,44 @@
Welcome to Apache Incubator CXF!
======================
-Apache Incubator CXF simplifies the construction, integration, and flexible reuse of technical and business components using a standards-based, service-oriented architecture (SOA). It provides a pluggable architecture that supports not only XML but also non-XML type bindings in combination with any type of transport. It also supports several programming languages like JAX-WS, JBI, SCA, and CORBA services and is designed for flexible deployment in a variety of containers including Spring-based, JBI, SCA, Servlet and J2EE containers. The broad range of flexibility makes it possible to create and integrate web services and legacy services using a single framework.
+Apache Incubator CXF simplifies the construction, integration, and flexible
+reuse of technical and business components using a standards-based,
+service-oriented architecture (SOA). It provides a pluggable architecture that
+supports not only XML but also non-XML bindings in combination with any type
+of transport. It also supports several programming models including JAX-WS,
+JBI, SCA, and CORBA. It is designed for flexible deployment in a variety of
+containers including Spring-based, JBI, SCA, Servlet and J2EE containers. This
+broad range of flexibility makes it possible to create and integrate Web
+services and legacy services using a single framework.
Incubation Disclaimer
=====================
-Apache Incubator CXF is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
+Apache Incubator CXF is an effort undergoing incubation at the Apache Software
+Foundation (ASF), sponsored by the Apache Incubator PMC.
-Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects.
-
-While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+Incubation is required of all newly accepted projects until a further review
+indicates that the infrastructure, communications, and decision making process
+have stabilized in a manner consistent with other successful ASF projects.
+
+While incubation status is not necessarily a reflection of the completeness or
+stability of the code, it does indicate that the project has yet to be fully
+endorsed by the ASF.
Getting Started
===============
-For Apache CXF source distribution, please read BUILDING.txt for
-how to build Apache CXF.
+For an Apache CXF source distribution, please read BUILDING.txt for
+instructions on building Apache CXF.
-For Apache CXF binary distribution, please read doc/release_notes.txt
-for installation instruction and list of supported and unsupported
+For an Apache CXF binary distribution, please read doc/release_notes.txt
+for installation instructions and list of supported and unsupported
features.
-Alternatively, you can also find out how to get started here
+Alternatively, you can also find out how to get started here:
http://cwiki.apache.org/confluence/display/CXF/Index
-If you need more help try talking to us on our mailing lists
+If you need more help try talking to us on our mailing lists:
http://cwiki.apache.org/confluence/display/CXF/Mailing+Lists
@@ -35,4 +48,4 @@
The Apache Incubator CXF Team
-http://incubator.apache.org/projects/cxf.html
+http://incubator.apache.org/projects/cxf.html
\ No newline at end of file
Modified: incubator/cxf/trunk/distribution/src/main/release/docs/release_notes.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/docs/release_notes.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/docs/release_notes.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/docs/release_notes.txt Fri Nov 3 15:11:18 2006
@@ -1,8 +1,8 @@
Apache CXF 2.0 M1 Release Notes
-1. Apache CXF 2.0 M1 release delivers the merge of Celtix project
-(http://celtix.objectweb.org) and Xfire project (http://xfire.codehaus.org),
-thus this release includes all major features from historical Celtix and Xfire
+Apache CXF 2.0 M1 release delivers the merge of the Celtix project
+(http://celtix.objectweb.org) and the Xfire project (http://xfire.codehaus.org).
+This release includes all major features of both the Celtix and the Xfire
projects:
* JAX-WS 2.0 implementation
* Transports: HTTP 1.1, HTTPS, and JMS
@@ -55,9 +55,9 @@
3. Building samples
-Building samples included in binary distribution is easy. Please change to
-samples directory and following build instruction readme.txt under each
-sample.
+Building the samples included in the binary distribution is easy. Change to
+the samples directory and follow the build instructions in the README.txt file
+included with each sample.
4. Known Problems
@@ -65,10 +65,10 @@
There is an issue with Jetty HTTP that prevents Apache CXF from being able to
shut down the actual port listener. If you programmatically remove the last endpoint
published on a port, the listener remains running on the port, but only 404
-(page not found) errors are served to all client connections.
+(page not found) errors are served to subsequent client connections.
3.2 Schema Definitions
-There is no support for nillable elements in XML Schema and xsi:nil attribute
+There is no support for nillable elements in XML Schema and xsi:nil attributes
in XML documents.
4. Reporting Problems
@@ -76,11 +76,12 @@
If you have any problems or want to send feedback of any kind, please e-mail the
cxf dev list, cxf-dev@incupator.apache.org.
-5. Specific issues, features, improvements fixed in CXF 2.0 M1 release:
+5. Specific issues, features, and improvements fixed in the
+CXF 2.0 M1 release:
Release Notes - CXF - Version 2.0-M1
-** Bug
+** Bugs
* [CXF-6] - jaxws-api, jsr181-api should be optional in cxf-common pom
* [CXF-18] - addPort not implemented
* [CXF-53] - Remove JAX-WS dependency of HTTP transport
@@ -111,14 +112,14 @@
* [CXF-174] - Allow overriding the default stax parser/writer
* [CXF-178] - Schema parser cannot resolve relative import locations (case of multiple imports).
-** Improvement
+** Improvements
* [CXF-98] - get schema validation working for jaxb mashall and unmashall
* [CXF-109] - Remove isInSoapHeader() from service model
* [CXF-115] - org.apache.cxf.jaxws.EndpointImpl needs additional constructors
* [CXF-116] - Remove references to HTTPAddress/SOAPAddress/etc in EndpointInfo
* [CXF-187] - Provide Eclipse plugin from CXF to faciliate STP Integration
-** New Feature
+** New Features
* [CXF-2] - Complete JAX-WS frontend
* [CXF-15] - JCA supportting
* [CXF-83] - Support the injection of WebServiceContext
@@ -127,7 +128,7 @@
* [CXF-130] - Add Handler demo
* [CXF-144] - Conduits/DestinationFactorys should be able to provide interceptors
-** Task
+** Tasks
* [CXF-1] - set up distribution build, meet incubator requirements etc...
* [CXF-7] - Dispatch
* [CXF-13] - CXF JMS Transport support
@@ -156,7 +157,7 @@
* [CXF-165] - addd dotnet integration demos
* [CXF-167] - Upgrade CXF jms transport to use ActiveMQ 4.0.x
-** Test
+** Tests
* [CXF-66] - Port Celtix type tests to CeltiXfire
* [CXF-111] - MTOM Interop testing (MicroSoft, Axis, and JAX-WS RI etc)
* [CXF-112] - CXF performance testing and tuning
@@ -165,5 +166,5 @@
* [CXF-176] - add test for anonymous ref in wsdl schema defination
* [CXF-182] - Port remaining system tests from Celtix
-** Wish
- * [CXF-146] - Add Bus factory method that takes a URL
+** Wishes
+ * [CXF-146] - Add Bus factory method that takes a URL
\ No newline at end of file
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/callback/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/callback/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/callback/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/callback/README.txt Fri Nov 3 15:11:18 2006
@@ -1,10 +1,10 @@
-Callback demo
+Callback Demo
=============================================
-This demo demonstrates a client creating a callback object,
-passing an EndpointReferenceType over to the server.
-The EndpointRefrenceType is then used to allow the server
-to call back on the callback object
+This demo showss a client creating a callback object by
+passing an EndpointReferenceType to the server. The
+EndpointRefrenceType is then used by the server to call
+back on the callback object
Please review the README in the samples directory before
continuing.
@@ -16,11 +16,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -107,6 +107,4 @@
To remove the code generated from the WSDL file and the .class
files, either delete the build directory and its contents or run:
- ant clean
-
-
+ ant clean
\ No newline at end of file
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/dispatch_provider/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/dispatch_provider/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/dispatch_provider/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/dispatch_provider/README.txt Fri Nov 3 15:11:18 2006
@@ -2,10 +2,10 @@
======================================================
The demo demonstrates the use of JAX-WS Dispatch and Provider interface.
-The client side Dispatch instance invokes upon a endpoint using a JAX-WS
-provider implementor. There are three differnt invocations from the client.
-The first uses a SOAPMessage data in MESSAGE mode. The second uses a DOMSource
-data in MESSAGE mode. The third uses a DOMSource in PAYLOAD mode. The three
+The client side Dispatch instance invokes upon an endpoint using a JAX-WS
+Provider implementor. There are three differnt invocations from the client.
+The first uses the SOAPMessage data in MESSAGE mode. The second uses the DOMSource
+data in MESSAGE mode. The third uses the DOMSource in PAYLOAD mode. The three
different messages are constructed by reading in the XML files found in the
src/demo/hwDispatch/client directory.
@@ -18,11 +18,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/handlers/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/handlers/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/handlers/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/handlers/README.txt Fri Nov 3 15:11:18 2006
@@ -1,8 +1,8 @@
Handler Demo
============
-This demo shows how JAXWS handlers can be used. The server uses a
-SOAP protocol handler which simply logs incoming and outgoing messages
+This demo shows how JAX-WS handlers are used. The server uses a
+SOAP protocol handler which logs incoming and outgoing messages
to the console.
The server code registers a handler using the @HandlerChain annotation
@@ -21,17 +21,17 @@
If your environment already includes cxf-incubator.jar on the CLASSPATH,
and the JDK and ant bin directories on the PATH, it is not necessary to
-run the environment script described in the samples directory README.
+set the environment as described in the samples directory's README.
If your environment is not properly configured, or if you are planning
on using wsdl2java, javac, and java to build and run the demos, you must
-set the environment by running the script.
+set the environment.
Building and running the demo using ant
---------------------------------------
From the samples/handlers directory, the ant build script can be used to
-build and run the demo. The server and client targets automatically build
+build and run the demo. The server and client targets automatically build
the demo.
Using either UNIX or Windows:
@@ -40,14 +40,14 @@
ant client
When using these ant targets, the server process uses the LoggingHandler
-and the client process uses the SmallNumberHandler. Notice that the both
-the client and server consoles display short informative messages. The
-client handler examines the operation parameters and, depending on the
-parameter values, may not forward the request to the server. The server
-handler displays the entire content of each message in its console and
-the client no longer uses a handler. The @HandlerChain annotation in the
-implementation class indicates that the file demo_handler.xml includes the
-information needed to identify the handler class.
+and the client process uses the SmallNumberHandler. Notice that the both
+the client and server consoles display short informative messages. The
+client handler examines the operation parameters and, based on the
+parameter values, may decide not to forward the request to the server. The server
+handler displays the entire content of each message in its console.
+The @HandlerChain annotation in the implementation class indicates that
+the file demo_handler.xml includes the information needed to identify the
+handler class.
@HandlerChain(file = "../common/demo_handlers.xml", name = "DemoHandlerChain")
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/hello_world/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/hello_world/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/hello_world/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/hello_world/README.txt Fri Nov 3 15:11:18 2006
@@ -1,9 +1,6 @@
Hello World Demo using Document/Literal Style
=============================================
-Yes, it's the ever present Hello World demo. No product is
-complete without one.
-
Please review the README in the samples directory before
continuing.
@@ -14,11 +11,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
+it is not necessary to set the environment as described in
the samples directory README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_RPCLit/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_RPCLit/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_RPCLit/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_RPCLit/README.txt Fri Nov 3 15:11:18 2006
@@ -1,8 +1,7 @@
Hello World Demo using RPC-Literal Style
========================================
-Yes, it's the ever present Hello World demo. No product is
-complete without one. However, this version demonstrates use
+This version of Helloe World demonstrates the use
of the RPC-Literal style binding.
Please review the README in the samples directory before
@@ -10,16 +9,16 @@
-Prerequisite
-------------
+Prerequisites
+-------------
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -79,8 +78,8 @@
Running the demo using java
---------------------------
-From the samples/hello_world_RPCLit directory run the commands, entered on a
-single command line:
+From the samples/hello_world_RPCLit directory run the following
+commands. They are entered on a single command line:
For UNIX (must use forward slashes):
java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
@@ -149,4 +148,4 @@
demo.hwRPCLit.client.Client http://localhost:#/helloworldrpclit/cxf/hello_world_rpclit
Where # is the TCP/IP port used by the servlet container,
-e.g., 8080.
+e.g., 8080.
\ No newline at end of file
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_async/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_async/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_async/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_async/README.txt Fri Nov 3 15:11:18 2006
@@ -1,13 +1,13 @@
Hello World Asynchronous Demo using Document/Literal Style
==========================================================
-This demo illustrates usage of the JAX-WS asynchronous
+This demo illustrates the use of the JAX-WS asynchronous
invocation model. Please refer to the JAX-WS 2.0 specification
(http://jcp.org/aboutJava/communityProcess/pfd/jsr224/index.html)
for background.
The asynchronous model allows the client thread to continue after
-making a twoway invocation without being blocked awaiting a
+making a two-way invocation without being blocked while awaiting a
response from the server. Once the response is available, it is
delivered to the client application asynchronously using one
of two alternative approaches:
@@ -41,13 +41,13 @@
Prerequisite
------------
-If your environment already includes cxf.jar on the
+If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
+it is not necessary to set the environment as described in
the samples directory README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -79,8 +79,8 @@
Edit the async_binding.xml.tmpl, substituting the full path to the
wsdl for @WSDL_LOCATION@
-Save as async_binding.xml, This file is required by the wsdl2java
-command to generate classes required in the async case.
+Save the editied file as async_binding.xml, This file is required by
+the wsdl2java command to generate classes required in the async case.
For UNIX:
mkdir -p build/classes
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_bare/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_bare/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_bare/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_bare/README.txt Fri Nov 3 15:11:18 2006
@@ -1,9 +1,9 @@
Hello World Demo using BARE Style in XML Binding
=============================================
-This demo illustrates how cxf works with xml binding instead of soap
-binding. And this specific demo shows you how xml binding works
-with the doc-lit bare style
+This demo illustrates the use of CXF's xml binding. This
+specific demo shows you how xml binding works with the
+doc-lit bare style
Please review the README in the samples directory before
continuing.
@@ -14,11 +14,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -78,8 +78,8 @@
Running the demo using java
---------------------------
-From the samples/hello_world_xml_bare directory run the commands, entered
-on a single command line:
+From the samples/hello_world_xml_bare directory run the following
+commands. They are entered on a single command line.
For UNIX (must use forward slashes):
java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_wrapped/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_wrapped/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_wrapped/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/hello_world_xml_wrapped/README.txt Fri Nov 3 15:11:18 2006
@@ -1,9 +1,9 @@
Hello World Demo using WRAPPED Style in XML Binding
=============================================
-This demo illustrates how cxf works with xml binding instead of soap
-binding. And this specific demo shows you how xml binding works
-with the doc-lit wrapped style.
+This demo illustrates the use of CXF's xml binding. This
+specific demo shows you how xml binding works with the
+doc-lit wrapped style.
Please review the README in the samples directory before
continuing.
@@ -14,11 +14,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/README.txt Fri Nov 3 15:11:18 2006
@@ -2,7 +2,7 @@
==========================================================
This sample demonstrates use of the Document-Literal style
-binding over JMS Transport using pub/sub mechanism.
+binding over JMS transport using the pub/sub mechanism.
Please review the README in the samples directory before
continuing.
@@ -14,20 +14,20 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
+it is not necessary to set the environment as described in
the samples directory README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
-This demo need to play with ActiveMQ 4.0.X, Before you run this
-Demo, please make sure you had installed the ActiveMQ 4.0.X and
+This demo requires ActiveMQ 4.0.X. Before you run this
+demo, please make sure you had installed the ActiveMQ 4.0.X and
set ACTIVE_HOME and ACTIVE_VERSION environment variables.
-Befor you run this demo, please start up the JMS message broker first.
+Befor you run this demo, start up the JMS message broker.
From ActiveMQ 4.0.X insallation launch ActiveMQ JMS Broker in seperate window
-or in background using the commandline:
+or in background using the commands:
For Unix:
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/jms_queue/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/jms_queue/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/jms_queue/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/jms_queue/README.txt Fri Nov 3 15:11:18 2006
@@ -2,7 +2,7 @@
==========================================================
This sample demonstrates use of the Document-Literal style
-binding over JMS Transport using queue mechanism.
+binding over JMS Transport using the queue mechanism.
Please review the README in the samples directory before
continuing.
@@ -14,19 +14,19 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
+it is not necessary to set the environment as described in
the samples directory README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
-This demo need to play with ActiveMQ 4.X, Before you run this
-Demo, please make sure you had installed the ActiveMQ 4.X and
+This demo requires ActiveMQ 4.X. Before you run this demo,
+please make sure you have installed the ActiveMQ 4.X and
set ACTIVE_HOME and ACTIVE_VERSION environment variables.
Befor you run this demo, please start up the JMS message broker first.
-From ActiveMQ 4.X insallation launch ActiveMQ JMS Broker in seperate window
+From ActiveMQ 4.X insallation launch ActiveMQ JMS broker in seperate window
or in background using the commandline:
For Unix:
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/js_provider/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/js_provider/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/js_provider/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/js_provider/README.txt Fri Nov 3 15:11:18 2006
@@ -21,11 +21,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
You also need to download js-1.6R2.jar from
(http://repo1.maven.org/maven2/rhino/js/1.6R2/) and xbean-2.1.0.jar
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/mtom/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/mtom/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/mtom/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/mtom/README.txt Fri Nov 3 15:11:18 2006
@@ -1,9 +1,8 @@
MTOM Demo for SWA & XOP
=============================================
-This is the demo for using attachment in soap. It illustrate
-the usage of Soap message with Attachment and XML-binary
-Optimized Packaging.
+This demo illustrates the use of a SOAP message
+with an attachment and XML-binary Optimized Packaging.
Please review the README in the samples directory before
continuing.
@@ -15,11 +14,11 @@
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -79,8 +78,8 @@
Running the demo using java
---------------------------
-From the samples/mtom directory run the commands, entered on a
-single command line:
+From the samples/mtom directory run the following commands.
+They are entered on a single command line.
For UNIX (must use forward slashes):
java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/restful/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/restful/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/restful/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/restful/README.txt Fri Nov 3 15:11:18 2006
@@ -1,15 +1,15 @@
RESTful Hello World Demo
========================
-The demo demonstrates the REST based webservices using XML binding and
-JAX-WS Provider/Dispatch. The rest server provides following services:
+The demo shows REST based Web services using the XML binding and
+JAX-WS Provider/Dispatch. The REST server provides the following services:
-A RESTful customer service is provided on URL http://localhost:9000/customerservice/customers,
-users access this URI to query or update customer info.
+A RESTful customer service is provided on URL http://localhost:9000/customerservice/customers.
+Users access this URI to query or update customer info.
A HTTP GET request to URL http://localhost:9000/customerservice/customers returns
-a list of customer hyperlinks, this allows client navigates through the
-application states. The xml document returned:
+a list of customer hyperlinks. This allows client navigates through the
+application states. The returned XML document:
<Customers>
<Customer href="http://localhost/customerservice/customer?id=1234">
@@ -24,7 +24,7 @@
</Customers>
A HTTP GET request to URL http://localhost:9000/customerservice/customers?id=1234
-returns a customer instance whose id is 1234. The xml document returned:
+returns a customer instance whose id is 1234. The returned XML document returned:
<Customer>
<id>1234</id>
@@ -32,7 +32,8 @@
<phoneNumber>123456</phoneNumber>
</Customer>
-A HTTP POST request to URL http://localhost:9000/customerservice/customers with data:
+A HTTP POST request to URL http://localhost:9000/customerservice/customers
+with the data:
<Customer>
<id>1234</id>
@@ -42,24 +43,24 @@
updates customer 1234 with the data provided.
-The demo client codes demonstrate how to sent HTTP POST with XML data using
-JAX-WS dispatch and how to sent HTTP GET using URL.openStream().
+The client code demonstrate how to send HTTP POST with XML data using
+JAX-WS Dispatch and how to send HTTP GET using URL.openStream().
Please review the README in the samples directory before
continuing.
-Prerequisite
+Prerequisites
------------
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
+it is not necessary to set the environment as described in
the samples directory README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -119,8 +120,8 @@
Running the demo using java
---------------------------
-From the samples/hello_world directory run the commands, entered on a
-single command line:
+From the samples/hello_world directory run the following commands. They
+are entered on a single command line.
For UNIX (must use forward slashes):
java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
@@ -146,5 +147,4 @@
To remove the code generated from the WSDL file and the .class
files, either delete the build directory and its contents or run:
- ant clean
-
+ ant clean
\ No newline at end of file
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/soap12/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/soap12/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/soap12/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/soap12/README.txt Fri Nov 3 15:11:18 2006
@@ -1,23 +1,23 @@
Hello World SOAP12 Demo using Document/Literal Style
=============================================
-This is exactly as same as Hello World demo but using SOAP 1.2
+This demo shows the use of CXF's SOAP 1.2 capabilities.
Please review the README in the samples directory before
continuing.
-Prerequisite
-------------
+Prerequisites
+-------------
If your environment already includes cxf-incubator.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -77,8 +77,8 @@
Running the demo using java
---------------------------
-From the samples/hello_world directory run the commands, entered on a
-single command line:
+From the samples/hello_world directory run the following commands.
+They are entered on a single command line:
For UNIX (must use forward slashes):
java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties
Modified: incubator/cxf/trunk/distribution/src/main/release/samples/soap_header/README.txt
URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/distribution/src/main/release/samples/soap_header/README.txt?view=diff&rev=471043&r1=471042&r2=471043
==============================================================================
--- incubator/cxf/trunk/distribution/src/main/release/samples/soap_header/README.txt (original)
+++ incubator/cxf/trunk/distribution/src/main/release/samples/soap_header/README.txt Fri Nov 3 15:11:18 2006
@@ -1,10 +1,10 @@
SOAP Headers
============
-This demo illustrates Apache CSF's support for SOAP headers. In the
-WSDL file, the SOAP header is included as an additiona part within
-message and binding definitions. With this approach to defining a
-SOAP header, celtixfire treats the header content as another parameter
+This demo illustrates Apache CxF's support for SOAP headers. In the
+WSDL file, the SOAP header is included as an additional part within
+the message and binding definitions. Using this approach to defining a
+SOAP header, CXF treats the header content as another parameter
to the operation. Consequently, the header content is simply
manipulated within the method body.
@@ -18,16 +18,16 @@
-Prerequisite
-------------
+Prerequisites
+-------------
If your environment already includes cxf.jar on the
CLASSPATH, and the JDK and ant bin directories on the PATH
-it is not necessary to run the environment script described in
-the samples directory README. If your environment is not
+it is not necessary to set the environment as described in
+the samples directory's README. If your environment is not
properly configured, or if you are planning on using wsdl2java,
javac, and java to build and run the demos, you must set the
-environment by running the script.
+environment.
@@ -85,8 +85,8 @@
Running the demo using java
---------------------------
-From the samples/soap_header directory run the commands, entered on a
-single command line:
+From the samples/soap_header directory run the following commands.
+They are entered on a single command line:
For UNIX (must use forward slashes):
java -Djava.util.logging.config.file=$CXF_HOME/etc/logging.properties