savara SVN: r109 - tools/eclipse/trunk/docs/gettingstartedguide/src/main/module.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2009-12-05 19:00:41 -0500 (Sat, 05 Dec 2009)
New Revision: 109
Modified:
tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml
Log:
Added message and schema validation.
Modified: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml
===================================================================
--- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml 2009-12-05 23:23:10 UTC (rev 108)
+++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml 2009-12-06 00:00:41 UTC (rev 109)
@@ -10,8 +10,51 @@
<section>
<title>Define Information Model</title>
+ <para>
+ One of the stages within the architecture phase is to define the information model
+ for the message types associated with the messages exchanges between the
+ interacting participants.
+ </para>
+
+ <para>
+ This involves defining message schema for each example message. The schema could
+ already exist and be reused, it could be based on existing schema and just need
+ to be upgraded to support new requirements, or it may need to be defined from
+ scratch.
+ </para>
+
+ <para>
+ An example of a schema associated with the purchasing model is the
+ <filename>store.xsd</filename> shown here:
+ </para>
+
<informalexample>
<programlisting role="XML" ><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://www.jboss.org/examples/store"
+ xmlns:tns="http://www.jboss.org/examples/store"
+ elementFormDefault="qualified">
+
+ <element name="BuyRequest" type="tns:StoreType"></element>
+ <element name="BuyConfirmed" type="tns:StoreType"></element>
+ <element name="BuyFailed" type="tns:StoreType"></element>
+
+ <complexType name="StoreType">
+ <attribute name="id" type="string"></attribute>
+ </complexType>
+</schema>
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ Once the schema has been defined, then the example messages need to be updated
+ to reference the schema, as shown in the following <filename>BuyRequest.xml</filename>
+ example message:
+ </para>
+
+ <informalexample>
+ <programlisting role="XML" ><
Hudson build completed: savara-eclipse-tool #2
by jboss-qa-internal＠redhat.com
See http://hudson.qa.jboss.com/hudson/job/savara-eclipse-tool/2/changes
14 years, 5 months
- 1
- 0
savara SVN: r107 - in tools/eclipse/trunk: distribution and 4 other directories.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2009-12-05 17:55:46 -0500 (Sat, 05 Dec 2009)
New Revision: 107
Added:
tools/eclipse/trunk/distribution/
tools/eclipse/trunk/distribution/pom.xml
tools/eclipse/trunk/distribution/src/
tools/eclipse/trunk/distribution/src/main/
tools/eclipse/trunk/distribution/src/main/assembly/
tools/eclipse/trunk/distribution/src/main/assembly/bin.xml
tools/eclipse/trunk/distribution/src/main/release/
tools/eclipse/trunk/distribution/src/main/release/JBossORG-EULA.txt
tools/eclipse/trunk/distribution/src/main/release/README.txt
tools/eclipse/trunk/distribution/src/main/release/ReleaseNotes.txt
Modified:
tools/eclipse/trunk/pom.xml
Log:
Update build scripts.
Added: tools/eclipse/trunk/distribution/pom.xml
===================================================================
--- tools/eclipse/trunk/distribution/pom.xml (rev 0)
+++ tools/eclipse/trunk/distribution/pom.xml 2009-12-05 22:55:46 UTC (rev 107)
@@ -0,0 +1,76 @@
+<!--
+ * 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.tools.eclipse</groupId>
+ <artifactId>distribution</artifactId>
+ <packaging>pom</packaging>
+ <name>Savara::Tools::Eclipse::Distribution</name>
+ <version>1.0-SNAPSHOT</version>
+ <url>http://www.jboss.org/savara</url>
+
+ <parent>
+ <groupId>org.jboss.savara.tools</groupId>
+ <artifactId>eclipse</artifactId>
+ <version>1.0-SNAPSHOT</version>
+ <relativePath>../pom.xml</relativePath>
+ </parent>
+
+ <properties>
+ <maven.test.skip>true</maven.test.skip>
+ </properties>
+
+ <dependencies>
+ </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-tools-eclipse-${project.version}</finalName>
+ <appendAssemblyId>false</appendAssemblyId>
+ <descriptors>
+ <descriptor>src/main/assembly/bin.xml</descriptor>
+ </descriptors>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+
+</project>
Added: tools/eclipse/trunk/distribution/src/main/assembly/bin.xml
===================================================================
--- tools/eclipse/trunk/distribution/src/main/assembly/bin.xml (rev 0)
+++ tools/eclipse/trunk/distribution/src/main/assembly/bin.xml 2009-12-05 22:55:46 UTC (rev 107)
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ * 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
+-->
+<assembly>
+ <!-- id typically identifies the "type" (src vs bin etc) of the assembly -->
+ <id>bin</id>
+ <includeBaseDirectory>true</includeBaseDirectory>
+ <formats>
+ <format>zip</format>
+ </formats>
+
+ <fileSets>
+
+ <!--Copy files like License and samples etc -->
+ <fileSet>
+ <directory>src/main/release</directory>
+ <outputDirectory>/</outputDirectory>
+ <includes>
+ <include>*.txt</include>
+ <include>*.properties</include>
+ </includes>
+ </fileSet>
+
+ <!-- copy documents -->
+ <fileSet>
+ <directory>../docs/userguide/target/docbook/publish/en-US</directory>
+ <outputDirectory>docs/userguide</outputDirectory>
+ </fileSet>
+
+ <fileSet>
+ <directory>../docs/gettingstartedguide/target/docbook/publish/en-US</directory>
+ <outputDirectory>docs/gettingstartedguide</outputDirectory>
+ </fileSet>
+
+ <!-- End of copying documents -->
+
+ </fileSets>
+
+ <dependencySets>
+
+ </dependencySets>
+
+</assembly>
Added: tools/eclipse/trunk/distribution/src/main/release/JBossORG-EULA.txt
===================================================================
--- tools/eclipse/trunk/distribution/src/main/release/JBossORG-EULA.txt (rev 0)
+++ tools/eclipse/trunk/distribution/src/main/release/JBossORG-EULA.txt 2009-12-05 22:55:46 UTC (rev 107)
@@ -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: tools/eclipse/trunk/distribution/src/main/release/README.txt
===================================================================
--- tools/eclipse/trunk/distribution/src/main/release/README.txt (rev 0)
+++ tools/eclipse/trunk/distribution/src/main/release/README.txt 2009-12-05 22:55:46 UTC (rev 107)
@@ -0,0 +1,8 @@
+SAVARA Tools Eclipse README
+===========================
+
+A Getting Started Guide and User Guide can be found in the docs folder.
+
+The Getting Started Guide is intended to provide an overview of how the Eclipse
+tools, and other SAVARA modules, can be used to develop a "Testable Architecture".
+
Added: tools/eclipse/trunk/distribution/src/main/release/ReleaseNotes.txt
===================================================================
--- tools/eclipse/trunk/distribution/src/main/release/ReleaseNotes.txt (rev 0)
+++ tools/eclipse/trunk/distribution/src/main/release/ReleaseNotes.txt 2009-12-05 22:55:46 UTC (rev 107)
@@ -0,0 +1,3 @@
+SAVARA Tools Eclipse 1.0-M1
+===========================
+
Modified: tools/eclipse/trunk/pom.xml
===================================================================
--- tools/eclipse/trunk/pom.xml 2009-12-05 22:27:21 UTC (rev 106)
+++ tools/eclipse/trunk/pom.xml 2009-12-05 22:55:46 UTC (rev 107)
@@ -38,6 +38,7 @@
</developers>
<modules>
<module>docs</module>
+ <module>distribution</module>
</modules>
<build>
14 years, 5 months
- 1
- 0
Build failed in Hudson: savara-validator #1
by jboss-qa-internal＠redhat.com
See http://hudson.qa.jboss.com/hudson/job/savara-validator/1/
------------------------------------------
[...truncated 1537 lines...]
773/883K
774/883K
775/883K
776/883K
778/883K
779/883K
780/883K
782/883K
783/883K
784/883K
786/883K
787/883K
789/883K
790/883K
791/883K
792/883K
793/883K
795/883K
796/883K
797/883K
799/883K
800/883K
802/883K
803/883K
805/883K
806/883K
807/883K
808/883K
809/883K
811/883K
812/883K
813/883K
815/883K
816/883K
817/883K
818/883K
819/883K
821/883K
823/883K
824/883K
825/883K
827/883K
828/883K
829/883K
831/883K
832/883K
833/883K
834/883K
835/883K
837/883K
839/883K
840/883K
841/883K
843/883K
844/883K
845/883K
847/883K
848/883K
849/883K
851/883K
852/883K
853/883K
855/883K
856/883K
857/883K
859/883K
860/883K
861/883K
863/883K
864/883K
865/883K
867/883K
868/883K
869/883K
870/883K
872/883K
873/883K
874/883K
876/883K
877/883K
878/883K
880/883K
881/883K
883/883K
883K downloaded
[INFO] [compiler:compile]
[INFO] Compiling 16 source files to /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/classes
[INFO] [resources:testResources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/src/test/resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb-1.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: dist}]
[INFO] Reading assembly descriptor: src/main/configs/esb-assembly.xml
[INFO] Processing DependencySet (output=/)
[INFO] Building zip: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb.esb-dist.zip
[INFO] Preparing javadoc:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [javadoc:jar {execution: generate-javadoc}]
Creating destination directory: "/qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/"
Loading source files for package org.jboss.savara.validator.jbossesb.pi4soa...
Loading source files for package org.jboss.savara.validator.jbossesb...
Constructing Javadoc information...
Standard Doclet version 1.6.0_11
Building tree for all the packages and classes...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//Pi4SOAServiceRecorder.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//Pi4SOAServiceValidator.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//Pi4SOAValidatorConfigLoader.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//ValidatorConfigGenerator.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//ValidatorConfigGenerator.InputOutputAnalyser.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//AbstractServiceValidator.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//DefaultValidatorConfig.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//Endpoint.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ESBUtil.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ServiceValidator.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ServiceValidatorFactory.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ServiceValidatorManager.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ServiceValidatorManager.DynamicReplyToEndpointManager.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ServiceValidatorManager.ValidatorConfigChangeMonitor.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ValidatorConfig.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ValidatorConfigFactory.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ValidatorConfigLoader.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ValidatorFilter.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//ValidatorName.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/overview-frame.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//package-frame.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//package-summary.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb//package-tree.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//package-frame.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//package-summary.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/org/jboss/savara/validator/jbossesb/pi4soa//package-tree.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/constant-values.html...
Building index for all the packages and classes...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/overview-tree.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/index-all.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/deprecated-list.html...
Building index for all classes...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/allclasses-frame.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/allclasses-noframe.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/index.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/overview-summary.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/help-doc.html...
Generating /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/javadoc/stylesheet.css...
Graphviz Executable: dot
4 warnings
[INFO] Javadoc Warnings
[WARNING] /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/src/main/java/org/jboss/savara/validator/jbossesb/DefaultValidatorConfig.java:34: warning - @param argument "modeType" is not a parameter name.
[WARNING] /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/src/main/java/org/jboss/savara/validator/jbossesb/ValidatorName.java:44: warning - @param argument "validate" is not a parameter name.
[WARNING] javadoc: warning - Graphviz is not found in the system path.
[WARNING] javadoc: warning - Skipping diagram generation.
[INFO] Building jar: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb-1.0-SNAPSHOT-javadoc.jar
[INFO] NOT adding javadoc to attached artifacts list.
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb-1.0-SNAPSHOT-sources.jar
[INFO] [install:install]
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb-1.0-SNAPSHOT.jar to /home/hudson/.m2/repository/org/jboss/savara/validator/savara-validator-jbossesb/1.0-SNAPSHOT/savara-validator-jbossesb-1.0-SNAPSHOT.jar
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb.esb-dist.zip to /home/hudson/.m2/repository/org/jboss/savara/validator/savara-validator-jbossesb/1.0-SNAPSHOT/savara-validator-jbossesb-1.0-SNAPSHOT-dist.zip
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/jbossesb/target/savara-validator-jbossesb-1.0-SNAPSHOT-sources.jar to /home/hudson/.m2/repository/org/jboss/savara/validator/savara-validator-jbossesb/1.0-SNAPSHOT/savara-validator-jbossesb-1.0-SNAPSHOT-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Validator::Docs
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] [install:install]
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/pom.xml to /home/hudson/.m2/repository/org/jboss/savara/validator/docs/1.0-SNAPSHOT/docs-1.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Validator::Docs::SamplesGuide
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [jdocbook:resources]
[INFO] unpacking dependency resource [/home/hudson/.m2/repository/org/jboss/jbossorg-jdocbook-style/1.1.0/jbossorg-jdocbook-style-1.1.0.jdocbook-style] to staging-dir [/qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/docbook/staging]
[INFO] Expanding: /home/hudson/.m2/repository/org/jboss/jbossorg-jdocbook-style/1.1.0/jbossorg-jdocbook-style-1.1.0.jdocbook-style into /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/docbook/staging
[INFO] [jdocbook:generate]
Dec 5, 2009 5:32:28 PM org.apache.fop.hyphenation.Hyphenator getHyphenationTree
SEVERE: Couldn't find hyphenation pattern en
Dec 5, 2009 5:32:31 PM org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: -1/-1)
[INFO] [jdocbook:bundle]
[INFO] Building jar: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/classes/samplesguide-1.0-SNAPSHOT.war
[INFO] [jdocbook:resources {execution: generate-docbook}]
[INFO] unpacking dependency resource [/home/hudson/.m2/repository/org/jboss/jbossorg-jdocbook-style/1.1.0/jbossorg-jdocbook-style-1.1.0.jdocbook-style] to staging-dir [/qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/docbook/staging]
[INFO] Expanding: /home/hudson/.m2/repository/org/jboss/jbossorg-jdocbook-style/1.1.0/jbossorg-jdocbook-style-1.1.0.jdocbook-style into /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/docbook/staging
[INFO] [jdocbook:generate {execution: generate-docbook}]
Dec 5, 2009 5:32:52 PM org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: -1/-1)
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/samplesguide-1.0-SNAPSHOT-sources.jar
[INFO] [install:install]
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/classes/samplesguide-1.0-SNAPSHOT.war to /home/hudson/.m2/repository/org/jboss/savara/validator/docs/samplesguide/1.0-SNAPSHOT/samplesguide-1.0-SNAPSHOT.jdocbook
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/docs/samplesguide/target/samplesguide-1.0-SNAPSHOT-sources.jar to /home/hudson/.m2/repository/org/jboss/savara/validator/docs/samplesguide/1.0-SNAPSHOT/samplesguide-1.0-SNAPSHOT-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Validator::Distribution
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [assembly:single {execution: bin}]
[INFO] Reading assembly descriptor: src/main/assembly/bin.xml
[INFO] Processing DependencySet (output=modules)
[WARNING] Cannot include project artifact: org.jboss.savara.validator:distribution:pom:1.0-SNAPSHOT; it doesn't have an associated file or directory.
[INFO] Building zip: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/distribution/target/savara-validator-1.0-SNAPSHOT.zip
[WARNING] Configuration options: 'appendAssemblyId' is set to false, and 'classifier' is missing.
Instead of attaching the assembly file: /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/distribution/target/savara-validator-1.0-SNAPSHOT.zip, it will become the file for main project artifact.
NOTE: If multiple descriptors or descriptor-formats are provided for this project, the value of this file will be non-deterministic!
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] [install:install]
[INFO] Installing /qa/services/hudson/hudson_workspace/workspace/savara-validator/validator/distribution/pom.xml to /home/hudson/.m2/repository/org/jboss/savara/validator/distribution/1.0-SNAPSHOT/distribution-1.0-SNAPSHOT.pom
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] Savara::Validator ..................................... SUCCESS [9.339s]
[INFO] Savara::Validator::JBoss ESB .......................... SUCCESS [34.519s]
[INFO] Savara::Validator::Docs ............................... SUCCESS [0.054s]
[INFO] Savara::Validator::Docs::SamplesGuide ................. SUCCESS [55.938s]
[INFO] Savara::Validator::Distribution ....................... SUCCESS [1.360s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 43 seconds
[INFO] Finished at: Sat Dec 05 17:33:02 EST 2009
[INFO] Final Memory: 52M/350M
[INFO] ------------------------------------------------------------------------
Archiving artifacts
Recording test results
No test report files were found. Configuration error?
14 years, 5 months
- 1
- 1
savara-validator - Build # 1 - Failure!
by jboss-qa-internal＠redhat.com
savara-validator - Build # 1 - Failure:
Check console output at http://hudson.qa.jboss.com/hudson/job/savara-validator/1/ to view the results.
14 years, 5 months
- 1
- 0
savara SVN: r106 - validator/trunk and 4 other directories.
by do-not-reply＠jboss.org
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>
14 years, 5 months
- 1
- 0
Hudson build completed: savara-runtime #1
by jboss-qa-internal＠redhat.com
See http://hudson.qa.jboss.com/hudson/job/savara-runtime/1/
14 years, 5 months
- 1
- 0
savara SVN: r105 - in tools/eclipse/trunk/docs/gettingstartedguide/src/main: module and 1 other directory.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2009-12-05 08:26:44 -0500 (Sat, 05 Dec 2009)
New Revision: 105
Added:
tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml
Modified:
tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml
tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml
Log:
Update to structure of getting started guide.
Modified: tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml
===================================================================
--- tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml 2009-12-05 12:46:40 UTC (rev 104)
+++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml 2009-12-05 13:26:44 UTC (rev 105)
@@ -14,6 +14,7 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/installation.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/businessanalysis.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/architecture.xml"/>
<!-- xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/serviceanalysisdesign.xml"/ -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/servicedev.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/runtimevalidation.xml"/>
Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml
===================================================================
--- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml (rev 0)
+++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml 2009-12-05 13:26:44 UTC (rev 105)
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="architecture">
+ <title>Architecture</title>
+
+ <para>
+ </para>
+
+ <section>
+ <title>Define Information Model</title>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+<tns:BuyRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:tns="http://www.jboss.org/examples/store"
+ xsi:schemaLocation="http://www.jboss.org/examples/store store.xsd "
+ id="1" />
+ ]]></programlisting>
+ </informalexample>
+
+ <section>
+ <title>Validating Example Messages against Schema</title>
+
+ <para>
+ </para>
+ </section>
+ </section>
+
+ <section>
+ <title>Define Choreography Model</title>
+
+ <para>
+The next step in the development process is to specify a Choreography Model to implement
+the requirements described within the set of scenarios.
+ </para>
+
+ <para>
+The current representation used to define Choreography Models within SAVARA is the W3C Web Service
+Choreography Description Language (WS-CDL). The pi4soa tools provide a WS-CDL (or choreography
+description) editor. Although this standard is associated with web services, it does not mean
+that a system specified using this standard needs to be implemented using web services. The
+actual WS-CDL language is used for defining the interactions between any distributed system.
+ </para>
+
+ <para>
+The choreography description for the Purchasing example can be found in
+<filename>purchasing-models/PurchaseGoods.cdm</filename>. When the
+choreography editor has been launched, by double-clicking on this file within the Eclipse
+environment, then navigate to the <emphasis>Choreography Flows</emphasis> tab to see the
+definition of the purchasing process:
+ </para>
+
+ <imageobject>
+ <imagedata fileref="images/PurchaseGoods.jpg" align="center" width="5in" />
+ </imageobject>
+
+ <section>
+ <title>Validating Requirements against Choreography Model</title>
+
+ <para>
+The pi4soa tools can be used to test the scenarios against the choreography description, to
+ensure that the choreography correctly implements the requirements. To test the
+<filename>SuccessfulPurchase.scn</filename> scenario against the choreography, launch
+the scenario editor by double-clicking on the scenario file, and then pressing the
+green <emphasis>play</emphasis> button in the toolbar. When complete, the scenario
+should look like the following image, indicating that the scenario completed successfully.
+ </para>
+
+ <imageobject>
+ <imagedata fileref="images/SuccessfulPurchasePostTest.jpg" align="center" width="5in" />
+ </imageobject>
+
+ <para>
+To view a scenario that demonstrates a test failure, open the
+<filename>InvalidPurchase.scn</filename> scenario by double-clicking on the file, and
+then initiate the test using the green <emphasis>play</emphasis> button in the toolbar.
+When complete, the scenario should look like the following image.
+ </para>
+
+ <imageobject>
+ <imagedata fileref="images/InvalidPurchasePostTest.jpg" align="center" width="5in" />
+ </imageobject>
+
+ <para>
+You will notice that the <emphasis>Store</emphasis> participant has a red 'send' node,
+indicating that this action was not expected behaviour when compared with the choreography
+description. The reason this is considered an error, is that the <emphasis>Store</emphasis>
+participant should only send a <emphasis>BuyFailed</emphasis> message following an invalid
+credit check.
+ </para>
+
+ <para>
+When an error is detected in a scenario, the choreography designer can then determine whether
+the scenario is wrong (i.e. it does not correctly describe a business requirement), or whether
+the choreography is wrong and needs to be updated to accomodate the scenario.
+ </para>
+ </section>
+
+ <section>
+ <title>Create Documentation</title>
+
+ <para>
+Once the choreography description has been successfully tested against the scenarios, the
+next step may be to obtain approval to proceed to the analysis/design phase. To help support
+this effort, the pi4soa tools provide the means to export the choreography description to
+a range of representations (e.g. BPMN, UML or HTML documentation
+<emphasis>TO BE CONFIRMED</emphasis>).
+ </para>
+ </section>
+ </section>
+
+</chapter>
Modified: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml
===================================================================
--- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml 2009-12-05 12:46:40 UTC (rev 104)
+++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml 2009-12-05 13:26:44 UTC (rev 105)
@@ -6,9 +6,26 @@
<para>
</para>
+
+ <section>
+ <title>Define Participants</title>
+
+ <para>
+ In the current Eclipse tools, that use the pi4soa Scenario and Choreography based
+ models for defining requirements and architectural models, this phase would be
+ achieved by defining the Participants and Roles within the choreography model.
+ </para>
+
+ <para>
+ Only these components need to be specified in the choreography model. This enables
+ them to be referenced in the subsequently defined scenarios. Otherwise it would be
+ necessary to return to the scenarios, once the choreography model had been defined
+ in the <emphasis>Architecture</emphasis> phase.
+ </para>
+ </section>
<section>
- <title>Defining Requirements</title>
+ <title>Outline Scenarios</title>
<para>
When designing a system, it is necessary to capture requirements. Various approaches can be
@@ -39,83 +56,41 @@
</section>
<section>
- <title>Creating a Global Model</title>
-
- <para>
-The next step in the development process is to specific a Global Model to implement
-the requirements described within the set of scenarios.
- </para>
+ <title>Create Example Messages</title>
<para>
-The current representation used to define Global Models within SAVARA is the W3C Web Service
-Choreography Description Language (WS-CDL). The pi4soa tools provide a WS-CDL (or choreography
-description) editor. Although this standard is associated with web services, it does not mean
-that a system specified using this standard needs to be implemented using web services. The
-actual WS-CDL language is used for defining the interactions between any distributed system.
+ The next step is to create the example messages required by the scenarios.
</para>
<para>
-The choreography description for the Purchasing example can be found in
-<filename>purchasing-models/PurchaseGoods.cdm</filename>. When the
-choreography editor has been launched, by double-clicking on this file within the Eclipse
-environment, then navigate to the <emphasis>Choreography Flows</emphasis> tab to see the
-definition of the purchasing process:
+ Some previously defined examples can be found in the <filename>process-models</filename>
+ Eclipse project. For example, the Buy request is defined as:
</para>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+<tns:BuyRequest xmlns:tns="http://www.jboss.org/examples/store"
+ id="1" />
+ ]]></programlisting>
+ </informalexample>
- <imageobject>
- <imagedata fileref="images/PurchaseGoods.jpg" align="center" width="5in" />
- </imageobject>
-
- </section>
-
- <section>
- <title>Validating Requirements against Global Model</title>
-
<para>
-The pi4soa tools can be used to test the scenarios against the choreography description, to
-ensure that the choreography correctly implements the requirements. To test the
-<filename>SuccessfulPurchase.scn</filename> scenario against the choreography, launch
-the scenario editor by double-clicking on the scenario file, and then pressing the
-green <emphasis>play</emphasis> button in the toolbar. When complete, the scenario
-should look like the following image, indicating that the scenario completed successfully.
+ Although a schema may not have been defined at this stage, unless one previously
+ existed that is being reused, it is a good idea to define a namespace for the
+ message type. This is because it will be used within the scenarios and
+ architectural models defined in the following stage. If the namespace was not
+ specified at this stage, then the example messages, scenarios and architectural
+ models would need to be updated at a later stage.
</para>
-
- <imageobject>
- <imagedata fileref="images/SuccessfulPurchasePostTest.jpg" align="center" width="5in" />
- </imageobject>
-
+
<para>
-To view a scenario that demonstrates a test failure, open the
-<filename>InvalidPurchase.scn</filename> scenario by double-clicking on the file, and
-then initiate the test using the green <emphasis>play</emphasis> button in the toolbar.
-When complete, the scenario should look like the following image.
+ Although this phase has been defined following the definition of the scenarios,
+ in practice these phases are iterative. So scenarios and example messages would be
+ defined concurrently. Similarly, new participants may be added in an evolutionary
+ manner, as scenarios are created that require them.
</para>
-
- <imageobject>
- <imagedata fileref="images/InvalidPurchasePostTest.jpg" align="center" width="5in" />
- </imageobject>
-
- <para>
-You will notice that the <emphasis>Store</emphasis> participant has a red 'send' node,
-indicating that this action was not expected behaviour when compared with the choreography
-description. The reason this is considered an error, is that the <emphasis>Store</emphasis>
-participant should only send a <emphasis>BuyFailed</emphasis> message following an invalid
-credit check.
- </para>
-
- <para>
-When an error is detected in a scenario, the choreography designer can then determine whether
-the scenario is wrong (i.e. it does not correctly describe a business requirement), or whether
-the choreography is wrong and needs to be updated to accomodate the scenario.
- </para>
-
- <para>
-Once the choreography description has been successfully tested against the scenarios, the
-next step may be to obtain approval to proceed to the analysis/design phase. To help support
-this effort, the pi4soa tools provide the means to export the choreography description to
-a range of representations (e.g. BPMN, UML or HTML documentation
-<emphasis>TO BE CONFIRMED</emphasis>).
- </para>
+
</section>
+
</chapter>
14 years, 5 months
- 1
- 0
savara SVN: r104 - trunk and 1 other directory.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2009-12-05 07:46:40 -0500 (Sat, 05 Dec 2009)
New Revision: 104
Added:
tools/eclipse/trunk/features/org.pi4soa.monitor.feature/
Removed:
trunk/org.pi4soa.monitor.feature/
Log:
Copied: tools/eclipse/trunk/features/org.pi4soa.monitor.feature (from rev 103, trunk/org.pi4soa.monitor.feature)
14 years, 5 months
- 1
- 0