[savara-commits] savara SVN: r106 - validator/trunk and 4 other directories.

Author: objectiser Date: 2009-12-05 17:27:21 -0500 (Sat, 05 Dec 2009) New Revision: 106 Added: validator/trunk/distribution/pom.xml validator/trunk/distribution/src/main/release/JBossORG-EULA.txt validator/trunk/distribution/src/main/release/README.txt validator/trunk/distribution/src/main/release/ReleaseNotes.txt validator/trunk/distribution/src/main/release/install/ validator/trunk/distribution/src/main/release/install/README.txt validator/trunk/distribution/src/main/release/install/build.xml validator/trunk/distribution/src/main/release/install/deployment.properties Modified: runtime/trunk/distribution/src/main/release/ReleaseNotes.txt validator/trunk/distribution/src/main/assembly/bin.xml validator/trunk/pom.xml Log: Update build for runtime and validator projects. Modified: runtime/trunk/distribution/src/main/release/ReleaseNotes.txt =================================================================== --- runtime/trunk/distribution/src/main/release/ReleaseNotes.txt 2009-12-05 13:26:44 UTC (rev 105) +++ runtime/trunk/distribution/src/main/release/ReleaseNotes.txt 2009-12-05 22:27:21 UTC (rev 106) @@ -1,58 +1,3 @@ -Overlord CDL 1.0-M2 -=================== +SAVARA Runtime 1.0-M1 +===================== -See the README.txt for more information about the Overlord CDL release. - -This is the second release of the CDL capabilities within the Overlord -"SOA Governance" project. Additional information will be made available -on the Overlord website (http://www.jboss.org/overlord/). Free free to post -questions to the User forum, or raise issues against the SOAG component -in Jira issue tracker. - -Please note: The "conversation aware ESB actions" mechanism should be -considered an alpha version only, and subject to change in future -releases. Its inclusion within this release is intended to enable the -community to experiment with the approach and hopefully provide feedback -that can be used to guide the direction of this capability. - -This "conversation aware" mechanism in M1 required state information to be -persisted for each service instance, and used by subsequent invocations of -the same service instance to understand its context within a business -transaction. However this has added a significant overhead in the implementation -and execution of the service. Therefore this M2 release introduces a lighter -weight approach. The previous M1 approach is still available and referred to -as the 'stateful' approach, whilst the new approach is referred to as -'stateless'. As the name suggests, this new approach does not require the -service to persist and use state information. The only requirement is that -it uses a few custom ESB actions that enable the behaviour of the service -to be inferred and used to check for conformance against a choreography -description. - -The same examples are available in both stateful and stateless approaches, -to enable comparison between the jboss-esb.xml definitions for each service. -Feedback on both approaches would be appreciated. - -Overlord CDL 1.0-M1 -=================== - -See the README.txt for more information about the Overlord CDL release. - -This is the initial release of the CDL capabilities within the Overlord -"SOA Governance" project. Additional information will be made available -on the Overlord website (http://www.jboss.org/overlord/). Free free to post -questions to the User forum, or raise issues against the SOAG component -in Jira issue tracker. - -Please note: The "conversation aware ESB actions" mechanism should be -considered an alpha version only, and subject to change in future -releases. Its inclusion within this release is intended to enable the -community to experiment with the approach and hopefully provide feedback -that can be used to guide the direction of this capability. - - -Overlord-CDL Development Team - ------------------------------------------------------------------------- - -The current list of outstanding problems or tasks can be obtained from -the Overlord JIRA system at: https://jira.jboss.org/jira/browse/SOAG Added: validator/trunk/distribution/pom.xml =================================================================== --- validator/trunk/distribution/pom.xml (rev 0) +++ validator/trunk/distribution/pom.xml 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,116 @@ +<!-- + * JBoss, Home of Professional Open Source + * Copyright 2008, JBoss Inc., and others contributors as indicated + * by the @authors tag. All rights reserved. + * See the copyright.txt in the distribution for a + * full listing of individual contributors. + * This copyrighted material is made available to anyone wishing to use, + * modify, copy, or redistribute it subject to the terms and conditions + * of the GNU Lesser General Public License, v. 2.1. + * This program is distributed in the hope that it will be useful, but WITHOUT A + * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A + * PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. + * You should have received a copy of the GNU Lesser General Public License, + * v.2.1 along with this distribution; if not, write to the Free Software + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, + * MA 02110-1301, USA. + * + * (C) 2008 +--> +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> + <modelVersion>4.0.0</modelVersion> + <groupId>org.jboss.savara.validator</groupId> + <artifactId>distribution</artifactId> + <packaging>pom</packaging> + <name>Savara::Validator::Distribution</name> + <version>1.0-SNAPSHOT</version> + <url>http://www.jboss.org/savara</url> + + <parent> + <groupId>org.jboss.savara</groupId> + <artifactId>validator</artifactId> + <version>1.0-SNAPSHOT</version> + <relativePath>../pom.xml</relativePath> + </parent> + + <properties> + <maven.test.skip>true</maven.test.skip> + </properties> + + <dependencies> + + <!-- + <dependency> + <groupId>org.jboss.savara.runtime</groupId> + <artifactId>savara-runtime-jbossesb</artifactId> + <version>${pom.version}</version> + </dependency> + --> + <dependency> + <groupId>org.jboss.savara.validator</groupId> + <artifactId>savara-validator-jbossesb</artifactId> + <version>${pom.version}</version> + <classifier>dist</classifier> + <type>zip</type> + </dependency> + <!-- + <dependency> + <groupId>log4j</groupId> + <artifactId>log4j</artifactId> + </dependency> + <dependency> + <groupId>org.jboss.overlord.dependencies.org.jboss.esb</groupId> + <artifactId>jbossesb-rosetta</artifactId> + </dependency> + <dependency> + <groupId>sun-jaxws</groupId> + <artifactId>jaxws-api</artifactId> + <version>2.1.1</version> + </dependency> + <dependency> + <groupId>javax.xml.bind</groupId> + <artifactId>jaxb-api</artifactId> + <version>2.1</version> + </dependency> + <dependency> + <groupId>sun-jaxws</groupId> + <artifactId>jsr181-api</artifactId> + <version>2.1.1</version> + </dependency> + --> + </dependencies> + + <build> + <resources> + <resource> + <directory>src/main/java</directory> + <includes> + <include>**/*</include> + </includes> + </resource> + </resources> + <plugins> + <plugin> + <artifactId>maven-assembly-plugin</artifactId> + <version>2.2-beta-2</version> + <executions> + <execution> + <id>bin</id> + <phase>process-resources</phase> + <goals> + <goal>single</goal> + </goals> + <configuration> + <finalName>savara-validator-${project.version}</finalName> + <appendAssemblyId>false</appendAssemblyId> + <descriptors> + <descriptor>src/main/assembly/bin.xml</descriptor> + </descriptors> + </configuration> + </execution> + </executions> + </plugin> + </plugins> + </build> + +</project> Modified: validator/trunk/distribution/src/main/assembly/bin.xml =================================================================== --- validator/trunk/distribution/src/main/assembly/bin.xml 2009-12-05 13:26:44 UTC (rev 105) +++ validator/trunk/distribution/src/main/assembly/bin.xml 2009-12-05 22:27:21 UTC (rev 106) @@ -43,6 +43,12 @@ <outputDirectory>/install</outputDirectory> </fileSet> + <!-- copy documents --> + <fileSet> + <directory>../docs/samplesguide/target/docbook/publish/en-US</directory> + <outputDirectory>docs/samplesguide</outputDirectory> + </fileSet> + <!-- copy samples --> <fileSet> @@ -51,6 +57,8 @@ </fileSet> <!-- Copy the cdl model for examples --> + + <!-- <fileSet> <directory>../samples/jbossesb/brokerage/models</directory> <outputDirectory>samples/models/brokerage</outputDirectory> @@ -82,6 +90,7 @@ <directory>../samples/jbossesb/common/creditAgency/src</directory> <outputDirectory>samples/common/creditAgency/src</outputDirectory> </fileSet> + --> <!-- copy client & trailblazer example--> <fileSet> @@ -97,7 +106,7 @@ <outputDirectory>modules</outputDirectory> <unpack>true</unpack> <includes> - <include>org.jboss.savara.runtime:savara-runtime-jbossesb:zip:dist</include> + <include>org.jboss.savara.validator:savara-validator-jbossesb:zip:dist</include> </includes> </dependencySet> @@ -107,6 +116,7 @@ need to explicitly refer to each Jar in the .classpath file, so removing the version from the name avoids having to find a way to automatically update the .classpath file --> + <!-- <dependencySet> <outputDirectory>samples/brokerage/broker/lib</outputDirectory> <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping> @@ -146,7 +156,7 @@ <include>sun-jaxws:jsr181-api</include> </includes> </dependencySet> - + --> </dependencySets> </assembly> Added: validator/trunk/distribution/src/main/release/JBossORG-EULA.txt =================================================================== --- validator/trunk/distribution/src/main/release/JBossORG-EULA.txt (rev 0) +++ validator/trunk/distribution/src/main/release/JBossORG-EULA.txt 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,107 @@ +LICENSE AGREEMENT +JBOSS(r) + +This License Agreement governs the use of the Software Packages and any updates to the Software +Packages, regardless of the delivery mechanism. Each Software Package is a collective work +under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to +the user ("Client") a license to the applicable collective work(s) pursuant to the +GNU Lesser General Public License v. 2.1 except for the following Software Packages: +(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to the +GNU General Public License v.2; + +(b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0; + +(c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensed under the +(open source) Sleepycat License (if Client does not wish to use the open source version of this database, +it may purchase a license from Sleepycat Software); + +and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1, +and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter various +royalty-free patent licenses. + +Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php. + +1. The Software. "Software Packages" refer to the various software modules that are created and made available +for distribution by the JBoss.org open source community at http://www.jboss.org. Each of the Software Packages +may be comprised of hundreds of software components. The end user license agreement for each component is located in +the component's source code. With the exception of certain image files identified in Section 2 below, +the license terms for the components permit Client to copy, modify, and redistribute the component, +in both source code and binary code forms. This agreement does not limit Client's rights under, +or grant Client rights that supersede, the license terms of any particular component. + +2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and are protected under copyright +and other laws. Title to the Software Packages and any component, or to any copy, modification, or merged portion shall +remain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat" trademark, the +individual Software Package trademarks, and the "Shadowman" logo are registered trademarks of Red Hat and its affiliates +in the U.S. and other countries. This agreement permits Client to distribute unmodified copies of the Software Packages +using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's +trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by +these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified. +If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at +http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted. +Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages. + +3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particular +component, to the maximum extent permitted under applicable law, the Software Packages and the +components are provided and licensed "as is" without warranty of any kind, expressed or implied, +including the implied warranties of merchantability, non-infringement or fitness for a particular purpose. +Red Hat warrants that the media on which Software Packages may be furnished will be free from defects in +materials and manufacture under normal use for a period of 30 days from the date of delivery to Client. +Red Hat does not warrant that the functions contained in the Software Packages will meet Client's requirements +or that the operation of the Software Packages will be entirely error free or appear precisely as described +in the accompanying documentation. This warranty extends only to the party that purchases the Services +pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor. + +4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies +described below are accepted by Client as its only remedies. Red Hat's entire liability, and Client's +exclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days of +delivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it or +refund the money paid by Client for the Software. To the maximum extent permitted by applicable law, +Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequential +damages, including lost profits or lost savings arising out of the use or inability to use the Software, +even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall +Red Hat's liability under this agreement exceed the amount that Client paid to Red Hat under this +Agreement during the twelve months preceding the action. + +5. Export Control. As required by U.S. law, Client represents and warrants that it: +(a) understands that the Software Packages are subject to export controls under the +U.S. Commerce Department's Export Administration Regulations ("EAR"); + +(b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations +(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); + +(c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity, +or individual without the necessary export license(s) or authorizations(s) from the U.S. Government; + +(d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical or +biological weapons, or missile technology end-uses unless authorized by the U.S. Government by +regulation or specific license; + +(e) understands and agrees that if it is in the United States and exports or transfers the Software +Packages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual +reports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name and +address (including country) of each transferee; + +and (f) understands that countries other than the United States may restrict the import, use, or +export of encryption products and that it shall be solely responsible for compliance with any such +import, use, or export restrictions. + +6. Third Party Programs. Red Hat may distribute third party software programs with the Software Packages +that are not part of the Software Packages and which Client must install separately. These third party +programs are subject to their own license terms. The license terms either accompany the programs or +can be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicable +license terms for such programs, then Client may not install them. If Client wishes to install the programs +on more than one system or transfer the programs to another party, then Client must contact the licensor +of the programs. + +7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the +enforceability of the remaining provisions. This License Agreement shall be governed by the laws of the +State of North Carolina and of the United States, without regard to any conflict of laws provisions, +except that the United Nations Convention on the International Sale of Goods shall not apply. + +Copyright 2006 Red Hat, Inc. All rights reserved. +"JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc. +All other trademarks are the property of their respective owners. + + Page 1 of 1 18 October 2006 + Added: validator/trunk/distribution/src/main/release/README.txt =================================================================== --- validator/trunk/distribution/src/main/release/README.txt (rev 0) +++ validator/trunk/distribution/src/main/release/README.txt 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,13 @@ +SAVARA Validator README +======================= + +Please refer to the README.txt in the 'install' folder for instructions on +how to install the SAVARA Validator capabilities into the JBossESB environment. + +For more information concerning the use and configuraton of service validation, please refer +to the Getting Started Guide and User Guide associated with the SAVARA Eclipse Tools for +more information. + +The Samples Guide in the docs folder explains how to run some examples demonstrating +the validation of ESB services against a choreography description. + Added: validator/trunk/distribution/src/main/release/ReleaseNotes.txt =================================================================== --- validator/trunk/distribution/src/main/release/ReleaseNotes.txt (rev 0) +++ validator/trunk/distribution/src/main/release/ReleaseNotes.txt 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,3 @@ +SAVARA Validator 1.0-M1 +======================= + Added: validator/trunk/distribution/src/main/release/install/README.txt =================================================================== --- validator/trunk/distribution/src/main/release/install/README.txt (rev 0) +++ validator/trunk/distribution/src/main/release/install/README.txt 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,20 @@ +Installation instructions for SAVARA Validator +============================================== + +1) Download JBossAS (http://www.jboss.org/jbossas) - version 5.1.0.GA or higher. Follow the installation +instructions that accompany this distribution. + +2) Download JBossESB (http://www.jboss.org/jbossesb) - version 4.7 or higher. Follow the installation +instructions that accompany this distribution, on how to install the ESB into the JBossAS environment. + +3) Edit the deployment.properties file in this ${SAVARA-Validator}/install folder. Set the org.jboss.as.home +property to the root directory where the JBossAS environment is located, and change the +org.jboss.as.config property from default if you wish to start your JBossAS using a different +configuration. + +4) Start a command window and execute the command 'ant deploy'. + +5) You should now start your JBossAS server. + +When you wish to uninstall this component, simply go back to the ${SAVARA-Validator}/install folder +and execute the command 'ant undeploy'. Added: validator/trunk/distribution/src/main/release/install/build.xml =================================================================== --- validator/trunk/distribution/src/main/release/install/build.xml (rev 0) +++ validator/trunk/distribution/src/main/release/install/build.xml 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,39 @@ +<project name="SAVARA_Validator_Installer" default="deploy" basedir="."> + + <!-- Set deployment properties filename --> + <property name="org.jboss.as.deployment.properties" location="deployment.properties"/> + + <!-- Load Build Properties File --> + <property file="${org.jboss.as.deployment.properties}"/> + + <property name="server.dir" value="${org.jboss.as.home}/server/${org.jboss.as.config}"/> + <property name="conf.dir" value="${server.dir}/conf"/> + <property name="deploy.dir" value="${server.dir}/deploy"/> + <property name="server.lib.dir" value="${server.dir}/lib"/> + + <property name="modules" value="../modules" /> + + <target name="check.deploy.props"> + <condition property="as.configured"> + <and> + <isset property="org.jboss.as.home"/> + <isset property="org.jboss.as.config"/> + </and> + </condition> + + <fail unless="as.configured" message="Cannot determine target deployment, please check deployment.properties"/> + </target> + + <target name="deploy" description="Deploys SAVARA Validator to the server"> + <echo message="Deploy SAVARA Validator to JBoss AS/ESB server" /> + <copy todir="${deploy.dir}/savara-validator-jbossesb.esb"> + <fileset dir="${modules}/savara-validator-jbossesb.esb"/> + </copy> + </target> + + <target name="undeploy" description="Undeploys SAVARA Validator"> + <echo message="Undeploy the SAVARA Validator from JBoss AS/ESB server" /> + <delete dir="${deploy.dir}/savara-validator-jbossesb.esb" /> + </target> + +</project> Added: validator/trunk/distribution/src/main/release/install/deployment.properties =================================================================== --- validator/trunk/distribution/src/main/release/install/deployment.properties (rev 0) +++ validator/trunk/distribution/src/main/release/install/deployment.properties 2009-12-05 22:27:21 UTC (rev 106) @@ -0,0 +1,19 @@ +###################################################################### +# JBossAS Configuration +###################################################################### +# The Directory in Which JBoss AS is Installed +# The absolute path to a directory in which a version of JBoss AS with +# EJB3 has been installed. +# This path should not include spaces. +# Use of relative paths or paths with spaces will cause runtime errors +# when deploying and executing the samples. +# (e.g. /local/deploy/jboss-5.1.0.GA) +org.jboss.as.home=/local/deploy/jboss-5.1.0.GA + +# The Configuration of JBoss AS to Use +# (e.g. default) +org.jboss.as.config=default + +# The directory for JBossESB home +# (e.g. /local/deploy/jbossesb-4.7) +org.jboss.esb.home=/local/deploy/jbossesb-4.7 Modified: validator/trunk/pom.xml =================================================================== --- validator/trunk/pom.xml 2009-12-05 13:26:44 UTC (rev 105) +++ validator/trunk/pom.xml 2009-12-05 22:27:21 UTC (rev 106) @@ -40,7 +40,7 @@ <module>jbossesb</module> <!-- module>samples</module --> <module>docs</module> - <!-- module>distribution</module --> + <module>distribution</module> </modules> <profiles>