diff options
| author | nash <nash@13f79535-47bb-0310-9956-ffa450edef68> | 2010-06-10 20:27:31 +0000 |
|---|---|---|
| committer | nash <nash@13f79535-47bb-0310-9956-ffa450edef68> | 2010-06-10 20:27:31 +0000 |
| commit | 98eec492c08e491401841dd33e8392b41c1e6660 (patch) | |
| tree | af1129e753a0923a51db744214be4bced2d694aa /sca-java-1.x/tags/travelsample-1.0/distribution | |
| parent | 9437c0186c353b9b379f92937421cd722d6f2c31 (diff) | |
Copy travelsample-1.0-RC3 tag as travelsample-1.0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@953445 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'sca-java-1.x/tags/travelsample-1.0/distribution')
8 files changed, 1991 insertions, 0 deletions
diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/pom.xml b/sca-java-1.x/tags/travelsample-1.0/distribution/pom.xml new file mode 100644 index 0000000000..f0ecd2de94 --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/pom.xml @@ -0,0 +1,88 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!-- + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. +--> +<project> + <modelVersion>4.0.0</modelVersion> + <parent> + <groupId>org.apache.tuscany.sca</groupId> + <artifactId>scatours</artifactId> + <version>1.0</version> + <relativePath>../pom.xml</relativePath> + </parent> + <artifactId>scatours-distribution</artifactId> + <name>Apache Tuscany SCA Tours Distribution</name> + <packaging>pom</packaging> + + <dependencies> + <dependency> + <groupId>com.sun.xml.ws</groupId> + <artifactId>jaxws-tools</artifactId> + <version>2.1.7</version> + <scope>runtime</scope> + <exclusions> + <!-- exclude the following because it's already included in binaries/target/jaxws --> + <exclusion> + <groupId>com.sun.xml.ws</groupId> + <artifactId>jaxws-rt</artifactId> + </exclusion> + <!-- exclude the following because it's part of the Tuscany SCA binary distro --> + <exclusion> + <groupId>com.sun.xml.bind</groupId> + <artifactId>jaxb-xjc</artifactId> + </exclusion> + </exclusions> + </dependency> + + <dependency> + <groupId>junit</groupId> + <artifactId>junit</artifactId> + <version>4.5</version> + <scope>runtime</scope> + </dependency> + </dependencies> + + <build> + <plugins> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-assembly-plugin</artifactId> + <executions> + <execution> + <id>distribution-package</id> + <phase>package</phase> + <goals> + <goal>single</goal> + </goals> + <configuration> + <descriptors> + <descriptor>src/main/assembly/src.xml</descriptor> + </descriptors> + <tarLongFileMode>gnu</tarLongFileMode> + <archiveBaseDirectory>.</archiveBaseDirectory> + <outputDirectory>target</outputDirectory> + <finalName>apache-tuscany-scatours-${version}</finalName> + <appendAssemblyId>true</appendAssemblyId> + <ignoreDirFormatExtensions>true</ignoreDirFormatExtensions> + </configuration> + </execution> + </executions> + </plugin> + </plugins> + </build> +</project> diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/assembly/src.xml b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/assembly/src.xml new file mode 100644 index 0000000000..36e67f6d77 --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/assembly/src.xml @@ -0,0 +1,96 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!-- + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. +--> +<assembly> + <!-- id typically identifies the "type" (src vs bin etc) of the assembly --> + <id></id> + <includeBaseDirectory>true</includeBaseDirectory> + <baseDirectory>tuscany-scatours-${version}</baseDirectory> + <formats> +<!-- + <format>dir</format> +--> + <format>tar.gz</format> + <format>zip</format> + </formats> + + <fileSets> + <fileSet> + <directory>..</directory> + <outputDirectory>travelsample</outputDirectory> + <excludes> + <exclude>**/.*</exclude> + <exclude>**/.*/**</exclude> + <exclude>**/*.log</exclude> + <exclude>**/target</exclude> + <exclude>**/target/**/*</exclude> + <exclude>**/maven-eclipse.xml</exclude> + </excludes> + </fileSet> + + <!-- Add the text files to the top-level directory --> + <fileSet> + <directory>src/main/release</directory> + <outputDirectory></outputDirectory> + <includes> + <include>BUILDING</include> + <include>CHANGES</include> + <include>LICENSE</include> + <include>NOTICE</include> + <include>README</include> + <include>RELEASE_NOTES</include> + </includes> + </fileSet> + + <!-- Add binary dependencies to the lib directory --> + <fileSet> + <directory>../binaries/target</directory> + <outputDirectory>lib</outputDirectory> + <includes> + <include>openejb/**/*</include> + <include>jaxws/**/*</include> + </includes> + </fileSet> + </fileSets> + + <dependencySets> + <!-- Add tools dependencies to the lib directory --> + <dependencySet> + <useProjectArtifact>false</useProjectArtifact> + <outputDirectory>lib/jaxws</outputDirectory> + <unpack>false</unpack> + <includes> + <include>com.sun.xml.ws:jaxws-tools</include> + </includes> + <scope>runtime</scope> + </dependencySet> + + <!-- Add tools dependencies to the lib directory --> + <dependencySet> + <useProjectArtifact>false</useProjectArtifact> + <outputDirectory>lib/junit</outputDirectory> + <unpack>false</unpack> + <includes> + <include>junit:junit</include> + </includes> + <scope>runtime</scope> + </dependencySet> + </dependencySets> + +</assembly> diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/BUILDING b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/BUILDING new file mode 100644 index 0000000000..e5eabe3b88 --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/BUILDING @@ -0,0 +1,139 @@ +Building the Apache Tuscany SCA Travel Sample 1.0 June 2010 release distribution
+================================================================================
+
+Initial Setup
+-------------
+
+1) Install Java SE JDK 5 or JDK 6, which can be downloaded from
+ http://java.sun.com/javase/downloads/index.jsp. For JDK 5 use update 22
+ and for JDK 6 use update 7 (or later).
+
+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 Apache Maven 2.0.7 or later, which can be downloaded from
+ http://maven.apache.org/download.html. Make sure that your M2_HOME
+ environment variable is set to the installation base directory, and that
+ your PATH includes %M2_HOME%\bin (windows) or $M2_HOME/bin (unix).
+
+4) Install Apache Ant 1.7.1 or later, which can be downloaded from
+ http://ant.apache.org/bindownload.cgi. Make sure that your ANT_HOME
+ environment variable is set to the installation base directory, and that
+ your PATH includes %ANT_HOME%\bin (windows) or $ANT_HOME/bin (unix).
+
+5) Download the Apache Tuscany SCA Java 1.6 (or later) binary distribution
+ from http://tuscany.apache.org/sca-java-1x-releases.html and unpack it
+ into a local directory. Set your TUSCANY_HOME environment variable to
+ the base directory containing the unpacked binary distribution.
+
+6) Download the Apache Tuscany SCA Java Travel Sample 1.0 (or later) distribution
+ from http://tuscany.apache.org/sca-java-travel-sample-1x-releases.html and
+ unpack it into a local directory.
+
+
+Building using Ant
+------------------
+
+1) Change to the "travelsample" directory of the Apache Tuscany SCA Travel Sample
+ distribution which you unpacked in step 6) above.
+
+2) Run the command "ant". This will compile the complete travel sample and
+ run all of the travel sample unit tests.
+
+
+Building using Maven
+--------------------
+
+1) Change to the "travelsample" directory of the Apache Tuscany SCA Travel Sample
+ distribution which you unpacked in step 6) above.
+
+2) Run the command "mvn". You will need a live internet connection so that
+ Maven can download any required files to your local repository. This will
+ compile the complete travel sample and run all of the travel sample unit tests.
+
+ Depending on the load of remote Maven 2.0 repositories, you may have
+ to run "mvn" several times until 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. Once all the
+ dependencies have been downloaded you may use the -o option to run maven
+ in offline mode, for example, 'mvn clean install -o'.
+
+ When building with Maven, an executable binary package for the travel
+ sample is created in the travelsample/binaries/target directory. By default
+ this binary package is an add-on delta to the Tuscany SCA Java 1.6 binary
+ distribution. If you want to produce a fully self-contained binary package
+ in the travelsample/binaries/target directory (with no external dependencies),
+ you can use the command "mvn -Pselfcontained" instead of "mvn" when
+ building from the "travelsample" directory.
+
+
+Building the Distribution
+-------------------------
+
+1) Change to the travelsample/distribution directory.
+
+2) Run the command "mvn". This will build the distribution package
+ with .zip and .tar.gz formats in the distribution/target directory.
+
+
+Running the Travel Sample
+-------------------------
+
+Full details of how to run the travel sample can be found in the README
+file in the "travelsample" directory of the unpacked distribution.
+
+
+Changing the Tuscany SCA Java version used for the build
+--------------------------------------------------------
+
+If you are using Maven to build the travel sample, the maven build files
+are set up to use the 1.6 version of Tuscany SCA Java. You can build
+the travel sample using some other version of Tuscany SCA Java (for example,
+a development snapshot) by changing the <tuscany.version> property in the
+travelsample/pom.xml file.
+
+If you are using Ant to build the travel sample, you can change the
+version of Tuscany SCA Java used by the build by changing the setting of
+the TUSCANY_HOME environment variable before running the build.
+
+
+Building a development snaphost of the travel sample code
+---------------------------------------------------------
+
+You can build the latest development snapshot of the travel sample by
+following these steps:
+
+1) Install Apache Subversion 1.4.0 or later, which can be downloaded from
+http://subversion.apache.org/packages.html. Make sure that your PATH
+includes the "bin" subdirectory of the installation base directory.
+
+2) Check out the travel sample code from svn using the following command:
+svn co http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tutorials/travelsample
+
+3) Change to the travelsample directory of your local travel sample checkout
+and run the command "mvn". This will use Maven to compile the complete
+travel sample and run all of the travel sample unit tests.
+
+4) If you want to build the travel sample using Ant instead of Maven,
+you need to peform the following additional steps:
+
+ 4a) Download the JUnit 4.5 (or later) binary distribution from
+ http://github.com/KentBeck/junit/downloads and unpack it into a local
+ directory. Set your the JUNIT_JAR environment variable to the full path
+ to the junit-x.y.z.jar in the unpacked binary distribution taking care
+ to replace x.y.z with the JUnit version number.
+
+ 4b) Download the Apache OpenEJB 3.1.2 (or later) binary distribution
+ from http://openejb.apache.org/download.html and unpack it into a local
+ directory. Set your OPENEJB_HOME environment variable to the base directory
+ containing the unpacked binary distribution.
+
+ 4c) If you are using JDK 5, download the JAX-WS reference implementation
+ version 2.1.7 from https://jax-ws.dev.java.net/2.1.7/ and unpack it into
+ a local directory. Set your JAXWS_HOME environment variable to the base
+ directory containing the unpacked download.
+
+ 4d) Change to the travelsample directory of your local travel sample
+ checkout and run the command "ant". This will use Ant to compile the
+ complete travel sample and run all of the travel sample unit tests.
diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/CHANGES b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/CHANGES new file mode 100644 index 0000000000..e58c518bf8 --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/CHANGES @@ -0,0 +1,4 @@ +Changes in Apache Tuscany SCA Travel Sample 1.0 June 2010
+=========================================================
+
+First release of the travel sample.
diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/LICENSE b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/LICENSE new file mode 100644 index 0000000000..90394d2117 --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/LICENSE @@ -0,0 +1,725 @@ +
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+===============================================================================
+
+APACHE TUSCANY SCA TRAVEL SAMPLE REDISTRIBUTED FILES:
+
+The Apache Tuscany SCA Travel Sample distribution includes a number of
+redistributed files with separate copyright notices and license terms.
+Your use of these redistributed files is subject to the terms and conditions
+of the following licenses.
+
+===============================================================================
+
+The following files come under Apache Software License 2.0:
+ commons-cli-1.1.jar
+ commons-dbcp-all-1.3-r699049.jar
+ ejb31-api-experimental-3.1.2.jar
+ geronimo-transaction-2.1.jar
+ javaee-api-5.0-2.jar
+ openejb-api-3.1.2.jar
+ openejb-client-3.1.2.jar
+ openejb-core-3.1.2.jar
+ openejb-ejbd-3.1.2.jar
+ openejb-javaagent-3.1.2.jar
+ openejb-jee-3.1.2.jar
+ openejb-loader-3.1.2.jar
+ openejb-server-3.1.2.jar
+ xbean-asm-shaded-3.6.jar
+ xbean-finder-shaded-3.6.jar
+ xbean-reflect-3.6.jar
+
+===============================================================================
+
+The files:
+ http-20070405.jar,
+ jaxws-rt-2.1.7.jar,
+ jaxws-tools-2.1.7.jar,
+ saaj-api-1.3.jar,
+ saaj-impl-1.3.3.jar,
+ stax-ex-1.2.jar,
+ streambuffer-0.9.jar
+are redistributed in executable form, with source code available at
+ https://jax-ws-sources.dev.java.net/source/browse/jax-ws-sources/
+and are licensed under the following terms:
+
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0
+
+
+ 1. Definitions.
+
+ 1.1. "Contributor" means each individual or entity that
+ creates or contributes to the creation of Modifications.
+
+ 1.2. "Contributor Version" means the combination of the
+ Original Software, prior Modifications used by a
+ Contributor (if any), and the Modifications made by that
+ particular Contributor.
+
+ 1.3. "Covered Software" means (a) the Original Software, or
+ (b) Modifications, or (c) the combination of files
+ containing Original Software with files containing
+ Modifications, in each case including portions thereof.
+
+ 1.4. "Executable" means the Covered Software in any form
+ other than Source Code.
+
+ 1.5. "Initial Developer" means the individual or entity
+ that first makes Original Software available under this
+ License.
+
+ 1.6. "Larger Work" means a work which combines Covered
+ Software or portions thereof with code not governed by the
+ terms of this License.
+
+ 1.7. "License" means this document.
+
+ 1.8. "Licensable" means having the right to grant, to the
+ maximum extent possible, whether at the time of the initial
+ grant or subsequently acquired, any and all of the rights
+ conveyed herein.
+
+ 1.9. "Modifications" means the Source Code and Executable
+ form of any of the following:
+
+ A. Any file that results from an addition to,
+ deletion from or modification of the contents of a
+ file containing Original Software or previous
+ Modifications;
+
+ B. Any new file that contains any part of the
+ Original Software or previous Modification; or
+
+ C. Any new file that is contributed or otherwise made
+ available under the terms of this License.
+
+ 1.10. "Original Software" means the Source Code and
+ Executable form of computer software code that is
+ originally released under this License.
+
+ 1.11. "Patent Claims" means any patent claim(s), now owned
+ or hereafter acquired, including without limitation,
+ method, process, and apparatus claims, in any patent
+ Licensable by grantor.
+
+ 1.12. "Source Code" means (a) the common form of computer
+ software code in which modifications are made and (b)
+ associated documentation included in or with such code.
+
+ 1.13. "You" (or "Your") means an individual or a legal
+ entity exercising rights under, and complying with all of
+ the terms of, this License. For legal entities, "You"
+ includes any entity which controls, is controlled by, or is
+ under common control with You. For purposes of this
+ definition, "control" means (a) the power, direct or
+ indirect, to cause the direction or management of such
+ entity, whether by contract or otherwise, or (b) ownership
+ of more than fifty percent (50%) of the outstanding shares
+ or beneficial ownership of such entity.
+
+ 2. License Grants.
+
+ 2.1. The Initial Developer Grant.
+
+ Conditioned upon Your compliance with Section 3.1 below and
+ subject to third party intellectual property claims, the
+ Initial Developer hereby grants You a world-wide,
+ royalty-free, non-exclusive license:
+
+ (a) under intellectual property rights (other than
+ patent or trademark) Licensable by Initial Developer,
+ to use, reproduce, modify, display, perform,
+ sublicense and distribute the Original Software (or
+ portions thereof), with or without Modifications,
+ and/or as part of a Larger Work; and
+
+ (b) under Patent Claims infringed by the making,
+ using or selling of Original Software, to make, have
+ made, use, practice, sell, and offer for sale, and/or
+ otherwise dispose of the Original Software (or
+ portions thereof).
+
+ (c) The licenses granted in Sections 2.1(a) and (b)
+ are effective on the date Initial Developer first
+ distributes or otherwise makes the Original Software
+ available to a third party under the terms of this
+ License.
+
+ (d) Notwithstanding Section 2.1(b) above, no patent
+ license is granted: (1) for code that You delete from
+ the Original Software, or (2) for infringements
+ caused by: (i) the modification of the Original
+ Software, or (ii) the combination of the Original
+ Software with other software or devices.
+
+ 2.2. Contributor Grant.
+
+ Conditioned upon Your compliance with Section 3.1 below and
+ subject to third party intellectual property claims, each
+ Contributor hereby grants You a world-wide, royalty-free,
+ non-exclusive license:
+
+ (a) under intellectual property rights (other than
+ patent or trademark) Licensable by Contributor to
+ use, reproduce, modify, display, perform, sublicense
+ and distribute the Modifications created by such
+ Contributor (or portions thereof), either on an
+ unmodified basis, with other Modifications, as
+ Covered Software and/or as part of a Larger Work; and
+
+
+ (b) under Patent Claims infringed by the making,
+ using, or selling of Modifications made by that
+ Contributor either alone and/or in combination with
+ its Contributor Version (or portions of such
+ combination), to make, use, sell, offer for sale,
+ have made, and/or otherwise dispose of: (1)
+ Modifications made by that Contributor (or portions
+ thereof); and (2) the combination of Modifications
+ made by that Contributor with its Contributor Version
+ (or portions of such combination).
+
+ (c) The licenses granted in Sections 2.2(a) and
+ 2.2(b) are effective on the date Contributor first
+ distributes or otherwise makes the Modifications
+ available to a third party.
+
+ (d) Notwithstanding Section 2.2(b) above, no patent
+ license is granted: (1) for any code that Contributor
+ has deleted from the Contributor Version; (2) for
+ infringements caused by: (i) third party
+ modifications of Contributor Version, or (ii) the
+ combination of Modifications made by that Contributor
+ with other software (except as part of the
+ Contributor Version) or other devices; or (3) under
+ Patent Claims infringed by Covered Software in the
+ absence of Modifications made by that Contributor.
+
+ 3. Distribution Obligations.
+
+ 3.1. Availability of Source Code.
+
+ Any Covered Software that You distribute or otherwise make
+ available in Executable form must also be made available in
+ Source Code form and that Source Code form must be
+ distributed only under the terms of this License. You must
+ include a copy of this License with every copy of the
+ Source Code form of the Covered Software You distribute or
+ otherwise make available. You must inform recipients of any
+ such Covered Software in Executable form as to how they can
+ obtain such Covered Software in Source Code form in a
+ reasonable manner on or through a medium customarily used
+ for software exchange.
+
+ 3.2. Modifications.
+
+ The Modifications that You create or to which You
+ contribute are governed by the terms of this License. You
+ represent that You believe Your Modifications are Your
+ original creation(s) and/or You have sufficient rights to
+ grant the rights conveyed by this License.
+
+ 3.3. Required Notices.
+
+ You must include a notice in each of Your Modifications
+ that identifies You as the Contributor of the Modification.
+ You may not remove or alter any copyright, patent or
+ trademark notices contained within the Covered Software, or
+ any notices of licensing or any descriptive text giving
+ attribution to any Contributor or the Initial Developer.
+
+ 3.4. Application of Additional Terms.
+
+ You may not offer or impose any terms on any Covered
+ Software in Source Code form that alters or restricts the
+ applicable version of this License or the recipients'
+ rights hereunder. You may choose to offer, and to charge a
+ fee for, warranty, support, indemnity or liability
+ obligations to one or more recipients of Covered Software.
+ However, you may do so only on Your own behalf, and not on
+ behalf of the Initial Developer or any Contributor. You
+ must make it absolutely clear that any such warranty,
+ support, indemnity or liability obligation is offered by
+ You alone, and You hereby agree to indemnify the Initial
+ Developer and every Contributor for any liability incurred
+ by the Initial Developer or such Contributor as a result of
+ warranty, support, indemnity or liability terms You offer.
+
+
+ 3.5. Distribution of Executable Versions.
+
+ You may distribute the Executable form of the Covered
+ Software under the terms of this License or under the terms
+ of a license of Your choice, which may contain terms
+ different from this License, provided that You are in
+ compliance with the terms of this License and that the
+ license for the Executable form does not attempt to limit
+ or alter the recipient's rights in the Source Code form
+ from the rights set forth in this License. If You
+ distribute the Covered Software in Executable form under a
+ different license, You must make it absolutely clear that
+ any terms which differ from this License are offered by You
+ alone, not by the Initial Developer or Contributor. You
+ hereby agree to indemnify the Initial Developer and every
+ Contributor for any liability incurred by the Initial
+ Developer or such Contributor as a result of any such terms
+ You offer.
+
+ 3.6. Larger Works.
+
+ You may create a Larger Work by combining Covered Software
+ with other code not governed by the terms of this License
+ and distribute the Larger Work as a single product. In such
+ a case, You must make sure the requirements of this License
+ are fulfilled for the Covered Software.
+
+ 4. Versions of the License.
+
+ 4.1. New Versions.
+
+ Sun Microsystems, Inc. is the initial license steward and
+ may publish revised and/or new versions of this License
+ from time to time. Each version will be given a
+ distinguishing version number. Except as provided in
+ Section 4.3, no one other than the license steward has the
+ right to modify this License.
+
+ 4.2. Effect of New Versions.
+
+ You may always continue to use, distribute or otherwise
+ make the Covered Software available under the terms of the
+ version of the License under which You originally received
+ the Covered Software. If the Initial Developer includes a
+ notice in the Original Software prohibiting it from being
+ distributed or otherwise made available under any
+ subsequent version of the License, You must distribute and
+ make the Covered Software available under the terms of the
+ version of the License under which You originally received
+ the Covered Software. Otherwise, You may also choose to
+ use, distribute or otherwise make the Covered Software
+ available under the terms of any subsequent version of the
+ License published by the license steward.
+
+ 4.3. Modified Versions.
+
+ When You are an Initial Developer and You want to create a
+ new license for Your Original Software, You may create and
+ use a modified version of this License if You: (a) rename
+ the license and remove any references to the name of the
+ license steward (except to note that the license differs
+ from this License); and (b) otherwise make it clear that
+ the license contains terms which differ from this License.
+
+
+ 5. DISCLAIMER OF WARRANTY.
+
+ COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS"
+ BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
+ INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED
+ SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR
+ PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
+ PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY
+ COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
+ INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF
+ ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
+ WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
+ ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS
+ DISCLAIMER.
+
+ 6. TERMINATION.
+
+ 6.1. This License and the rights granted hereunder will
+ terminate automatically if You fail to comply with terms
+ herein and fail to cure such breach within 30 days of
+ becoming aware of the breach. Provisions which, by their
+ nature, must remain in effect beyond the termination of
+ this License shall survive.
+
+ 6.2. If You assert a patent infringement claim (excluding
+ declaratory judgment actions) against Initial Developer or
+ a Contributor (the Initial Developer or Contributor against
+ whom You assert such claim is referred to as "Participant")
+ alleging that the Participant Software (meaning the
+ Contributor Version where the Participant is a Contributor
+ or the Original Software where the Participant is the
+ Initial Developer) directly or indirectly infringes any
+ patent, then any and all rights granted directly or
+ indirectly to You by such Participant, the Initial
+ Developer (if the Initial Developer is not the Participant)
+ and all Contributors under Sections 2.1 and/or 2.2 of this
+ License shall, upon 60 days notice from Participant
+ terminate prospectively and automatically at the expiration
+ of such 60 day notice period, unless if within such 60 day
+ period You withdraw Your claim with respect to the
+ Participant Software against such Participant either
+ unilaterally or pursuant to a written agreement with
+ Participant.
+
+ 6.3. In the event of termination under Sections 6.1 or 6.2
+ above, all end user licenses that have been validly granted
+ by You or any distributor hereunder prior to termination
+ (excluding licenses granted to You by any distributor)
+ shall survive termination.
+
+ 7. LIMITATION OF LIABILITY.
+
+ UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
+ (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE
+ INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF
+ COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE
+ LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR
+ CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT
+ LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK
+ STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
+ COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
+ INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
+ LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL
+ INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT
+ APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO
+ NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR
+ CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT
+ APPLY TO YOU.
+
+ 8. U.S. GOVERNMENT END USERS.
+
+ The Covered Software is a "commercial item," as that term is
+ defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial
+ computer software" (as that term is defined at 48 C.F.R.
+ 252.227-7014(a)(1)) and "commercial computer software
+ documentation" as such terms are used in 48 C.F.R. 12.212 (Sept.
+ 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1
+ through 227.7202-4 (June 1995), all U.S. Government End Users
+ acquire Covered Software with only those rights set forth herein.
+ This U.S. Government Rights clause is in lieu of, and supersedes,
+ any other FAR, DFAR, or other clause or provision that addresses
+ Government rights in computer software under this License.
+
+ 9. MISCELLANEOUS.
+
+ This License represents the complete agreement concerning subject
+ matter hereof. If any provision of this License is held to be
+ unenforceable, such provision shall be reformed only to the
+ extent necessary to make it enforceable. This License shall be
+ governed by the law of the jurisdiction specified in a notice
+ contained within the Original Software (except to the extent
+ applicable law, if any, provides otherwise), excluding such
+ jurisdiction's conflict-of-law provisions. Any litigation
+ relating to this License shall be subject to the jurisdiction of
+ the courts located in the jurisdiction and venue specified in a
+ notice contained within the Original Software, with the losing
+ party responsible for costs, including, without limitation, court
+ costs and reasonable attorneys' fees and expenses. The
+ application of the United Nations Convention on Contracts for the
+ International Sale of Goods is expressly excluded. Any law or
+ regulation which provides that the language of a contract shall
+ be construed against the drafter shall not apply to this License.
+ You agree that You alone are responsible for compliance with the
+ United States export administration regulations (and the export
+ control laws and regulation of any other countries) when You use,
+ distribute or otherwise make available any Covered Software.
+
+ 10. RESPONSIBILITY FOR CLAIMS.
+
+ As between Initial Developer and the Contributors, each party is
+ responsible for claims and damages arising, directly or
+ indirectly, out of its utilization of rights under this License
+ and You agree to work with Initial Developer and Contributors to
+ distribute such responsibility on an equitable basis. Nothing
+ herein is intended or shall be deemed to constitute any admission
+ of liability.
+
+===============================================================================
+
+The file:
+ junit-4.5.jar
+is redistributed in object code form, with source code available at
+ http://sourceforge.net/projects/junit/files/
+and is licensed under the following terms:
+
+Common Public License - v 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+ a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and
+ b) in the case of each subsequent Contributor:
+
+ i) changes to the Program, and
+
+ ii) additions to the Program;
+
+ where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.
+
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
+
+2. GRANT OF RIGHTS
+
+ a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.
+
+ b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.
+
+ c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.
+
+ d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.
+
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
+
+ a) it complies with the terms and conditions of this Agreement; and
+
+ b) its license agreement:
+
+ i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;
+
+ ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;
+
+ iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and
+
+ iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.
+
+When the Program is made available in source code form:
+
+ a) it must be made available under this Agreement; and
+
+ b) a copy of this Agreement must be included with each copy of the Program.
+
+Contributors may not remove or alter any copyright notices contained within the Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
+
+All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.
diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/NOTICE b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/NOTICE new file mode 100644 index 0000000000..5346498b7c --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/NOTICE @@ -0,0 +1,5 @@ +Apache Tuscany
+Copyright (c) 2005 - 2010 The Apache Software Foundation
+
+This product includes/uses software developed at
+The Apache Software Foundation (http://www.apache.org/).
diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/README b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/README new file mode 100644 index 0000000000..5a0408ad7c --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/README @@ -0,0 +1,869 @@ +README for the Apache Tuscany SCA Travel Sample 1.0 June 2010
+=============================================================
+
+Structure of the travel sample
+------------------------------
+
+The travel sample consists of the following directory tree:
+
+lib dependencies for the travel sample (see notes below)
+ jaxws jars from the JAX-WS reference implementation
+ junit the Junit jar
+ openejb jars from the OpenEJB binary distribution
+travelsample top-level directory for the travel sample
+ binaries builds a binaries-only package for the travel sample
+ clients non-SCA clients for the travel sample
+ contributions SCA contributions for the travel sample
+ distribution builds the travel sample distribution
+ domainconfig configuration files for the domain manager
+ launchers launcher programs for the travel sample
+ services non-SCA services used by the travel sample
+ testdomain scratch directory for trying out the domain manager
+ util utility code used by other parts of the travel sample
+
+Note 1: The travel sample depends on the Apache Tuscany SCA Java 1.x binary
+distribution, which is downloaded separately from the travel sample.
+To avoid needless duplication, the "lib" directory of the travel sample only
+contains dependencies that aren't provided in the Apache Tuscany SCA Java 1.x
+binary distribution. The 1.0 release of the travel sample has been tested
+with Apache Tuscany SCA Java 1.6.
+
+Note 2: The 1.0 release of the travel sample is not compatible with
+Apache Tuscany SCA Java 2.x.
+
+Note 3: Before attempting to build or run the travel sample, you will need
+to download the Apache Tuscany SCA Java 1.6 (or later 1.x release) binary
+distribution and set your TUSCANY_HOME environment variable to a local
+directory containing the unpacked binary distribution.
+
+
+Overview of the travel sample
+-----------------------------
+
+The travel sample consists of a number of related scenarios. For each
+scenario, this section lists the following:
+ Description: A description of the scenario.
+ Contributions: SCA contributions used in the scenario. Each contribution
+ is a subdirectory of the travelsample/contributions directory.
+ Launchers: Launchers used in the scenario. Each launcher is a subdirectory
+ of the travelsample/launchers directory.
+ Services: Non-SCA services used in the scenario, if any. Each non-SCA
+ service is a subdirectory of the travelsample/services directory.
+ Clients: Non-SCA clients used in the scenario, if any. Each non-SCA
+ client is a subdirectory of the travelsample/clients directory.
+ Webapp: Web application (.war) file used to run the scenario, for those
+ scenarios that use contributions packaged as web applications and
+ deployed in a Web application server such as Tomcat.
+
+Details of how to build and run these scenarios can be found in later
+sections of this file.
+
+1) Jumpstart - First simple example of using Tuscany
+
+Description: The jumpstart launcher shows the code needed to load an
+ SCA contribution and invoke a method. The introducing-trips contribution
+ shows how to package an SCA component in a contribution.
+Contributions: introducing-trips
+Launchers: jumpstart
+
+2) Introducing - Simplified introduction to the travel application
+
+Description: This scenario introduces a simplified form of the travel
+ booking application that will be developed and extended by other
+ scenarios in the travel sample. This scenario gives a clearer picture
+ than jumpstart of how SCA applications are constructed because it
+ shows multiple SCA components connected together with references wired
+ to services.
+Contributions: introducing-client, introducing-tours, introducing-trips
+Launchers: introducing
+
+3) Introducing (distributed) - Distributed services with a domain manager
+
+Description: We're using the same SCA components, services, and implementations
+ as in the previous scenario but with a big difference--they're distributed
+ across multiple execution nodes and they make remote calls to each other
+ using configuration information provided by the Tuscany domain manager.
+ For simplicity these nodes are represented as different processes running on
+ a single computer, though the domain manager configuration could easily be
+ modified to run the nodes on different computers communicating across a network.
+Contributions: introducing-client, introducing-tours, introducing-trips
+Launchers: introducing-client, introducing-domain, introducing-tours,
+ introducing-trips
+
+4) Using SCA - Defining and using SCA Components
+
+Description: The examples in this scenario show how to define SCA components
+ and how to use SCA components in a business application. This "guided tour"
+ consists of code samples illustrating the major features of SCA components
+ including implementations, services, interfaces, references, wires, properties,
+ bindings and domains.
+Contributions: usingsca
+Launchers: usingsca
+
+5) Building blocks - Using SCA composites as application building blocks
+
+Description: We're looking at how to create composite applications using
+ SCA composites as building blocks. The ToursImpl composite shows how to
+ use a composite as a component implementation (black box reuse) and the
+ ToursImplInclude composite demonstrates including one composite in another
+ (white box reuse). The ToursAppl composite combines both of these kinds
+ of reuse and shows how easy it is to build a full composite application
+ using building blocks.
+Contributions: buildingblocks, buildingblocks-client, introducing-trips
+Launchers: buildingblocks
+
+6) Interaction - Different SCA interaction styles
+
+Description: Each SCA interaction pattern is demonstrated using a component
+ from the travel booking application. We’re going to see the Hotel, Calendar,
+ CurrencyConverter and ShoppingCart components used here. These components
+ don't work in isolation so for each interaction pattern we've written a
+ simple client component. For example, the InteractionLocalClient component
+ demonstrates local interactions by sending a local message to the Calendar
+ component. The launcher starts two nodes (node1 and node2) which are used
+ to run samples for all of the interaction patterns. The first node "node1"
+ loads the contributions common, currency, calendar, shoppingcart, and
+ interaction-client, and runs the client.composite from the interaction-client
+ contribution. The local interaction patterns are demonstrated by clients
+ calling the currency, calendar, and shoppingcart components locally within
+ node1. The second node node2 loads the contributions common, hotel, and
+ interaction-service-remote, and runs the service.composite from the
+ interaction-service-remote contribution. This node provides the hotel
+ component that's used by client components in node1 for sending remote
+ messages to demonstrate the remote interaction pattern.
+Contributions: calendar, common, currency, flight, hotel, interaction-client,
+ interaction-service-remote, shoppingcart
+Launchers: interaction
+
+7) Full application - The full interactive travel application
+
+Description: This is the fully functional travel application with a user
+ interface for booking a trip (either pre-packaged or customized), adding the
+ trip to a shopping cart, and checking out the purchase using a credit card.
+Contributions: car, common, creditcard-payment-jaxb-policy, currency, flight,
+ fullapp-bespoketrip, fullapp-coordination, fullapp-currency, fullapp-packagedtrip,
+ fullapp-shoppingcart, fullapp-ui, hotel, payment-spring-policy, scatours,
+ shoppingcart, travelcatalog, trip, tripbooking
+Launchers: fullapp
+
+8) Full application (distributed) - Distributed services with a domain manager
+
+Description: This version of the full travel application uses multiple execution
+ nodes and the domain manager. The execution nodes all run within the same
+ process, which isn't very realistic but shows the flexibility of the Tuscany
+ runtime model which allows nodes to be allocated to processes and computers in
+ any combination. There's one small difference in the contributions used by this
+ distributed version: payment-java-policy is used instead of payment-spring-policy
+ because of an incompatibility between the domain manager and implementation.spring
+ (see issue TUSCANY-3476).
+
+Contributions: car, common, creditcard-payment-jaxb-policy, currency, flight,
+ fullapp-bespoketrip, fullapp-coordination, fullapp-currency, fullapp-packagedtrip,
+ fullapp-shoppingcart, fullapp-ui, hotel, payment-java-policy, scatours,
+ shoppingcart, travelcatalog, trip, tripbooking
+Launchers: fullapp-domain, fullapp-nodes
+
+9) Callback
+
+Description: SCA callbacks are illustrated using a variation of the Payment
+ service which makes callbacks to the client to perform additional security
+ checks for large payments.
+Contributions: payment-java-callback
+Launchers: payment-java-callback
+
+10) Reference passing
+
+Description: We use another variation on the Payment service to show how
+ SCA service references can be passed as parameters when invoking a service.
+ The Payment service creates a service reference for the EmailGateway service
+ and passes this service reference to the CreditCardPayment service. When the
+ CreditCardPayment service has finished doing the credit card authorization,
+ it invokes the EmailGateway service using the service reference that was
+ passed in.
+Contributions: payment-java-reference-pass
+Launchers: payment-java-reference-pass
+
+11) Help pages
+
+Description: This scenario shows how an SCA application can expose HTML web pages
+ by using an SCA component with the implementation.resource implementation type.
+Contributions: help-pages
+Launchers: help-pages
+
+12) Blog feed
+
+Description: An SCA component implementation of a blog is exposed as a
+ feed via the Atom protocol using binding.atom and via the RSS protocol
+ using binding.rss. For each protocol there are example implementations
+ using two different approaches: the getAll() method and the Collection API.
+Contributions: blog-feed
+Launchers: blog-feed
+
+13) Feed logger
+
+Description: An SCA component implementation is connected to an Atom feed
+ using binding.atom and an RSS feed using binding.rss. The SCA component
+ receives and logs entries from both feeds.
+Contributions: feed-logger
+Launchers: feed-logger
+
+14) Data binding
+
+Description: A Payment component that uses JAXB as its data representation
+ invokes a CreditCardPayment component that uses SDO to represent its data.
+ The Tuscany data binding framework converts automatically between these
+ different data representations.
+Contributions: creditcard-payment-sdo, databinding-client, payment-java
+Launchers: databinding
+
+15) Policy
+
+Description: The implementation of the Trip component has the tuscany:logging
+ implementation policy applied to it which means that all invocations of all
+ its services go through the JDKLoggingPolicyInterceptor class. In addition
+ the CreditCardPayment service has the "authentication" interaction policy
+ intent which requires invocations of this service from the Payment component
+ to use a policy set that satisifies this intent by providing authentication
+ of the invoking client.
+Contributions: creditcard-payment-jaxb-policy, payment-java-policy,
+ policy-client, trip-policy
+Launchers: policy
+
+16) SCA credit card payment service packaged as a web application
+
+Description: The CreditCardPayment service is packaged in a web application
+ (.war file) including all its Tuscany runtime dependencies and suitable
+ for deployment to a Web application server such as Apache Tomcat. The
+ service is configured with a <binding.ws> endpoint which is exposed by
+ Apache Tomcat and will display its WSDL in response to a ?wsdl request.
+ The web application also includes a JSP which provides a user interface
+ for invoking the CreditCardPayment service.
+Contributions: creditcard-payment-jaxb, creditcard-payment-webapp
+Webapp: creditcard-payment-webapp
+
+17) Payment service with different implementation types
+
+Description: In SCA the technology used to implement a service is encapsulated
+ by the service and doesn't affect other components that invoke the service.
+ In this scenario we show how the Payment service can be implemented using a
+ range of different technologies while providing the same interface and the
+ same semantics.
+
+17a) implementation.bpel
+
+Description: The Payment service is implemented using a BPEL process.
+Contributions: creditcard-payment-jaxb, emailgateway, payment-bpel, payment-bpel-process
+Launchers: payment-bpel
+
+17b) implementation.script written in Groovy
+
+Description: The Payment service is implemented using a Groovy script.
+Contributions: emailgateway, payment-groovy
+Launchers: payment-groovy
+
+17c) implementation.java
+
+Description: The Payment service is implemented using a Java class.
+Contributions: creditcard-payment-jaxb, payment-java
+Launchers: payment-java
+
+17d) implementation.java with policy
+
+Description: The Payment service is implemented using a Java class, and
+ the reference from the Payment service to the CreditCardPayment service
+ is defined as requiring the "authentication" security policy.
+Contributions: creditcard-payment-jaxb-policy, payment-java-policy
+Launchers: payment-java-policy
+
+17e) implementation.script written in Python
+
+Description: The Payment service is implemented using a Python script.
+Contributions: emailgateway, payment-python
+Launchers: payment-python
+
+17f) implementation.spring
+
+Description: The Payment service is implemented using a Spring application
+ context which doesn't use any SCA-specific features.
+Contributions: creditcard-payment-jaxb, payment-spring
+Launchers: payment-spring
+
+17g) implementation.spring with SCA tags
+
+Description: The Payment service is implemented using a Spring application
+ context which uses SCA-specific XML elements (tags) to define SCA references
+ and properties.
+Contributions: creditcard-payment-jaxb, payment-spring-scatag
+Launchers: payment-spring-scatag
+
+18) SCA currency converter service interoperating with SCA or non-SCA client
+
+Description: In SCA a service can be configured with a variety of bindings
+ to expose it using a range of different communication protocols. This
+ scenario contains a number of examples showing the CurrencyConverter service
+ exposed using different bindings and invoked by SCA or non-SCA clients
+ using various protocols.
+
+18a) SCA client
+
+Description: The CurrencyConverter service uses the default SCA binding and
+ is invoked by an SCA client running in the same process.
+Contributions: currency
+Launchers: currency-converter
+
+18b) CORBA client
+
+Description: The CurrencyConverter service is exposed as a CORBA service
+ using binding.corba and is invoked by a Java CORBA client running in a
+ different process.
+Contributions: currency, currency-corba
+Launchers: currency-converter-corba
+Clients: currency-converter-corba
+
+18c) JMS client
+
+Description: The CurrencyConverter service is exposed as a JMS service
+ using binding.jms and is invoked by an ActiveMQ JMS client running in
+ a different process.
+Contributions: currency, currency-jms
+Launchers: currency-converter-jms
+Clients: currency-converter-jms
+
+18d) RMI client
+
+Description: The CurrencyConverter service is exposed as an RMI service
+ using binding.rmi and is invoked by a Java RMI client running in a
+ different process.
+Contributions: currency, currency-rmi
+Launchers: currency-converter-rmi
+Clients: currency-converter-rmi
+
+18e) JAX-WS client
+
+Description: The CurrencyConverter service is exposed as a web service
+ using binding.ws and is invoked over SOAP/HTTP by a JAX-WS client
+ running in a different process.
+Contributions: currency, currency-ws
+Launchers: currency-converter-ws
+Clients: currency-converter-ws-jaxws
+
+18f) Web application JSP client
+
+Description: The CurrencyConverter service is deployed as a web
+ application using the default SCA binding and is invoked from the
+ same process by a JSP client that's deployed as part of the same
+ web application.
+Contributions: currency, currency-jsp
+Webapp: scatours-contribution-currency-jsp.war
+
+18g) Web application servlet client
+
+Description: The CurrencyConverter service is deployed as a web
+ application using the default SCA binding and is invoked from the
+ same process using a servlet in the same web application which
+ generates HTML to display a client page.
+Contributions: currency, currency-servlet
+Webapp: scatours-contribution-currency-servlet.war
+
+19) SCA notification service interoperating with non-SCA SMS gateway service
+
+Description: SCA references can invoke non-SCA services using a range
+ of different communication protocols which are selected by choosing
+ a suitable binding to configure the reference. This scenario contains
+ a number of examples showing an SCA Notification service using an
+ SCA reference configured with different bindings to invoke a non-SCA
+ SMSGateway service over various different protocols.
+
+19a) SMS gateway CORBA service
+
+Description: The SCA reference uses binding.corba to invoke an SMSGateway
+ Java CORBA service running in a different process.
+Contributions: notification, notification-corba
+Services: smsgateway-corba
+Launchers: notification-corba
+
+19b) SMS gateway EJB service
+
+Description: The SCA reference uses binding.ejb to invoke an SMSGateway
+ EJB session bean running on OpenEJB in a different process.
+Contributions: notification, notification-ejb
+Services: smsgateway-ejb
+Launchers: notification-ejb
+
+19c) SMS gateway JMS service
+
+Description: The SCA reference uses binding.jms to invoke an SMSGateway
+ JMS service running on ActiveMQ in a different process.
+Contributions: notification, notification-jms
+Services: smsgateway-jms
+Launchers: notification-jms
+
+19d) SMS gateway RMI service
+
+Description: The SCA reference uses binding.rmi to invoke an SMSGateway
+ RMI service running in a different process.
+Contributions: notification, notification-rmi
+Services: smsgateway-rmi
+Launchers: notification-rmi
+
+19e) SMS gateway JAX-WS service
+
+Description: The SCA reference uses binding.ws to invoke an SMSGateway
+ JAX-WS web service running in a different process.
+Contributions: notification, notification-ws
+Services: smsgateway-jaxws
+Launchers: notification-ws
+
+
+Building the travel sample
+--------------------------
+
+Please see the BUILDING file in the travel sample distribution for full
+details of how to build the travel sample using Maven or Ant.
+
+
+Running travel sample scenarios from launcher source directories
+----------------------------------------------------------------
+
+After building the travel sample using either Maven or Ant, you can run
+all the scenarios that have launchers by using ant scripts in the
+subdirectories of the travelsample/launchers directory. For scenarios
+that are packaged as web applications and don't have launchers, the next
+section describes how you can run these.
+
+You can run the launcher ant scripts as follows:
+ 1. Open a command prompt.
+ 2. Change directory to travelsample/launchers/<launcher-dir> where
+ <launcher-dir> is the launcher directory for the scenario that you
+ want to run.
+ 3. Enter the command shown in Table 1 below. This command is usually
+ "ant run". This runs an ant script that sets the necessary
+ classpath and invokes the launcher class.
+ 4. Some scenarios require the above steps to be repeated multiple times
+ with different commands. These cases are indicated by entries in
+ Table 1 with more than one command listed. For these scenarios, all
+ the listed commands should be entered in separate command prompts
+ from the same current directory and in the same order as shown.
+ 5. Some scenarios have a browser-based user interface which is displayed
+ by entering the URLs shown in Table 1 in a browser after running the
+ launcher or launchers for the scenario. The recommended browser is
+ Firefox as some scenarios don't work with Internet Explorer.
+
+Table 1. Running scenarios packaged as launchers and contributions
+---------------------------------------------------------------------------------------------------------------
+| Scenario Launcher directory Commands URLs |
+---------------------------------------------------------------------------------------------------------------
+| 1) Jumpstart | jumpstart | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 2) Introducing | introducing | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 3) Introducing | introducing-client | ant run-domain | |
+| (distributed) | | ant run-trips | |
+| | | ant run-tours | |
+| | | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 4) Using SCA | usingsca | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 5) Building blocks | buildingblocks | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 6) Interaction | interaction | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 7) Full application | fullapp | ant run | http://localhost:8080/scatours |
+---------------------------------------------------------------------------------------------------------------
+| 8) Full application | fullapp-nodes | ant run-domain | |
+| (distributed) | | ant run | http://localhost:8080/scatours |
+---------------------------------------------------------------------------------------------------------------
+| 9) Callback | payment-java-callback | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 10) Reference | payment-java-reference-pass | ant run | |
+| passing | | | |
+---------------------------------------------------------------------------------------------------------------
+| 11) Help pages | help-pages | ant run | http://localhost:8085/help/index.html |
+---------------------------------------------------------------------------------------------------------------
+| 12) Blog feed | blog-feed | ant run | http://localhost:8090/BlogAtom |
+| | | | http://localhost:8090/BlogRSS |
+| | | | http://localhost:8090/BlogAtomAPIs |
+| | | | http://localhost:8090/BlogRSSAPIs |
+---------------------------------------------------------------------------------------------------------------
+| 13) Feed logger | feed-logger | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 14) Data binding | databinding | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 15) Policy | policy | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17) Payment service implementation types |
+| |
+| Impl type Launcher directory Commands URLs |
+---------------------------------------------------------------------------------------------------------------
+| 17a) BPEL | payment-bpel | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17b) Groovy | payment-groovy | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17c) Java | payment-java | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17d) Java + policy | payment-java-policy | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17e) Python | payment-python | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17f) Spring | payment-spring | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 17g) Spring SCA tags | payment-spring-scatag | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 18) Currency converter service binding types |
+| |
+| Binding type Launcher directory Commands URLs |
+---------------------------------------------------------------------------------------------------------------
+| 18a) SCA | currency-converter | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 18b) CORBA | currency-converter-corba | ant run | |
+| | | ant run-client | |
+---------------------------------------------------------------------------------------------------------------
+| 18c) JMS | currency-converter-jms | ant run | |
+| | | ant run-client | |
+---------------------------------------------------------------------------------------------------------------
+| 18d) RMI | currency-converter-rmi | ant run | |
+| | | ant run-client | |
+---------------------------------------------------------------------------------------------------------------
+| 18e) WS | currency-converter-ws | ant run | |
+| | | ant run-client | |
+---------------------------------------------------------------------------------------------------------------
+| 19) Notification reference binding types |
+| |
+| Binding type Launcher directory Commands URLs |
+---------------------------------------------------------------------------------------------------------------
+| 19a) CORBA | notification-corba | ant run-smsgateway | |
+| | | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 19b) EJB | notification-ejb | ant run-smsgateway | |
+| | | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 19c) JMS | notification-jms | ant run-smsgateway | |
+| | | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 19d) RMI | notification-rmi | ant run-smsgateway | |
+| | | ant run | |
+---------------------------------------------------------------------------------------------------------------
+| 19e) WS | notification-ws | ant run-smsgateway | |
+| | | ant run | |
+---------------------------------------------------------------------------------------------------------------
+
+
+Running travel sample scenarios in a Web application server
+-----------------------------------------------------------
+
+Some scenarios are packaged as web applications (.war files) and don't
+have launchers. After building the travel sample using either Maven or Ant,
+you can use a Web application server to run these scenarios.
+
+You can run these web applications as follows:
+ 1. Deploy the web application (.war) file to a Web application server
+ such as Tomcat. The .war file can be found in the directory
+ travelsample/contributions/<contrib-dir>/target where <contrib-dir>
+ is the contribution directory listed in Table 2 below. The name of
+ the .war file is scatours-contribution-<contrib-dir>.war.
+ 2. Display the browser-based user interface for the scenario by entering
+ its URLs in a browser. The URLs for each scenario are shown in Table 2.
+ The host and port in these URLs may need to be changed depending on the
+ configuration of the Web application server in which the web application
+ is deployed. These scenarios work in both Firefox and Internet Explorer.
+
+Table 2. Running scenarios packaged as web applications
+-------------------------------------------------------------------------------------------------------------------------------------------------
+| Scenario | Contribution directory | URLs |
+-------------------------------------------------------------------------------------------------------------------------------------------------
+| 16) Credit card | creditcard-payment-webapp | http://localhost:8080/scatours-contribution-creditcard-payment-webapp |
+| webapp service | | http://localhost:8080/scatours-contribution-creditcard-payment-webapp/CreditCardPayment?wsdl |
+-------------------------------------------------------------------------------------------------------------------------------------------------
+| 18f) Currency | currency-jsp | http://localhost:8080/scatours-contribution-currency-jsp |
+| converter JSP | | |
+-------------------------------------------------------------------------------------------------------------------------------------------------
+| 18g) Currency | currency-servlet | http://localhost:8080/scatours-contribution-currency-servlet |
+| converter | | |
+| servlet | | |
+-------------------------------------------------------------------------------------------------------------------------------------------------
+
+
+Running the domain manager
+--------------------------
+
+The travelsample/testdomain directory is provided for the purpose
+of running the domain manager and creating your own configuration.
+You can do this as follows:
+
+1. Open a command prompt and make travelsample/testdomain your
+ current directory.
+
+2. Enter "ant run" to start the domain manager.
+
+3. In a browser, start the domain manager GUI by entering the URL
+ "http://localhost:9990/ui/home". The recommended browser is Firefox
+ because the domain manager GUI doesn't work with Internet Explorer.
+
+4. In the browser window, create or update your domain manager
+ configuration using the domain manager GUI.
+
+5. To exit the domain manager, enter "q" in the command prompt window.
+ The domain configuration is saved automatically and will be
+ restored the next time you start the domain manager.
+
+6. If you want to remove your saved configuration and start again from
+ a clean slate, enter either "ant clean" or "mvn clean" from the
+ command prompt window.
+
+
+Running travel sample scenarios from the "binaries" directory
+-------------------------------------------------------------
+
+If the travel sample was built from the distribution using Ant or Maven,
+a binary package for the travel sample will be created in the binaries/target
+directory and its subdirectories. This binary package contains all the built
+jar and war files and runtime dependencies for these files. By looking at the
+contents of the binaries/target directory tree you can see how to package a
+Tuscany application in binary form for distribution to users of the application.
+
+The following subdirectories of binaries/target contain jar and war files
+for the travel sample:
+ clients - non-SCA clients using various communication technologies
+ contributions - SCA contributions for the travel sample
+ launchers - executable launchers for the travel sample
+ services - non-SCA services using various communication technologies
+ util - jar files needed by other jars in the travel sample
+ webapps - war files for the travel sample
+
+The following subdirectories of binaries/target contain runtime dependencies
+for the above files:
+ domainconfig - domain configuration files
+ jaxws - JAX-WS runtime jars neeed when running the travel sample on JDK 5
+ lib - Tuscany runtime jars and their dependencies needed by the travel sample
+ (only present if the travel sample was built using "mvn -Pselfcontained")
+ ode - JPA Derby database needed by the ODE runtime
+ openejb - OpenEJB 3.1.2 runtime jars needed by the travel sample
+
+To use the binary package to run the travel sample scenarios packaged with
+launchers, you can do the following:
+ 1. Open a command prompt.
+ 2. Change directory to travelsample/binaries/target/<runtime-dir> where
+ <runtime-dir> is the directory for the scenario shown in Table 3 below.
+ 3. Enter the command for the scenario shown in Table 3. This runs an
+ ant script that sets the necessary classpath and invokes the launcher class.
+ 4. Some scenarios require the above steps to be repeated multiple times
+ with different commands. These cases are indicated by entries in
+ Table 3 with more than one directory and command listed. For these
+ scenarios, all the listed commands should be entered in separate command
+ prompts from the listed current directories in the same order as shown.
+ 5. Some scenarios have a browser-based user interface which is started
+ by entering the URL shown in Table 3 in a browser after running the
+ launcher or launchers for the scenario. The recommended browser is
+ Firefox as some scenarios don't work with Internet Explorer.
+
+Table 3. Running scenarios with launchers from the binaries/target directory
+-------------------------------------------------------------------------------------------------------------------
+| Scenario Directory Commands URLs |
+-------------------------------------------------------------------------------------------------------------------
+| 1) Jumpstart | not available when running from binaries/target |
+-------------------------------------------------------------------------------------------------------------------
+| 2) Introducing | launchers | ant run-introducing | |
+-------------------------------------------------------------------------------------------------------------------
+| 3) Introducing | launchers | ant run-introducing-domain | |
+| (distributed) | launchers | ant run-introducing-trips | |
+| | launchers | ant run-introducing-tours | |
+| | launchers | ant run-introducing-client | |
+-------------------------------------------------------------------------------------------------------------------
+| 4) Using SCA | launchers | ant run-usingsca | |
+-------------------------------------------------------------------------------------------------------------------
+| 5) Building blocks | launchers | ant run-buildingblocks | |
+-------------------------------------------------------------------------------------------------------------------
+| 6) Interaction | launchers | ant run-interaction | |
+-------------------------------------------------------------------------------------------------------------------
+| 7) Full application | launchers | ant run-fullapp | http://localhost:8080/scatours |
+-------------------------------------------------------------------------------------------------------------------
+| 8) Full application | launchers | ant run-fullapp-domain | |
+| (distributed) | launchers | ant run-fullapp-nodes | http://localhost:8080/scatours |
+-------------------------------------------------------------------------------------------------------------------
+| 9) Callback | launchers | ant run-payment-java-callback | |
+-------------------------------------------------------------------------------------------------------------------
+| 10) Reference | launchers | ant run-payment-java-reference-pass | |
+| passing | | | |
+-------------------------------------------------------------------------------------------------------------------
+| 11) Help pages | launchers | ant run-help-pages | http://localhost:8085/help/index.html |
+-------------------------------------------------------------------------------------------------------------------
+| 12) Blog feed | launchers | ant run-blog-feed | http://localhost:8090/BlogAtom |
+| | | | http://localhost:8090/BlogRSS |
+| | | | http://localhost:8090/BlogAtomAPIs |
+| | | | http://localhost:8090/BlogRSSAPIs |
+-------------------------------------------------------------------------------------------------------------------
+| 13) Feed logger | launchers | ant run-feed-logger | |
+-------------------------------------------------------------------------------------------------------------------
+| 14) Data binding | launchers | ant run-databinding | |
+-------------------------------------------------------------------------------------------------------------------
+| 15) Policy | launchers | ant run-policy | |
+-------------------------------------------------------------------------------------------------------------------
+| 17) Payment service implementation types |
+| |
+| Impl type Directory Commands URLs |
+-------------------------------------------------------------------------------------------------------------------
+| 17a) BPEL | launchers | ant run-payment-bpel | |
+-------------------------------------------------------------------------------------------------------------------
+| 17b) Groovy | launchers | ant run-payment-groovy | |
+-------------------------------------------------------------------------------------------------------------------
+| 17c) Java | launchers | ant run-payment-java | |
+-------------------------------------------------------------------------------------------------------------------
+| 17d) Java + policy | launchers | ant run-payment-java-policy | |
+-------------------------------------------------------------------------------------------------------------------
+| 17e) Python | launchers | ant run-payment-python | |
+-------------------------------------------------------------------------------------------------------------------
+| 17f) Spring | launchers | ant run-payment-spring | |
+-------------------------------------------------------------------------------------------------------------------
+| 17g) Spring SCA tags | launchers | ant run-payment-spring-scatag | |
+-------------------------------------------------------------------------------------------------------------------
+| 18) Currency converter service binding types |
+| |
+| Binding type Directories Commands URLs |
+-------------------------------------------------------------------------------------------------------------------
+| 18a) SCA | launchers | ant run-currency-converter | |
+-------------------------------------------------------------------------------------------------------------------
+| 18b) CORBA | launchers | ant run-currency-converter-corba | |
+| | clients | ant run-currency-converter-corba | |
+-------------------------------------------------------------------------------------------------------------------
+| 18c) JMS | launchers | ant run-currency-converter-jms | |
+| | clients | ant run-currency-converter-jms | |
+-------------------------------------------------------------------------------------------------------------------
+| 18d) RMI | launchers | ant run-currency-converter-rmi | |
+| | clients | ant run-currency-converter-rmi | |
+-------------------------------------------------------------------------------------------------------------------
+| 18e) WS | launchers | ant run-currency-converter-ws | |
+| | clients | ant run-currency-converter-ws-jaxws | |
+-------------------------------------------------------------------------------------------------------------------
+| 19) Notification reference binding types |
+| |
+| Binding type Directories Commands URLs |
+-------------------------------------------------------------------------------------------------------------------
+| 19a) CORBA | services | ant run-smsgateway-corba | |
+| | launchers | ant run-notification-corba | |
+-------------------------------------------------------------------------------------------------------------------
+| 19b) EJB | services | ant run-smsgateway-ejb | |
+| | launchers | ant run-notification-ejb | |
+-------------------------------------------------------------------------------------------------------------------
+| 19c) JMS | services | ant run-smsgateway-jms | |
+| | launchers | ant run-notification-jms | |
+-------------------------------------------------------------------------------------------------------------------
+| 19d) RMI | services | ant run-smsgateway-rmi | |
+| | launchers | ant run-notification-rmi | |
+-------------------------------------------------------------------------------------------------------------------
+| 19e) WS | services | ant run-smsgateway-jaxws | |
+| | launchers | ant run-notification-ws | |
+-------------------------------------------------------------------------------------------------------------------
+
+Some scenarios are packaged as web applications and don't have launchers.
+You can run these using .war files from the binaries/target/webapps
+directory as follows:
+ 1. Deploy the web application (.war) file to a Web application server
+ such as Tomcat. The .war file can be found in the directory
+ travelsample/binaries/target/webapps and has the name listed in
+ Table 4 below.
+ 2. Display the browser-based user interface for the scenario by entering
+ its URLs in a browser. The URLs for each scenario are shown in Table 4.
+ The host and port in these URLs may need to be changed depending on the
+ configuration of the Web application server in which the web application
+ is deployed. These scenarios work in both Firefox and Internet Explorer.
+
+Table 4. Running scenarios packaged as web applications
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+| Scenario | Web application file | URLs |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+| 16) Credit card | scatours-contribution-creditcard-payment-webapp.war | http://localhost:8080/scatours-contribution-creditcard-payment-webapp |
+| webapp service | | http://localhost:8080/scatours-contribution-creditcard-payment-webapp/CreditCardPayment?wsdl |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+| 18f) Currency | scatours-contribution-currency-jsp.war | http://localhost:8080/scatours-contribution-currency-jsp |
+| converter JSP | | |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+| 18g) Currency | scatours-contribution-currency-servlet.war | http://localhost:8080/scatours-contribution-currency-servlet |
+| converter | | |
+| servlet | | |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+
+Building and running the self-contained travel sample
+-----------------------------------------------------
+
+The travel sample can be built using the "mvn -Pselfcontained" command. This
+puts all of its runtime dependencies under the binaries/target directory and
+doesn't use any files from the Tuscany SCA Java binary distribution.
+
+If the travel sample has been built in this way, you can run it as described
+in the previous section using the same ant scripts. Alternatively you can
+use the "java -jar" command to run the travel sample executable jars directly
+using the manifest dependencies in the jar files. For example, the commands
+ ant run-currency-converter-ws
+ ant run-currency-converter-ws-jaxws
+ ant run-smsgateway-corba
+could be replaced by the commands
+ java -jar scatours-launcher-currency-converter-ws.jar
+ java -jar scatours-client-currency-converter-ws-jaxws.jar
+ java -jar scatours-service-smsgateway-corba.jar
+
+
+Cross-reference of contributions to scenarios
+---------------------------------------------
+
+The following table shows which contributions are used in which scenarios.
+
+contributions/blog-feed 12
+contributions/buildingblocks 5
+contributions/buildingblocks-client 5
+contributions/calendar 6
+contributions/car 7, 8
+contributions/common 6, 7, 8, 15
+contributions/creditcard-payment-jaxb 17a, 17c, 17f, 17g, 16
+contributions/creditcard-payment-jaxb-policy 7, 8, 15, 17d
+contributions/creditcard-payment-sdo 14
+contributions/creditcard-payment-webapp 16
+contributions/currency 6, 7, 8, 18a, 18b, 18c, 18d, 18e, 18f, 18g
+contributions/currency-corba 18b
+contributions/currency-jms 18c
+contributions/currency-jsp 18f
+contributions/currency-rmi 18d
+contributions/currency-servlet 18g
+contributions/currency-ws 18e
+contributions/databinding-client 14
+contributions/emailgateway 17a, 17b, 17e
+contributions/feed-logger 13
+contributions/flight 6, 7, 8
+contributions/fullapp-bespoketrip 7, 8
+contributions/fullapp-coordination 7, 8
+contributions/fullapp-currency 7, 8
+contributions/fullapp-packagedtrip 7, 8
+contributions/fullapp-shoppingcart 7, 8
+contributions/fullapp-ui 7, 8
+contributions/help-pages 11
+contributions/hotel 7, 8
+contributions/interaction-client 6
+contributions/interaction-service-remote 6
+contributions/introducing-client 2, 3
+contributions/introducing-tours 2, 3
+contributions/introducing-trips 1, 2, 3, 5
+contributions/notification 19a, 19b, 19c, 19d, 19e
+contributions/notification-corba 19a
+contributions/notification-ejb 19b
+contributions/notification-jms 19c
+contributions/notification-rmi 19d
+contributions/notification-ws 19e
+contributions/payment-bpel 17a
+contributions/payment-bpel-process 17a
+contributions/payment-groovy 17b
+contributions/payment-java 14, 17c
+contributions/payment-java-callback 9
+contributions/payment-java-policy 8, 15, 17d
+contributions/payment-java-reference-pass 10
+contributions/payment-python 17e
+contributions/payment-spring 17f
+contributions/payment-spring-policy 7
+contributions/payment-spring-scatag 17g
+contributions/policy-client 15
+contributions/scatours 7, 8
+contributions/shoppingcart 6, 7, 8
+contributions/travelcatalog 7, 8
+contributions/trip 7, 8
+contributions/tripbooking 7, 8
+contributions/trip-policy 15
+contributions/usingsca 4
diff --git a/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/RELEASE_NOTES b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/RELEASE_NOTES new file mode 100644 index 0000000000..a4b24fb067 --- /dev/null +++ b/sca-java-1.x/tags/travelsample-1.0/distribution/src/main/release/RELEASE_NOTES @@ -0,0 +1,65 @@ +Apache Tuscany SCA Travel Sample 1.0 June 2010 Release Notes
+============================================================
+
+The Apache Tuscany SCA Travel Sample shows how Apache Tuscany SCA
+can be used in a business application.
+
+Overview
+--------
+
+The travel sample consists of a number of scenarios which demonstrate
+various aspects of SCA and Apache Tuscany in the context of a travel
+booking application. Details of these scenarios can be found in the
+travel sample README file.
+
+Unlike other Apache Tuscany SCA samples that are included in the
+Apache Tuscany SCA distribution, the travel sample is released as a
+separate package. This matches how user applications are developed
+and makes it easier for Apache Tuscany users to use the travel sample
+as a template for developing and packaging their own applications.
+
+The travel sample distribution contains source code and build files for
+the travel sample, together with binary dependencies of the travel sample
+that aren't included in the Apache Tuscany SCA Java binary distribution.
+The distribution doesn't include binaries for the travel sample because
+one of the major purposes of this sample is to show users how to build
+and run an Apache Tuscany application from source code. See the BUILDING
+and README files for details of the steps needed to do this.
+
+See the travel sample CHANGES file for a detailed list of new features
+and bug fixes in this release.
+
+Support
+-------
+
+For more information on Apache Tuscany visit the website at:
+
+ http://tuscany.apache.org/
+
+Any issues with this release can be reported to Apache Tuscany
+using the mailing lists or in the JIRA issue tracker.
+
+ Mailing list archives:
+
+ http://mail-archives.apache.org/mod_mbox/tuscany-user
+ http://mail-archives.apache.org/mod_mbox/tuscany-dev/
+
+ JIRA:
+
+ http://issues.apache.org/jira/browse/TUSCANY
+
+To join the project's mailing lists follow the instructions at:
+
+ http://tuscany.apache.org/mailing-lists.html
+
+To find out more about OASIS Open CSA go to:
+
+ http://www.oasis-opencsa.org.
+
+Apache Tuscany welcomes your help. Any contribution, including code,
+testing, improving the documentation, or bug reporting is always
+appreciated.
+
+Thank you for using Apache Tuscany!
+
+- The Tuscany Team.
|