savara SVN: r427 - in trunk/docs/gettingstartedguide/src/main/en-US: module and 1 other directory.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2010-09-30 15:57:46 -0400 (Thu, 30 Sep 2010)
New Revision: 427
Added:
trunk/docs/gettingstartedguide/src/main/en-US/module/tap.xml
Modified:
trunk/docs/gettingstartedguide/src/main/en-US/master.xml
trunk/docs/gettingstartedguide/src/main/en-US/module/installation.xml
trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml
trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml
Log:
Updates to getting started guide to discuss BPEL runtime validation, update installation instructions and TAP.
Modified: trunk/docs/gettingstartedguide/src/main/en-US/master.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/master.xml 2010-09-30 17:25:15 UTC (rev 426)
+++ trunk/docs/gettingstartedguide/src/main/en-US/master.xml 2010-09-30 19:57:46 UTC (rev 427)
@@ -17,5 +17,6 @@
<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/tap.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/runtimevalidation.xml"/>
</book>
Modified: trunk/docs/gettingstartedguide/src/main/en-US/module/installation.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/installation.xml 2010-09-30 17:25:15 UTC (rev 426)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/installation.xml 2010-09-30 19:57:46 UTC (rev 427)
@@ -14,19 +14,18 @@
The pre-requisites for the SAVARA Eclipse Tools are:
</para>
<orderedlist>
- <listitem>Eclipse JEE (3.5 or higher) <ulink url="http://www.eclipse.org">http://www.eclipse.org</ulink></listitem>
- <listitem>SAVARA (version 1.0.0.CR2 or higher), available from <ulink url="http://www.jboss.org/savara/downloads">http://www.jboss.org/savara/downloads</ulink></listitem>
- <listitem>JBoss Tools (3.1 or higher) <ulink url="http://www.jboss.org/tools">http://www.jboss.org/tools</ulink>
+ <listitem>Eclipse JEE (3.6 or higher) <ulink url="http://www.eclipse.org">http://www.eclipse.org</ulink></listitem>
+ <listitem>JBoss Tools (3.2 or higher) <ulink url="http://www.jboss.org/tools">http://www.jboss.org/tools</ulink>
available from an update site</listitem>
</orderedlist>
<para>
- The pre-requisites for the SAVARA Service Validator (for JBossESB) are:
+ The pre-requisites for the SAVARA Service Validator are:
</para>
<orderedlist>
<listitem>JBossAS (5.1.0.GA or higher) <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbossas</ulink></listitem>
<listitem>JBossAS (4.8 or higher) <ulink url="http://www.jboss.org/jbossesb">http://www.jboss.org/jbossesb</ulink></listitem>
- <listitem>SAVARA (version 1.0.0.CR2 or higher), available from <ulink url="http://www.jboss.org/savara/downloads">http://www.jboss.org/savara/downloads</ulink></listitem>
+ <listitem>SAVARA (version 1.1.0 or higher), available from <ulink url="http://www.jboss.org/savara/downloads">http://www.jboss.org/savara/downloads</ulink></listitem>
</orderedlist>
</section>
@@ -48,7 +47,7 @@
<para>
When Eclipse has been lauched, go to the <emphasis>Help->Install New Software..</emphasis>
menu item. Select the Eclipse update site
- for the version of Eclipse (e.g. Galileo or Helios). Within the SOA Development
+ for the version of Eclipse (e.g. Helios). Within the SOA Development
category, select the BPMN Project Feature. Follow the instructions to accept
the license and then restart Eclipse after the plugins have been
installed.
@@ -65,34 +64,33 @@
them within your Eclipse environment.
</para>
<para>
- The <emphasis>pi4soa core</emphasis> feature should be selected from the
- <emphasis>All JBoss Tools</emphasis> category.
+ The <emphasis>JBoss Savara Tools</emphasis> feature should be selected from the
+ <emphasis>SOA Development</emphasis> category.
</para>
<para>
If you wish to view the generated BPEL using a BPEL editor, rather than
XML, then you should also select the <emphasis>JBoss BPEL Editor</emphasis> from the
- <emphasis>All JBoss Tools</emphasis> category.
+ <emphasis>SOA Development</emphasis> category.
</para>
<para>
NOTE: If you don't install the BPEL Editor, then you will have to install
- GMF. This can be found on the Galileo/Helios update site, under the <emphasis>Modeling</emphasis>
+ GMF. This can be found on the Helios update site, under the <emphasis>Modeling</emphasis>
category. Select the <emphasis>Graphical Modeling Framework</emphasis> entry, and
following the instructions to install.
</para>
+
+ <para>
+ It is also recommended that you install the JBoss WebServices Tools, and JBossAS Tools,
+ from the All category. These are required to define and launch a JBossAS
+ server from within Eclipse, generate a JAX-WS web service from a WSDL definition,
+ and test a Web Service.
+ </para>
</listitem>
-
- <listitem>
- Install SAVARA Eclipse plugins
- <para>
- The Eclipse plugins for SAVARA are installed via an update site referenced
- on the SAVARA <ulink url="http://www.jboss.org/savara/downloads">download page</ulink>.
- </para>
- </listitem>
</orderedlist>
<para>
- The installation instructions for the SAVARA Service Validator (for JBossESB) are:
+ The installation instructions for the SAVARA Service Validator are:
</para>
<orderedlist>
<listitem>
Modified: trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2010-09-30 17:25:15 UTC (rev 426)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2010-09-30 19:57:46 UTC (rev 427)
@@ -12,15 +12,34 @@
</note>
<para>
- Once services have been deployed, as mentioned in the previous section, we still need to be
- able to verify that the services continue to conform to the choreography description.
+ The previous sections have provided a brief introduction to the design-time
+ SOA governance features provided within the SAVARA Eclipse Tools distribution.
+ The aim of these capabilities are to enable verification of an implementation, initially
+ defined just using BPEL process definitions, against a
+ choreography, which in turn has been verified against business requirements defined using
+ scenarios. Therefore this helps to ensure that the implemented system meets the original
+ business requirements.
+ </para>
+
+ <para>
+ Being able to statically check that the implementation should send or receive messages
+ in the correct order is important, as it will reduce the amount of testing required
+ to ensure the service behaves correctly. However it does not enable the internal
+ implementation details to be verified, which may result in invalid decisions being
+ made at runtime, resulting in unexpected paths being taken.
+ </para>
+
+ <para>
+ Therefore, to ensure this situation does not occur, we also need runtime governance.
+ We still need to be able to verify that the services continue to conform to the
+ choreography description.
The <emphasis>Service Validator</emphasis> capability within the SAVARA distribution
can be used to validate the behaviour of each service.
</para>
<para>
In this section, we will use the <emphasis>purchasing</emphasis> example found in the
- <filename>${SAVARA}/samples/purchasing]</filename> folder.
+ <filename>${SAVARA}/samples/purchasing</filename> folder.
</para>
<section>
@@ -125,6 +144,83 @@
</section>
<section>
+ <title>Web Service / WS-BPEL Example - Purchasing</title>
+
+ <note>
+ <para>
+ Savara now includes the ability to validate web services (and therefore BPEL
+ processes) that use the jbossws-native stack. However the ODE engine, used
+ to execute BPEL processes within RiftSaw, currently optimises communications
+ between BPEL processes executing within the same engine, so that the communications
+ do not occur using the Web Service stack. This means that Savara is currently
+ unable to validate these interactions. Therefore it is currently recommended to
+ implement the 'Credit Agency' participant as a JAX-WS service. More information
+ on this will be available on the Savara blog.
+ </para>
+ </note>
+
+ <section>
+ <title>Deploying the Example</title>
+
+ <para>
+ The first step is to deploy the BPEL processes for the Store and CreditAgency
+ participants to a JBossAS server running RiftSaw. This can be achieved
+ using the Eclipse Web Tooling Project (WTP) server support, in conjunction with
+ the JBoss Tools features mentioned in the installation section.
+ </para>
+
+ <para>
+ Create a JBossAS server, configured to point to a JBossAS environment that has
+ previously been configured to run RiftSaw. Select the server in the
+ <emphasis>Servers</emphasis> view, and then select the <emphasis>Add and Remove ...</emphasis>
+ menu item. This will show a dialog window that will include the CreditAgency
+ and Store BPEL projects on the left. Select both projects, and press the
+ <emphasis>Add</emphasis> button. When the <emphasis>Finish</emphasis> button
+ is selected, the BPEL processes will be associated with the server.
+ </para>
+ </section>
+
+ <section>
+ <title>Running the Example</title>
+
+ <para>
+ Start the server using the <emphasis>Start</emphasis> menu item associated with
+ the JBossAS server in the <emphasis>Servers</emphasis> view. Once the server
+ has fully started, the BPEL processes should have been deployed.
+ </para>
+
+ <para>
+ The next step is to start the <emphasis>Savara->Monitor</emphasis> associated
+ with the <filename>PurchaseGoods.cdm</filename> choreography description.
+ </para>
+
+ <para>
+ The final step is to send a test message to the <emphasis>Store</emphasis>
+ BPEL process. This can be achieved by selecting the <filename>PurchaseGoodsProcess_Store.wsdl</filename>
+ file, within the <emphasis>PurchaseGoodsProcess_Store</emphasis> project (bpelContents
+ folder), and then select the menu item <emphasis>Web Services->Test with Web Services Explorer</emphasis>.
+ </para>
+
+ <para>
+ Expand the 'StoreInterfaceBinding' node, in the left hand panel of the explorer,
+ and select the 'buy' operation. Then select the 'Source' link, which will show the
+ various sections of the SOAP message to be sent. Edit the message body to be:
+ </para>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+ <q0:BuyRequest id="1" amount="200" />
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ Then press the 'Ok' button further down the panel. This will send the message to the
+ Store process, and eventually cause a response to appear in the lower panel.
+ </para>
+ </section>
+ </section>
+
+ <section>
<title>JBossESB Example - Trailblazer</title>
<section>
Modified: trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml 2010-09-30 17:25:15 UTC (rev 426)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml 2010-09-30 19:57:46 UTC (rev 427)
@@ -104,33 +104,4 @@
</section>
</section>
-
- <section>
- <title>Summary</title>
-
- <para>
-This section has provided a brief introduction to the design-time SOA governance features
-provided within the SAVARA Eclipse Tools distribution.
- </para>
-
- <para>
-The aim of these capabilities are to enable verification of an implementation, initially
-defined just using BPEL process definitions, against a
-choreography, which in turn has been verified against business requirements defined using
-scenarios. Therefore this helps to ensure that the implemented system meets the original
-business requirements.
- </para>
-
- <para>
-Being able to statically check that the implementation should send or receive messages
-in the correct order is important, as it will reduce the amount of testing required
-to ensure the service behaves correctly. However it does not enable the internal
-implementation details to be verified, which may result in invalid decisions being
-made at runtime, resulting in unexpected paths being taken. Therefore, to ensure this
-situation does not occur, we also need runtime governance, which is discussed in a
-later section (Runtime Validation).
- </para>
-
- </section>
-
</chapter>
Added: trunk/docs/gettingstartedguide/src/main/en-US/module/tap.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/tap.xml (rev 0)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/tap.xml 2010-09-30 19:57:46 UTC (rev 427)
@@ -0,0 +1,151 @@
+<?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="tap">
+ <title>Testable Architecture Project</title>
+
+ <para>
+ The previous sections have discussed the various phases of the software development
+ lifecycle, and the artifacts that can be created. They have also outlined some
+ validation performed between the scenarios and choreography, when a specific link
+ has been established from the scenario.
+ </para>
+
+ <para>
+ However the aim of the "Testable Architecture" methodology is to provide validation
+ between all artifacts, to ensure that artifacts defined at any particular phase
+ can be shown to be valid against the artifacts in preceding phases.
+ </para>
+
+ <para>
+ Therefore the concept of a "Testable Architecture Project" or TAP has been introduced.
+ This is essentially a file that records information about the artifacts defined in
+ each phase of the software development lifecycle, and the relationships between them.
+ This file can then be validated to ensure that each artifact, and its dependencies,
+ are valid in respect of each other.
+ </para>
+
+ <para>
+ For example, the <filename>purchasing</filename> example contains a TAP file with
+ the following contents:
+ </para>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+<project xmlns="http://www.savara.org/ta/project" xmlns:xsi="http://www.w3.org/2001/XMLSchema"
+ xsi:schemaLocation="http://www.savara.org/ta/project tap.xsd"
+ name="Purchasing" version="1.0.0">
+
+ <phase name="requirements">
+ <resource id="SuccessfulPurchase.scn">
+ <uri type="eclipse" context="purchasing" locator="/SuccessfulPurchase.scn" />
+ </resource>
+ <resource id="InvalidPurchase.scn">
+ <uri type="eclipse" context="purchasing" locator="/InvalidPurchase.scn" />
+ </resource>
+ </phase>
+
+ <phase name="architecture">
+ <resource id="PurchaseGoods.cdm">
+ <uri type="eclipse" context="purchasing" locator="/PurchaseGoods.cdm" />
+ <relationship type="depends" ref="SuccessfulPurchase.scn" />
+ <relationship type="depends" ref="InvalidPurchase.scn" />
+ </resource>
+ </phase>
+
+ <phase name="implementation">
+ <resource id="PurchaseGoodsProcess_Store.bpel">
+ <uri type="eclipse" context="PurchaseGoodsProcess-Store"
+ locator="/bpelContent/PurchaseGoodsProcess_Store.bpel" />
+ <relationship type="depends" ref="PurchaseGoods.cdm" >
+ <description>
+ Link from the BPEL process to the 'Store' participant
+ within the choreography
+ </description>
+ <link type="role" to="Store" />
+ </relationship>
+ </resource>
+ <resource id="PurchaseGoodsProcess_CreditAgency.bpel">
+ <uri type="eclipse" context="PurchaseGoodsProcess-CreditAgency"
+ locator="/bpelContent/PurchaseGoodsProcess_CreditAgency.bpel" />
+ <relationship type="depends" ref="PurchaseGoods.cdm" >
+ <description>
+ Link from the BPEL process to the 'CreditAgency' participant
+ within the choreography
+ </description>
+ <link type="role" to="CreditAgency" />
+ </relationship>
+ </resource>
+ </phase>
+</project>
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ The top level element is <emphasis>project</emphasis>, with the <emphasis>name</emphasis>
+ and <emphasis>version</emphasis> attributes to define the details of the Testable Architecture
+ Project.
+ </para>
+
+ <para>
+ The project then contains <emphasis>phase</emphasis> elements, one for each stage of the
+ software development lifecycle we are interested in. These elements are only used to
+ segment the artifacts into the different phases, which can be useful for tasks such as
+ project management or documentation generation.
+ </para>
+
+ <para>
+ The phase element contains <emphasis>resource</emphasis> elements, one per artifact. A
+ resource represents an artifact that is of interest in the Testable Architecture Project.
+ </para>
+
+ <para>
+ The resource element contains one or more of the following elements:
+ </para>
+
+ <orderedlist>
+ <listitem>
+ uri
+ <para>
+ This element is used to define the location of a resource. A URI element is required for
+ each environent in which the resource may be accessed, for example, within Eclipse and
+ within an SOA Repository.
+ </para>
+ <para>
+ The <emphasis>type</emphasis> attribute defines the type of locator, which will usually
+ map onto the environment in which the resource exists. So in this case we are only
+ defining URI elements associated with the Eclipse environment.
+ </para>
+ <para>
+ The <emphasis>context</emphasis> attribute defines the local information that can be used
+ in the particular environment, to determine where the resource is contained. For example,
+ if the environment is Eclipse, the context would be the project name.
+ </para>
+ <para>
+ The <emphasis>locator</emphasis> attribute is used to specify the specific location of
+ the resource, within the particular specified context, in the environment type. For example,
+ if the environment was Eclipse, then the locator would be the relative path of the resource
+ within the project identified in the context attribute.
+ </para>
+ </listitem>
+ <listitem>
+ relationship
+ <para>
+ This element establishes a relationship from the containing resource, to another resource
+ identifed by the <emphasis>ref</emphasis> attribute.
+ </para>
+ <para>
+ The relationship element can optionally have additional information associated with it,
+ to help clarify the nature of the relationship between the two resources.
+ </para>
+ <para>
+ For example, in the TAP file illustrated above, the two BPEL resources (in the implementation
+ phase) have a relationship to the choreography file - however the relationship needs to be
+ more specific. We need to indicate what <emphasis>role</emphasis> within that choreography
+ the BPEL processes are associated with. The <emphasis>link</emphasis> element enables
+ the <emphasis>type</emphasis> to be defined, and a value to be specified in the
+ <emphasis>to</emphasis> attribute.
+ </para>
+ </listitem>
+ </orderedlist>
+</chapter>
13 years, 7 months
- 1
- 0
savara SVN: r426 - in trunk/docs/gettingstartedguide/src/main/en-US: module and 1 other directory.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2010-09-30 13:25:15 -0400 (Thu, 30 Sep 2010)
New Revision: 426
Added:
trunk/docs/gettingstartedguide/src/main/en-US/images/editvalidatorann.png
trunk/docs/gettingstartedguide/src/main/en-US/images/validatorannotation.png
trunk/docs/gettingstartedguide/src/main/en-US/images/validatortooltip.png
Removed:
trunk/docs/gettingstartedguide/src/main/en-US/images/SVJBossESBAnnotation.jpg
trunk/docs/gettingstartedguide/src/main/en-US/images/SVJBossESBAnnotationToolTip.jpg
trunk/docs/gettingstartedguide/src/main/en-US/images/SVJBossESBEditAnnotation.jpg
Modified:
trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml
trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml
Log:
Updated getting started guide.
Deleted: trunk/docs/gettingstartedguide/src/main/en-US/images/SVJBossESBAnnotation.jpg
===================================================================
(Binary files differ)
Deleted: trunk/docs/gettingstartedguide/src/main/en-US/images/SVJBossESBAnnotationToolTip.jpg
===================================================================
(Binary files differ)
Deleted: trunk/docs/gettingstartedguide/src/main/en-US/images/SVJBossESBEditAnnotation.jpg
===================================================================
(Binary files differ)
Added: trunk/docs/gettingstartedguide/src/main/en-US/images/editvalidatorann.png
===================================================================
(Binary files differ)
Property changes on: trunk/docs/gettingstartedguide/src/main/en-US/images/editvalidatorann.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/docs/gettingstartedguide/src/main/en-US/images/validatorannotation.png
===================================================================
(Binary files differ)
Property changes on: trunk/docs/gettingstartedguide/src/main/en-US/images/validatorannotation.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/docs/gettingstartedguide/src/main/en-US/images/validatortooltip.png
===================================================================
(Binary files differ)
Property changes on: trunk/docs/gettingstartedguide/src/main/en-US/images/validatortooltip.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2010-09-30 16:04:45 UTC (rev 425)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2010-09-30 17:25:15 UTC (rev 426)
@@ -7,219 +7,249 @@
<note>
<para>
Before you can deploy and run the runtime validation example, you will
- need to install the SAVARA Validator module for JBossESB.
+ need to install the SAVARA Validator module for JBoss.
</para>
</note>
<para>
-Once services have been deployed, as mentioned in the previous section, we still need to be
-able to verify that the services continue to conform to the choreography description.
-The <emphasis>Conversation Validation</emphasis> capability within the SAVARA distribution
-can be used to validate the behaviour of each service.
+ Once services have been deployed, as mentioned in the previous section, we still need to be
+ able to verify that the services continue to conform to the choreography description.
+ The <emphasis>Service Validator</emphasis> capability within the SAVARA distribution
+ can be used to validate the behaviour of each service.
</para>
<para>
-In this section, we will use the Trailblazer example found in the <filename>${SAVARA}/samples/trailblazer</filename> folder and the <filename>trailblazer-models</filename> Eclipse project.
+ In this section, we will use the <emphasis>purchasing</emphasis> example found in the
+ <filename>${SAVARA}/samples/purchasing]</filename> folder.
</para>
<section>
<title>Service Validator Configuration</title>
<para>
-The JBossESB service validator configuration is defined using jbossesb specific annotations, that are associated
-with the 'exchange details' components (contained within interactions), within the choreography description.
+ The service validator configuration is defined using specific annotation, that is associated
+ with the 'exchange details' components (contained within interactions), within the
+ choreography description.
</para>
<para>
-To view the pre-configured service validator configuration defined for the Trailblazer example, edit the
-<filename>TrailBlazer.cdm</filename> file, navigate to the <emphasis>Choreography Flows</emphasis> tab and then
-select the <emphasis>Choreography->Edit Annotations</emphasis> menu item associated with the first 'exchange details'
-component (as shown below).
+ To view the pre-configured service validator configuration defined for the Purchasing
+ example, edit the <filename>PurchaseGoods.cdm</filename> file, navigate to the
+ <emphasis>Choreography Flows</emphasis> tab and then select the
+ <emphasis>Choreography->Edit Annotations</emphasis> menu item associated with the first
+ 'exchange details' component (as shown below).
</para>
<imageobject>
- <imagedata fileref="en-US/images/SVJBossESBEditAnnotation.jpg" align="center" width="3in" />
+ <imagedata fileref="en-US/images/editvalidatorann.png" align="center" width="3in" />
</imageobject>
<para>
-This will display the annotation editor, with the single configured annotation called 'validator'. This annotation defines
-the information required for the Service Validator to monitor this specific message exchange (i.e. the JMS destination
-on which the message will be passed).
+ This will display the annotation editor, with the single configured annotation called
+ 'validator'. This annotation defines the information required for the Service Validator
+ to monitor this specific message exchange (e.g. the JMS destination
+ on which the message will be passed, or in this case the Service Name for the target
+ Web Service).
</para>
<imageobject>
- <imagedata fileref="en-US/images/SVJBossESBAnnotation.jpg" align="center" width="3in" />
+ <imagedata fileref="en-US/images/validatorannotation.png" align="center" width="3in" />
</imageobject>
<para>
-Once an annotation has been defined, it will also be displayed as part of the tooltip for the associated model component, for example:
+ Once an annotation has been defined, it will also be displayed as part of the tooltip
+ for the associated model component, for example:
</para>
<imageobject>
- <imagedata fileref="en-US/images/SVJBossESBAnnotationTooltip.jpg" align="center" width="3in" />
+ <imagedata fileref="en-US/images/validatortooltip.png" align="center" width="4in" />
</imageobject>
<para>
-Once the jbossesb annotations have been defined for all relevant 'exchange details' components
-in the choreography description, the choreography file can be copied to the
-<filename>${JBossAS}/server/default/deploy/savara-validator.esb/models</filename>
-folder in the JBossAS environment. The service validator configuration for the
-<emphasis>trailblazer</emphasis> example has been preconfigured to be deployed as part of
-the installation procedure.
+ Once the annotations have been defined for all relevant 'exchange details' components
+ in the choreography description, the choreography file can be copied to the
+ <filename>${JBossAS}/server/default/deploy/savara-validator-jboss.sar/models</filename>
+ folder in the JBossAS environment. The service validator configuration for the
+ <emphasis>purchasing</emphasis> example has been preconfigured to be deployed as part of
+ the installation procedure.
</para>
<note>
<para>
-If the <filename>savara-validator.esb/validator-config.xml</filename> within the JBossAS
-environment is modified, or choreography description files added, removed or updated within
-the <filename>savara-validator.esb/models</filename> sub-folder, then the changes will
-automatically be detected and used to re-configure the service validators without having to
-restart the JBossESB server.
+ If the <filename>savara-validator-jboss.sar/validator-config.xml</filename> within the JBossAS
+ environment is modified, or choreography description files added, removed or updated within
+ the <filename>savara-validator-jboss.sar/models</filename> sub-folder, then the changes will
+ automatically be detected and used to re-configure the service validators without having to
+ restart the server.
</para>
</note>
</section>
<section>
- <title>Deploy the TrailBlazer Example</title>
+ <title>SAVARA Monitor</title>
<para>
-The first step to deploying the Trailblazer example is to configure the JBossAS environment:
+ The SAVARA Monitor is an Eclipse based tool that can be used to help develop,
+ test and validate a business process (encoded as a choreography) executing across
+ a distributed system. (Future releases will include equivalent web based tooling
+ to enable production based logging and query of the validation information).
</para>
-
- <orderedlist>
- <listitem>
-Update the <filename>${JBossAS}/server/default/deploy/jbossesb.sar/jbossesb-properties.xml</filename>
-file, in the section entitled "transports" and specify all of the SMTP mail server settings for
-your environment.
- </listitem>
- <listitem>
-Update the <filename>trailblazer/trailblazer.properties</filename>
- <para>
-Update the <property>file.bank.monitored.directory</property> and <property>file.output.directory</property> properties. These are folders used by the File Based Bank, and are set to <filename>/tmp/input</filename> and <filename>/tmp/output</filename> by default.
- </para>
- </listitem>
- <listitem>
-Update the <filename>trailblazer/esb/conf/jboss-esb.xml</filename>
- <para>
-There is a <emphasis>fs-provider</emphasis> block, update the <property>directory</property> attribute value to be the same as the <property>file.output.directory</property> value in <filename>trailblazer.properties</filename> file.
- </para>
- </listitem>
- <listitem>
-Start the JBossAS server
- </listitem>
- </orderedlist>
-
+
<para>
-One the server has been started, the next step is to deploy the relevant components into the JBossAS environment. This is achieved by:
+ The tool is used to observe a correlated view of the executing business
+ transactions. Each service validator can be configured to report activites (i.e. sent
+ and received messages) that it validates, to enable the correlator to reconstitute a
+ global interpretation of each transaction.
</para>
- <orderedlist>
- <listitem>
-From the <filename>trailblazer</filename> folder, execute the following command to deploy the example to the ESB: <emphasis role="bold">ant deploy</emphasis>
- <para>
-this should deploy the ESB and WAR files to your JBoss AS <filename>server/default</filename>.
- </para>
- </listitem>
- <listitem>
-From the <filename>trailblazer/banks</filename> folder, execute the command to start the JMS Bank service: <emphasis role="bold">ant runJMSBank</emphasis>.
- </listitem>
- <listitem>
-From the <filename>trailblazer/banks</filename> folder, execute the command to start the JMS Bank service: <emphasis role="bold">ant runFileBank</emphasis>.
- </listitem>
- </orderedlist>
-
- </section>
-
- <section>
- <title>Starting the pi4soa Monitor</title>
-
<para>
-The pi4soa Monitor is used to observe a correlated view of the executing business transactions. Each service validator can be configured to report activites (i.e. sent and received messages) that it validates, to enable the correlator to reconstitute a global interpretation of each transaction.
+ This correlated view of each transaction can be used to understand where each
+ transaction is within the process. It can also be used to report
+ <emphasis>out of sequence</emphasis>, <emphasis>unexpected messages</emphasis> and
+ more general errors in the context of the business process.
</para>
<para>
-This correlated view of each transaction can be used to understand where each transaction is within the process. It can also be used to report <emphasis>out of sequence</emphasis>, <emphasis>unexpected messages</emphasis> and more general errors in the context of the business process.
+ Once the following examples have been deployed to the JBossAS environment, and the
+ server is running, then the monitoring tool can be launched from the Eclipse environment
+ by selecting the <emphasis>Savara->Monitor</emphasis> menu item from the popup menu
+ associated with the choreography (.cdm) file.
</para>
<para>
-A simple monitoring tool is currently provided with the pi4soa tools, to enable the correlated global view of the transactions to be observed. Once the Trailblazer example has been deployed to the JBossAS environment, and the server is running, then the monitoring tool can be launched from the Eclipse environment by selecting the <emphasis>Choreography->Monitor</emphasis> menu item from the popup menu associated with the <filename>TrailBlazer.cdm</filename> file.
+ Wait for the monitor window to start, and indicate that the choreography is being monitored,
+ shown in the status line at the bottom of the window.
</para>
- <imageobject>
- <imagedata fileref="en-US/images/MonitorMenu.jpg" align="center" width="2in" />
- </imageobject>
-
- <para>
-Wait for the monitor window to start, and indicate that the choreography is being monitored,
-shown in the status line at the bottom of the window.
- </para>
-
- <imageobject>
- <imagedata fileref="en-US/images/ChoreoMonReady.jpg" align="center" width="4in" />
- </imageobject>
-
</section>
<section>
- <title>Running the Example</title>
-
- <para>
-To run the example, you need to start a browser and select the URL
-<ulink url="http://localhost:8080/trailblazer">localhost:8080/trailblazer</ulink>. This will
-show the following page, if the server has been configured correctly and the TrailBlazer
-example deployed:
- </para>
-
- <imageobject>
- <imagedata fileref="en-US/images/TrailblazerWebPage.jpg" align="center" width="4in" />
- </imageobject>
-
- <para>
-Now you can submit quotes, You will see either a loan request rejected (single email) because
-the score is less than 4, or two emails (one from JMS bank and one from FileBased bank) with
-valid quotes. When entering subsequent quotes, make sure that the quote reference is updated,
-so that each session has a unique id.
- </para>
-
+ <title>JBossESB Example - Trailblazer</title>
+
+ <section>
+ <title>Deploying the Example</title>
+
+ <para>
+ The first step to deploying the Trailblazer example is to configure the JBossAS environment:
+ </para>
+
+ <orderedlist>
+ <listitem>
+ Update the <filename>${JBossAS}/server/default/deployers/esb.deployer/jbossesb-properties.xml</filename>
+ file, in the section entitled "transports" and specify all of the SMTP mail server settings for
+ your environment.
+ </listitem>
+ <listitem>
+ Update the <filename>trailblazer/trailblazer.properties</filename>
+ <para>
+ Update the <property>file.bank.monitored.directory</property> and
+ <property>file.output.directory</property> properties. These are folders
+ used by the File Based Bank, and are set to <filename>/tmp/input</filename>
+ and <filename>/tmp/output</filename> by default.
+ </para>
+ </listitem>
+ <listitem>
+ Update the <filename>trailblazer/esb/conf/jboss-esb.xml</filename>
+ <para>
+ There is a <emphasis>fs-provider</emphasis> block, update the
+ <property>directory</property> attribute value to be the same as the
+ <property>file.output.directory</property> value in
+ <filename>trailblazer.properties</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ Start the JBossAS server
+ </listitem>
+ </orderedlist>
+
+ <para>
+ One the server has been started, the next step is to deploy the relevant
+ components into the JBossAS environment. This is achieved by:
+ </para>
+
+ <orderedlist>
+ <listitem>
+ From the <filename>trailblazer</filename> folder, execute the following
+ command to deploy the example to the ESB:
+ <emphasis role="bold">ant deploy</emphasis>
+ <para>
+ this should deploy the ESB and WAR files to your JBoss AS
+ <filename>server/default</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ From the <filename>trailblazer/banks</filename> folder, execute the command
+ to start the JMS Bank service: <emphasis role="bold">ant runJMSBank</emphasis>.
+ </listitem>
+ <listitem>
+ From the <filename>trailblazer/banks</filename> folder, execute the command
+ to start the JMS Bank service: <emphasis role="bold">ant runFileBank</emphasis>.
+ </listitem>
+ </orderedlist>
+
+ </section>
+
+ <section>
+ <title>Running the Example</title>
+
+ <para>
+ To run the example, you need to start a browser and select the URL
+ <ulink url="http://localhost:8080/trailblazer">localhost:8080/trailblazer</ulink>. This will
+ show the following page, if the server has been configured correctly and the TrailBlazer
+ example deployed:
+ </para>
+
+ <imageobject>
+ <imagedata fileref="en-US/images/TrailblazerWebPage.jpg" align="center" width="4in" />
+ </imageobject>
+
+ <para>
+ Now you can submit quotes, You will see either a loan request rejected (single email) because
+ the score is less than 4, or two emails (one from JMS bank and one from FileBased bank) with
+ valid quotes. When entering subsequent quotes, make sure that the quote reference is updated,
+ so that each session has a unique id.
+ </para>
+
+ </section>
+
+ <section>
+ <title>Detecting a Validation Error</title>
+
+ <para>
+ To demonstrate the detection of validation errors, there is an alternative implementation of the
+ trailblazer modules that behaviour differently to the choreography that is being monitored.
+ Specifically, the credit score threshold used to determine whether a loan request should be
+ issued to the banks, is raised from 4 to 7.
+ </para>
+
+ <para>
+ To deploy the version of the TrailBlazer example that results in validation errors, then:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ From the <filename>${SAVARA}/samples/trailblazer</filename> folder, execute the
+ following command to deploy the example to the ESB:
+ <emphasis role="bold">ant deploy-error-client</emphasis>.
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The next step is to issue more transactions, until a credit check score occurs that is between
+ 4 and 6 inclusive. This will result in a <emphasis>insufficientCredit</emphasis> interaction
+ being reported, which would be unexpected in terms of the choreography.
+ </para>
+
+ <imageobject>
+ <imagedata fileref="en-US/images/TrailBlazerMonitorError.jpg" align="center" width="4in" />
+ </imageobject>
+
+ <para>
+ When errors, such as unexpected messages, are detected by the service validators and reported
+ to the SAVARA Monitor, they are displayed in red.
+ </para>
+
+ </section>
</section>
-
- <section>
- <title>Detecting a Validation Error</title>
-
- <para>
-To demonstrate the detection of validation errors, there is an alternative implementation of the
-trailblazer modules that behaviour differently to the choreography that is being monitored.
-Specifically, the credit score threshold used to determine whether a loan request should be
-issued to the banks, is raised from 4 to 7.
- </para>
-
- <para>
-To deploy the version of the TrailBlazer example that results in validation errors, then:
- </para>
-
- <itemizedlist>
- <listitem>
-From the <filename>${SAVARA}/samples/trailblazer</filename> folder, execute the
-following command to deploy the example to the ESB: <emphasis role="bold">ant deploy-error-client</emphasis>.
- </listitem>
- </itemizedlist>
-
- <para>
-The next step is to issue more transactions, until a credit check score occurs that is between
-4 and 6 inclusive. This will result in a <emphasis>insufficientCredit</emphasis> interaction
-being reported, which would be unexpected in terms of the choreography.
- </para>
-
- <imageobject>
- <imagedata fileref="en-US/images/TrailBlazerMonitorError.jpg" align="center" width="4in" />
- </imageobject>
-
- <para>
-When errors, such as unexpected messages, are detected by the service validators and reported
-to the Choreography Monitor, they are displayed in red.
- </para>
-
- </section>
-
</chapter>
Modified: trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml 2010-09-30 16:04:45 UTC (rev 425)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/servicedev.xml 2010-09-30 17:25:15 UTC (rev 426)
@@ -80,399 +80,27 @@
</section>
<section>
- <title>Adding implementation details to CreditAgency</title>
+ <title>Adding implementation details</title>
- <section>
- <title>Deployment Descriptor</title>
-
- <para>
- When generated, the deployment descriptor initially has the following content:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
- xmlns:ns1="http://www.jboss.org/examples/creditAgency">
- <process name="ns1:PurchaseGoodsProcess_CreditAgency">
- <active>
- true
- </active>
- <provide partnerLink="StoreToCreditAgency">
- <service/>
- </provide>
- </process>
-</deploy>
- ]]></programlisting>
- </informalexample>
-
- <para>
-The only change necessary is to add some attributes to the <emphasis>service</emphasis> element:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<service name="ns1:CreditAgencyService" port="CreditAgencyInterfacePort"/>
- ]]></programlisting>
- </informalexample>
-
- </section>
-
- <section>
- <title>BPEL Process Definition</title>
-
- <para>
-The generated BPEL process for the CreditAgency participant is as follows:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<process xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
- xmlns:ca="http://www.jboss.org/examples/creditAgency"
- xmlns:sto="http://www.jboss.org/examples/store"
- xmlns:tns="http://www.jboss.org/savara/examples"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:ns0="http://www.scribble.org/conversation"
- ns0:conversationType="savara.samples.Common@CreditAgency"
- name="PurchaseGoodsProcess_CreditAgency"
- targetNamespace="http://www.jboss.org/examples/creditAgency"
- xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable">
- <import importType="http://schemas.xmlsoap.org/wsdl/"
- location="PurchaseGoodsProcess_CreditAgency.wsdl"
- namespace="http://www.jboss.org/examples/creditAgency"/>
- <import importType="http://schemas.xmlsoap.org/wsdl/"
- location="PurchaseGoodsProcess_Store.wsdl"
- namespace="http://www.jboss.org/examples/store"/>
- <import importType="http://schemas.xmlsoap.org/wsdl/"
- location="PurchaseGoodsProcess_CreditAgencyArtifacts.wsdl"
- namespace="http://www.jboss.org/examples/creditAgency"/>
- <partnerLinks>
- <partnerLink myRole="CreditAgencyService" name="StoreToCreditAgency"
- partnerLinkType="ca:StoreToCreditAgencyServiceLT"/>
- </partnerLinks>
- <variables>
- <variable messageType="ca:checkCreditRequest" name="creditCheckRequestVar"/>
- <variable messageType="ca:checkCreditResponse" name="creditCheckOkVar"/>
- <variable messageType="ca:CreditCheckFailedFault" name="creditCheckInvalidVar"/>
- </variables>
- <sequence>
- <receive createInstance="yes" name="Receive_CreditCheckRequest" operation="checkCredit"
- partnerLink="StoreToCreditAgency" portType="ca:CreditAgencyInterface"
- variable="creditCheckRequestVar"/>
- <if>
- <sequence>
- <reply name="Send_CreditCheckOk" operation="checkCredit"
- partnerLink="StoreToCreditAgency"
- portType="ca:CreditAgencyInterface" variable="creditCheckOkVar"/>
- </sequence>
- <else>
- <sequence>
- <reply faultName="ca:CreditCheckFailed" name="Send_CreditCheckInvalid"
- operation="checkCredit" partnerLink="StoreToCreditAgency"
- portType="ca:CreditAgencyInterface" variable="creditCheckInvalidVar"/>
- </sequence>
- </else>
- </if>
- </sequence>
-</process>
- ]]></programlisting>
- </informalexample>
-
- <para>
- There are three changes required, the first being to add a condition following
- the <emphasis>if</emphasis> element:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<if>
- <bpel:condition>
- $creditCheckRequestVar.content/@amount <= 500
- </bpel:condition>
- ....
- ]]></programlisting>
- </informalexample>
+ <para>
+ The generated BPEL processes and deployment descriptors are incomplete, due to
+ lack of implementation details in the choreography description. The choreography
+ simply represents the externally observable interactions between the parties,
+ and therefore cannot provide internal implementation details.
+ </para>
- <para>
- The next two changes relate to taking the information provided in the request
- and constructing an appropriate normal and fault response. In this simple
- example we only echo back the information received in the request, however
- more complicated processing could be performed before returning either
- response.
- </para>
-
- <para>
- The following XML code should be added before the normal response (i.e.
- just inside the <emphasis>sequence</emphasis> element following the
- condition:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<assign name="CopyPurchaseDetails">
- <bpel:copy>
- <bpel:from>
- <bpel:literal xml:space="preserve">
- <tns:CreditCheckOk xmlns:tns="http://www.jboss.org/examples/creditAgency"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.jboss.org/examples/creditAgency creditAgency.xsd "
- id="" amount="" >
- </tns:CreditCheckOk>
- </bpel:literal>
- </bpel:from>
- <bpel:to variable="creditCheckOkVar" part="content"></bpel:to>
- </bpel:copy>
- <copy>
- <from>$creditCheckRequestVar.content/@id</from>
- <to>$creditCheckOkVar.content/@id</to>
- </copy>
-</assign>
- ]]></programlisting>
- </informalexample>
-
- <para>
- The following XML code should be added before the fault response (i.e.
- just inside the <emphasis>sequence</emphasis> element that is contained
- in the <emphasis>else</emphasis> element:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<assign name="CopyPurchaseDetails">
- <bpel:copy>
- <bpel:from>
- <bpel:literal xml:space="preserve">
- <tns:CreditCheckInvalid xmlns:tns="http://www.jboss.org/examples/creditAgency"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.jboss.org/examples/creditAgency creditAgency.xsd "
- id="" amount="" >
- </tns:CreditCheckInvalid>
- </bpel:literal>
- </bpel:from>
- <bpel:to variable="creditCheckInvalidVar" part="content"></bpel:to>
- </bpel:copy>
- <copy>
- <from>$creditCheckRequestVar.content/@id</from>
- <to>$creditCheckInvalidVar.content/@id</to>
- </copy>
-</assign>
- ]]></programlisting>
- </informalexample>
-
- </section>
- </section>
-
- <section>
- <title>Adding implementation details to Store</title>
-
- <section>
- <title>Deployment Descriptor</title>
-
- <para>
- When generated, the deployment descriptor initially has the following content:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
- xmlns:ns1="http://www.jboss.org/examples/store">
- <process name="ns1:PurchaseGoodsProcess_Store">
- <active>
- true
- </active>
- <provide partnerLink="BuyerToStore">
- <service/>
- </provide>
- <invoke partnerLink="StoreToCreditAgency">
- <service/>
- </invoke>
- </process>
-</deploy>
- ]]></programlisting>
- </informalexample>
-
- <para>
- The only changes necessary are, (1) to add a namespace prefix definition,
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-xmlns:ns2="http://www.jboss.org/examples/creditAgency"
- ]]></programlisting>
- </informalexample>
-
- <para>
- and (2) to add some attributes to the <emphasis>service</emphasis> element:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
- <provide partnerLink="BuyerToStore">
- <service name="ns1:StoreService" port="StoreInterfacePort"/>
- </provide>
- <invoke partnerLink="StoreToCreditAgency">
- <service name="ns2:CreditAgencyService" port="CreditAgencyInterfacePort"/>
- </invoke>
- ]]></programlisting>
- </informalexample>
-
- </section>
-
- <section>
- <title>BPEL Process Definition</title>
-
- <para>
- The generated BPEL process for the Store participant is as follows:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<process xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
- xmlns:ca="http://www.jboss.org/examples/creditAgency"
- xmlns:sto="http://www.jboss.org/examples/store"
- xmlns:tns="http://www.jboss.org/savara/examples"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- xmlns:ns0="http://www.scribble.org/conversation"
- ns0:conversationType="savara.samples.Purchasing@Store"
- name="PurchaseGoodsProcess_Store"
- targetNamespace="http://www.jboss.org/examples/store"
- xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable">
- <import importType="http://schemas.xmlsoap.org/wsdl/"
- location="PurchaseGoodsProcess_Store.wsdl"
- namespace="http://www.jboss.org/examples/store"/>
- <import importType="http://schemas.xmlsoap.org/wsdl/"
- location="PurchaseGoodsProcess_CreditAgency.wsdl"
- namespace="http://www.jboss.org/examples/creditAgency"/>
- <import importType="http://schemas.xmlsoap.org/wsdl/"
- location="PurchaseGoodsProcess_StoreArtifacts.wsdl"
- namespace="http://www.jboss.org/examples/store"/>
- <partnerLinks>
- <partnerLink myRole="StoreService" name="BuyerToStore" partnerLinkType="sto:BuyerToStoreServiceLT"/>
- <partnerLink name="StoreToCreditAgency" partnerLinkType="sto:StoreToCreditAgencyLT"
- partnerRole="CreditAgencyRequester"/>
- </partnerLinks>
- <variables>
- <variable messageType="sto:buyRequest" name="buyRequestVar"/>
- <variable messageType="ca:checkCreditRequest" name="creditCheckRequestVar"/>
- <variable messageType="ca:checkCreditResponse" name="creditCheckOkVar"/>
- <variable messageType="sto:buyResponse" name="buyConfirmedVar"/>
- <variable messageType="sto:BuyFailedFault" name="buyFailedVar"/>
- </variables>
- <sequence>
- <receive createInstance="yes" name="Receive_BuyRequest" operation="buy"
- partnerLink="BuyerToStore"
- portType="sto:StoreInterface" variable="buyRequestVar"/>
- <scope>
- <faultHandlers>
- <catch faultMessageType="ca:CreditCheckFailedFault"
- faultName="ca:CreditCheckFailed"
- faultVariable="creditCheckInvalidVar">
- <sequence>
- <reply faultName="sto:BuyFailed" name="Send_BuyFailed" operation="buy"
- partnerLink="BuyerToStore" portType="sto:StoreInterface"
- variable="buyFailedVar"/>
- </sequence>
- </catch>
- </faultHandlers>
- <sequence>
- <invoke inputVariable="creditCheckRequestVar" name="Send_CreditCheckRequest"
- operation="checkCredit" outputVariable="creditCheckOkVar"
- partnerLink="StoreToCreditAgency" portType="ca:CreditAgencyInterface"/>
- <reply name="Send_BuyConfirmed" operation="buy" partnerLink="BuyerToStore"
- portType="sto:StoreInterface" variable="buyConfirmedVar"/>
- </sequence>
- </scope>
- </sequence>
-</process>
- ]]></programlisting>
- </informalexample>
-
- <para>
- There are three changes required. The first being to add an assignment
- statement within the <emphasis>catch</emphasis> element's
- <emphasis>sequence</emphasis> prior to the <emphasis>reply</emphasis>:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<assign name="CopyPurchaseDetails">
- <bpel:copy>
- <bpel:from>
- <bpel:literal xml:space="preserve">
- <tns:BuyFailed 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="" />
- </bpel:literal>
- </bpel:from>
- <bpel:to variable="buyFailedVar" part="content"></bpel:to>
- </bpel:copy>
- <copy>
- <from>$creditCheckInvalidVar.content/@id</from>
- <to>$buyFailedVar.content/@id</to>
- </copy>
-</assign>
- ]]></programlisting>
- </informalexample>
+ <para>
+ Therefore a completed version of the deployment descriptor and BPEL process files,
+ for both the creditAgency and store participants, can be found in the
+ <emphasis>purchasing</emphasis> example's <filename>completed</filename> folder.
+ </para>
- <para>
- The remaining two changes relate to taking the information received in the
- initial request, to construct a request to the credit agency, and then
- extracting the information from the credit agency response, to return it
- to the <emphasis>Store</emphasis> client. The following snippet shows
- the two assignment statements either side of the <emphasis>invoke</emphasis>
- statement:
- </para>
-
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<assign name="CopyPurchaseDetails">
- <bpel:copy>
- <bpel:from>
- <bpel:literal xml:space="preserve">
- <tns:CreditCheckRequest xmlns:tns="http://www.jboss.org/examples/creditAgency"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.jboss.org/examples/creditAgency creditAgency.xsd "
- id="" amount="" >
- </tns:CreditCheckRequest>
- </bpel:literal>
- </bpel:from>
- <bpel:to variable="creditCheckRequestVar" part="content"></bpel:to>
- </bpel:copy>
- <copy>
- <from>$buyRequestVar.content/@id</from>
- <to>$creditCheckRequestVar.content/@id</to>
- </copy>
- <copy>
- <from>$buyRequestVar.content/@amount</from>
- <to>$creditCheckRequestVar.content/@amount</to>
- </copy>
-</assign>
-<invoke inputVariable="creditCheckRequestVar" name="Send_CreditCheckRequest"
- operation="checkCredit" outputVariable="creditCheckOkVar"
- partnerLink="StoreToCreditAgency" portType="ca:CreditAgencyInterface"/>
-<assign name="CopyPurchaseDetails">
- <bpel:copy>
- <bpel:from>
- <bpel:literal xml:space="preserve">
- <tns:BuyConfirmed 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="" />
- </bpel:literal>
- </bpel:from>
- <bpel:to variable="buyConfirmedVar" part="content"></bpel:to>
- </bpel:copy>
- <copy>
- <from>$creditCheckOkVar.content/@id</from>
- <to>$buyConfirmedVar.content/@id</to>
- </copy>
-</assign>
- ]]></programlisting>
- </informalexample>
-
- </section>
+ <para>
+ To highlight the differences between the original generated version, and the completed
+ version, simply select both files and use the <emphasis>Compare With->Each Other</emphasis>
+ menu item.
+ </para>
+
</section>
</section>
13 years, 7 months
- 1
- 0
savara SVN: r425 - in trunk/docs/userguide/src/main/en-US: module and 1 other directory.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2010-09-30 12:04:45 -0400 (Thu, 30 Sep 2010)
New Revision: 425
Added:
trunk/docs/userguide/src/main/en-US/images/monitorprefs.png
Modified:
trunk/docs/userguide/src/main/en-US/images/editvalidatorann.png
trunk/docs/userguide/src/main/en-US/images/monitorui.png
trunk/docs/userguide/src/main/en-US/images/validatorannotation.png
trunk/docs/userguide/src/main/en-US/module/conversation-validation.xml
Log:
Update the user guide text and images.
Modified: trunk/docs/userguide/src/main/en-US/images/editvalidatorann.png
===================================================================
(Binary files differ)
Added: trunk/docs/userguide/src/main/en-US/images/monitorprefs.png
===================================================================
(Binary files differ)
Property changes on: trunk/docs/userguide/src/main/en-US/images/monitorprefs.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/docs/userguide/src/main/en-US/images/monitorui.png
===================================================================
(Binary files differ)
Modified: trunk/docs/userguide/src/main/en-US/images/validatorannotation.png
===================================================================
(Binary files differ)
Modified: trunk/docs/userguide/src/main/en-US/module/conversation-validation.xml
===================================================================
--- trunk/docs/userguide/src/main/en-US/module/conversation-validation.xml 2010-09-29 20:11:37 UTC (rev 424)
+++ trunk/docs/userguide/src/main/en-US/module/conversation-validation.xml 2010-09-30 16:04:45 UTC (rev 425)
@@ -22,39 +22,123 @@
<title>Configuration of Conversation Validation</title>
<para>
- This section explains how to configure the conversation validation mechanism to validate ESB services
+ This section explains how to configure the conversation validation mechanism to validate services
against a choreography description. The first sub-section describes how the mechanism is hooked into the
- JBossESB environment. The following two sub-sections explain two alternate ways that relevant endpoint
+ JBossESB and JBossWS-Native environments. The following two sub-sections explain two alternate ways that relevant endpoint
references can be configured for validation.
</para>
<section>
<title>Installing the Conversation Validation Mechanism</title>
- <para>
-The principle mechanism used for validating conversations within an ESB is through the use of a global filter registered with the <emphasis>jbossesb-properties.xml</emphasis>. This file is located in the <emphasis>$JBossESB/server/default/deploy/jbossesb.sar</emphasis> folder.
- </para>
- <informalexample>
- <programlisting role="XML" ><![CDATA[
- <properties name="filters">
- ...
- <property name="org.jboss.soa.esb.filter.10"
- value="org.jboss.savara.validator.jbossesb.ValidatorFilter"/>
- </properties>
- ]]></programlisting>
- </informalexample>
+
+ <section>
+ <title>JBossWS-Native</title>
+
+ <para>
+ The principle mechanism used for validating conversations within the JBossWS Native stack
+ is through the use of a global filter registered in the
+ <filename>standard-jaxws-client-config.xml</filename> and
+ <filename>standard-jaxws-endpoint-config.xml</filename> files.
+ These files are located in the <emphasis>$JBossAS/server/default/deployers/jbossws.deployter/META-INF</emphasis>
+ folder.
+ </para>
+
+ <para>
+ The <filename>standard-jaxws-client-config.xml</filename> is updated to include a
+ <emphaiss>pre handler</emphaiss> implemented by a Savara client interceptor.
+ </para>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+ <client-config>
+ <config-name>Standard Client</config-name>
+ <pre-handler-chains>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>SAVARA JBossWS-Native Client Validator Interceptor</javaee:handler-name>
+ <javaee:handler-class>org.jboss.savara.validator.jbosswsnative.JBossWSNativeClientInterceptor</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ </pre-handler-chains>
+ <feature>http://org.jboss.ws/dispatch/validate</feature>
+ <property>
+ <property-name>http://org.jboss.ws/http#chunksize</property-name>
+ <property-value>2048</property-value>
+ </property>
+ </client-config>
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ The <filename>standard-jaxws-endpoint-config.xml</filename> is updated to include a
+ <emphaiss>pre handler</emphaiss> implemented by a Savara server interceptor.
+ </para>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+ <endpoint-config>
+ <config-name>Standard Endpoint</config-name>
+ <pre-handler-chains>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>Recording Handler</javaee:handler-name>
+ <javaee:handler-class>org.jboss.wsf.framework.invocation.RecordingServerHandler</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>SAVARA JBossWS-Native Service Validator Interceptor</javaee:handler-name>
+ <javaee:handler-class>org.jboss.savara.validator.jbosswsnative.JBossWSNativeServerInterceptor</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ </pre-handler-chains>
+ </endpoint-config>
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ These interceptors are installed as part of the installation process for the SAVARA
+ distribution.
+ </para>
+ </section>
- <para>
-This filter is installed as part of the installation process for the SAVARA distribution.
- </para>
+ <section>
+ <title>JBossESB</title>
+
+ <para>
+ The principle mechanism used for validating conversations within an ESB is through the use
+ of a global filter registered with the <emphasis>jbossesb-properties.xml</emphasis>.
+ This file is located in the <emphasis>$JBossAS/server/default/deployers/esb.deployer</emphasis>
+ folder.
+ </para>
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+ <properties name="filters">
+ ...
+ <property name="org.jboss.soa.esb.filter.10"
+ value="org.jboss.savara.validator.jbossesb.ValidatorFilter"/>
+ </properties>
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ This filter is installed as part of the installation process for the SAVARA distribution.
+ </para>
+ </section>
</section>
<section>
<title>Explicit Configuration</title>
<para>
-The information concerning which destinations will be validated, and to which model/role they relate, can be explicitly
-defined within the <emphasis>validator-config.xml</emphasis> file, contained within the <emphasis>savara-validator-jbossesb.esb</emphasis> bundle.
+ The information concerning which destinations will be validated, and to which model/role
+ they relate, can be explicitly defined within the <emphasis>validator-config.xml</emphasis>
+ file, contained within the <emphasis>savara-validator-jbossesb.esb</emphasis> bundle.
</para>
+
<para>
An example of the contents of this file, that would related to the TrailBlazer example, is:
</para>
@@ -92,30 +176,58 @@
</informalexample>
<para>
-The 'validator' element has an optional attribute called 'mode', with the possible values of 'monitor' or 'manage'. If the
-mode is 'monitor' (which is the default), then any messages that result in validation errors being detected will continue to be received or sent, with the errors only be reported for information purposes. If the mode is 'manage', then any erronous messages detected during validation, that conflict with the behaviour as described in the choreography, will be prevented from being received or sent.
+ The 'validator' element has an optional attribute called 'mode', with the possible values
+ of 'monitor' or 'manage'. If the mode is 'monitor' (which is the default), then any messages
+ that result in validation errors being detected will continue to be received or sent, with
+ the errors only be reported for information purposes. If the mode is 'manage', then any
+ erronous messages detected during validation, that conflict with the behaviour as described
+ in the choreography, will be prevented from being received or sent.
</para>
<note>
<para>
- It is important to note that if 'manage' validation mode is used, then the validation mechanism will be an integral part of the message flow. This may have a slight performance impact on the delivery of messages between services.
+ It is important to note that if 'manage' validation mode is used, then the validation
+ mechanism will be an integral part of the message flow. This may have a slight performance
+ impact on the delivery of messages between services.
</para>
</note>
<para>
-The optional 'replyToTimeout' (defined in milliseconds) is used to determine how long a dynamic reply-to destination should be monitored for validation purposes. In some message exchanges, the response destination will not always be known in advance. Therefore the configuration can identify such situations, and monitor the reply-to destination for the response. However, if a response is not delivered in a particular time period, we need to be able to discontinue the validation of the dynamic endpoint. If this did not occur, then over time too many endpoints would be monitored, which may result in out-of-memory problems. The default timeout period is 10 seconds.
+ The optional 'replyToTimeout' (defined in milliseconds) is used to determine how long a dynamic
+ reply-to destination should be monitored for validation purposes. In some message exchanges,
+ the response destination will not always be known in advance. Therefore the configuration can
+ identify such situations, and monitor the reply-to destination for the response. However, if a
+ response is not delivered in a particular time period, we need to be able to discontinue the
+ validation of the dynamic endpoint. If this did not occur, then over time too many endpoints
+ would be monitored, which may result in out-of-memory problems. The default timeout period is
+ 10 seconds.
</para>
<para>
-Within the 'validator' element is a list of 'service' elements, one per service being validated. The behaviour of the service being validated is identified by specifying the model (e.g. choreography description file) and the role (e.g. participant type) within the model. Therefore, within the above configuration, the first set of destinations (eprs) are associated with the <emphasis>LoanBrokerParticipant</emphasis> defined within the choreography description model found in the file <filename>TrailBlazer.cdm</filename>, which will be located within the <filename>models</filename> folder contained within the
-<emphasis>savara-validator-jbossesb.esb</emphasis> bundle.
+ Within the 'validator' element is a list of 'service' elements, one per service being validated.
+ The behaviour of the service being validated is identified by specifying the model (e.g.
+ choreography description file) and the role (e.g. participant type) within the model. Therefore,
+ within the above configuration, the first set of destinations (eprs) are associated with the
+ <emphasis>LoanBrokerParticipant</emphasis> defined within the choreography description model
+ found in the file <filename>TrailBlazer.cdm</filename>, which will be located within the
+ <filename>models</filename> folder contained within the
+ <emphasis>savara-validator-jboss.sar</emphasis> bundle.
</para>
<para>
-The elements contained within the 'service' element define the <emphasis>input</emphasis> and <emphasis>output</emphasis> eprs (Endpoint References) that are associated with the service. The <emphasis>input</emphasis> eprs are the destinations on which messages will be received and the <emphasis>output</emphasis> eprs are the destinations on which messages will be sent by the service.
+ The elements contained within the 'service' element define the <emphasis>input</emphasis> and
+ <emphasis>output</emphasis> eprs (Endpoint References) that are associated with the service.
+ The <emphasis>input</emphasis> eprs are the destinations on which messages will be received and
+ the <emphasis>output</emphasis> eprs are the destinations on which messages will be sent by the
+ service.
</para>
<para>
-The format of the 'epr' attribute will be specific to the type of transport used for the ESB aware destination. Currently only JMS is supported, and can be identified by the protocol prefix 'jms:'.
+ The format of the 'epr' attribute will be specific to the type of transport being validated.
+ Currently JMS is supported, and can be identified by the protocol prefix 'jms:', or a
+ Web Service endpoint using a service name with the QName style of '{namespace}localpart'.
</para>
<para>
-Each 'input' and 'output' element can also define an optional 'dynamicReplyTo' boolean attribute. If defined, it will indicate to the Service Validator that the message on the specified endpoint (epr) will contain a dynamically defined 'reply-to' destination that needs to be monitored for a response.
+ Each 'input' and 'output' element can also define an optional 'dynamicReplyTo' boolean attribute.
+ If defined, it will indicate to the Service Validator that the message on the specified endpoint
+ (epr) will contain a dynamically defined 'reply-to' destination that needs to be monitored for
+ a response.
</para>
</section>
@@ -164,10 +276,30 @@
</imageobject>
<para>
- To specify the EPR for a particular message exchange, enter the EPR into the
- <emphasis>Destination</emphasis> field. If the exchange is a request, that
+ To specify the Endpoint Reference (EPR) for a particular message exchange, enter the EPR into the
+ <emphasis>Destination</emphasis> field. The value specified in this field will
+ be dependent upon the technology being validated. For example, if the JBossESB
+ is being monitored, then the value will be a physical address associated with the
+ ESB service endpoint (e.g. jms:queue/esb-quotes). If the technology being validated is a Web
+ Service (or BPEL process), then the field will represent the WSDL service name
+ specified using the QName style (e.g. {namespace}localpart).
+ </para>
+
+ <para>
+ The <emphasis>Type</emphasis> field is used to define the style of endpoint being
+ validated. In the image above, the endpoint being validated is a Web Service (or
+ BPEL process), and therefore the type is specified as a 'service name'. However if
+ the technology being validated identifies a different endpoint address, for the request
+ and response (as in the case of JBossESB), then the type should be set to
+ 'endpoint address'.
+ </para>
+
+ <para>
+ If the exchange is a request, that
will result in a response being sent on a dynamically provided "reply-to"
destination, then the <emphasis>Dynamic Reply-To</emphasis> checkbox should be selected.
+ This situation may occur in the case of validating a JBossESB service, where a
+ well-defined endpoint address has not been defined for the response.
</para>
<para>
@@ -179,7 +311,7 @@
When all of the relevant 'exchange details' components have been configured with
a <emphasis>validator</emphasis> annotation, defining the EPR to be validated,
then the choreography description file can be copied into the
- <filename>savara-validator-jbossesb.esb/models</filename> folder. This will cause
+ <filename>savara-validator-jboss.sar/models</filename> folder. This will cause
the validation mechanism to derive the configuration information from the choreography
description model, and begin validating the defined destinations against that
choreography description model.
@@ -191,49 +323,48 @@
<section>
<title>Monitoring the Choreography Description</title>
-<para>
-Once the JBossESB environment has been configured, to perform service validation of a set of ESB services against a choreography
-description, and the server has been started, then the next step is to launch a tool to view the correlated information from
-the service validators - and determine if the transactions are being correctly executed.
-</para>
-<para>
-Within an Eclipse Java project, that contains the choreography description to be monitored, a configuration file called <emphasis>pi4soa.xml</emphasis> needs to be defined on the project's classpath. This file provides details of the JMS configuration parameters required to subscribe for the information generated by the service validators. The contents of this file is:
-</para>
- <informalexample>
- <programlisting role="XML" ><![CDATA[
-<pi4soa>
- <tracker>
- <jndi>
- <initialContextFactory>org.jnp.interfaces.NamingContextFactory</initialContextFactory>
- <providerURL>jnp://localhost:1099</providerURL>
- <factoryURLPackages>org.jboss.naming:org.jnp.interfaces</factoryURLPackages>
- </jndi>
- <jms>
- <connectionFactory>ConnectionFactory</connectionFactory>
- <connectionFactoryAlternate>ConnectionFactory</connectionFactoryAlternate>
- <destination>topic/tracker</destination>
- </jms>
- </tracker>
-</pi4soa>
- ]]></programlisting>
- </informalexample>
+
+ <para>
+ Once the server environment has been configured, to perform service validation of a set of
+ services against a choreography description, and the server has been started, then the next
+ step is to configure the monitoring tool. This can be achieved by opening the
+ <emphasis>Window->Preferences->Savara->Monitor</emphasis> dialog, as shown in the following
+ image.
+ </para>
-<para>
-The destination defined in this file must match the one configured in the <emphasis>pi4soa.sar/pi4soa.xml</emphasis> file within the server.
-</para>
+ <imageobject>
+ <imagedata fileref="en-US/images/monitorprefs.png" width="5in" />
+ </imageobject>
+
<para>
-The next step is to launch the monitoring tool. This is located on the popup menu, for the choreography description (i.e. .cdm) file, by selecting the Choreography->Monitor menu item. Once the tool has been launched, it will load the choreography description, subscribe to the relevant event destination, and then indicate via a message in the bottom status line that it is ready to monitor.
+ In general, the default values specified for the JNDI and JMS properties will be fine.
+ The only information that should need to be provided is a path to the JMS and JNDI
+ libraries. When using the JBossAS server, this path can be set to the top level
+ <filename>client</filename> folder.
</para>
+
+ <para>
+ The next step is to launch the monitoring tool. This is located on the popup menu, for
+ the choreography description (i.e. .cdm) file, by selecting the Savara->Monitor menu
+ item. Once the tool has been launched, it will load the choreography description, subscribe
+ to the relevant event destination, and then indicate via a message in the bottom status line
+ that it is ready to monitor.
+ </para>
<imageobject>
<imagedata fileref="en-US/images/monitorui.png" width="5in" />
</imageobject>
<para>
- When the information is received, from the service validators representing the different participants (services), it is correlated to show the global status of the business transaction. The list of correlated interactions is show in reverse time order in the image, so in this example a <emphasis>LoanBroker</emphasis> sends a <emphasis>creditCheck</emphasis> message to a <emphasis>CreditAgency</emphasis>, followed by a <emphasis>creditCheckResult</emphasis> being returned.
+ When the information is received, from the service validators representing the different
+ participants (services), it is correlated to show the global status of the business
+ transaction. The list of correlated interactions is shown in reverse time order in the
+ image.
</para>
+
<para>
-If any <emphasis>out of sequence</emphasis> or other error situations arise, these are displayed in red.
+ If any <emphasis>out of sequence</emphasis> or other error situations arise, these are
+ displayed in red.
</para>
</section>
13 years, 7 months
- 1
- 0
savara SVN: r424 - in trunk: samples/purchasing and 1 other directories.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2010-09-29 16:11:37 -0400 (Wed, 29 Sep 2010)
New Revision: 424
Modified:
trunk/distribution/src/files/jbossws-native/standard-jaxws-client-config-validator.xml
trunk/samples/purchasing/CreditCheckRequest.xml
trunk/samples/purchasing/PurchaseGoods.cdm
trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/AbstractJBossWSNativeInterceptor.java
trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeClientInterceptor.java
trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeServerInterceptor.java
Log:
Fix various issues with monitoring a jaxws service.
Modified: trunk/distribution/src/files/jbossws-native/standard-jaxws-client-config-validator.xml
===================================================================
--- trunk/distribution/src/files/jbossws-native/standard-jaxws-client-config-validator.xml 2010-09-24 14:28:04 UTC (rev 423)
+++ trunk/distribution/src/files/jbossws-native/standard-jaxws-client-config-validator.xml 2010-09-29 20:11:37 UTC (rev 424)
@@ -5,7 +5,7 @@
<client-config>
<config-name>Standard Client</config-name>
- <post-handler-chains>
+ <pre-handler-chains>
<javaee:handler-chain>
<javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
<javaee:handler>
@@ -13,7 +13,7 @@
<javaee:handler-class>org.jboss.savara.validator.jbosswsnative.JBossWSNativeClientInterceptor</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
- </post-handler-chains>
+ </pre-handler-chains>
<feature>http://org.jboss.ws/dispatch/validate</feature>
<property>
<property-name>http://org.jboss.ws/http#chunksize</property-name>
Modified: trunk/samples/purchasing/CreditCheckRequest.xml
===================================================================
--- trunk/samples/purchasing/CreditCheckRequest.xml 2010-09-24 14:28:04 UTC (rev 423)
+++ trunk/samples/purchasing/CreditCheckRequest.xml 2010-09-29 20:11:37 UTC (rev 424)
@@ -1,4 +1,4 @@
<tns:CreditCheckRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:tns="http://www.jboss.org/examples/creditAgency"
xsi:schemaLocation="http://www.jboss.org/examples/creditAgency creditAgency.xsd "
- id="1" />
\ No newline at end of file
+ id="1" amount="200" />
\ No newline at end of file
Modified: trunk/samples/purchasing/PurchaseGoods.cdm
===================================================================
--- trunk/samples/purchasing/PurchaseGoods.cdm 2010-09-24 14:28:04 UTC (rev 423)
+++ trunk/samples/purchasing/PurchaseGoods.cdm 2010-09-29 20:11:37 UTC (rev 424)
@@ -50,26 +50,27 @@
</typeDefinitions>
<choreographies description="Choreography flow for the PurchaseGoods process" name="PurchaseGoodsProcess" root="true">
<variableDefinitions description="Channel to facilitate interaction to CreditAgency" name="CreditAgencyChannel" type="//@typeDefinitions/(a)channelTypes.0"/>
+ <variableDefinitions name="CreditCheckVar" type="//@typeDefinitions/(a)informationTypes.5"/>
<variableDefinitions description="Channel to facilitate interaction to Supplier" name="SupplierChannel" type="//@typeDefinitions/(a)channelTypes.1"/>
<variableDefinitions description="This is the variable buy" name="buy" type="//@typeDefinitions/(a)informationTypes.2"/>
- <activities xsi:type="org.pi4soa.cdl:Interaction" name="BuyRequest" operation="buy" channelVariable="//@choreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0">
+ <activities xsi:type="org.pi4soa.cdl:Interaction" name="BuyRequest" operation="buy" channelVariable="//@choreographies.0/(a)variableDefinitions.2" relationship="//@typeDefinitions/(a)relationshipTypes.0">
<exchangeDetails description="This is the exchange details for the request exchange associated with interaction BuyRequest" name="BuyRequestRequestExchange" type="//@typeDefinitions/(a)informationTypes.2">
<semanticAnnotations annotation="<validator>
	<destination name="{{Destination;The URI for the destination;string;;{http://www.jboss.org/examples/store}StoreService}}&q... type of destination;enum;endpoint address,service name;service name}}" />
		dynamicReplyTo="{{Dynamic ReplyTo;Whether the replyTo destination is dynamic;boolean;;false}}" />
</validator>
" name="validator"/>
</exchangeDetails>
</activities>
<activities xsi:type="org.pi4soa.cdl:Interaction" name="CreditCheck" operation="checkCredit" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.1">
- <exchangeDetails description="This is the exchange details for the request exchange associated with interaction CreditCheck" name="CreditCheckRequestExchange" type="//@typeDefinitions/(a)informationTypes.5">
+ <exchangeDetails description="This is the exchange details for the request exchange associated with interaction CreditCheck" name="CreditCheckRequestExchange" type="//@typeDefinitions/(a)informationTypes.5" receiveVariable="//@choreographies.0/(a)variableDefinitions.1">
<semanticAnnotations annotation="<validator>
	<destination name="{{Destination;The URI for the destination;string;;{http://www.jboss.org/examples/creditAgency}CreditAge... type of destination;enum;endpoint address,service name;service name}}" />
		dynamicReplyTo="{{Dynamic ReplyTo;Whether the replyTo destination is dynamic;boolean;;false}}" />
</validator>
" name="validator"/>
</exchangeDetails>
</activities>
<activities xsi:type="org.pi4soa.cdl:Choice" description="Is credit ok?">
- <activities xsi:type="org.pi4soa.cdl:Sequence" description="Credit Valid">
+ <activities xsi:type="org.pi4soa.cdl:Conditional" name="CreditValid" expression="cdl:getVariable('CreditCheckVar','','//@amount','CreditAgency') < 250">
<activities xsi:type="org.pi4soa.cdl:Interaction" name="CreditCheckOk" operation="checkCredit" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.1">
<exchangeDetails description="This is the exchange details for the respond exchange associated with interaction CreditCheckOk" name="CreditCheckOkRespondExchange" type="//@typeDefinitions/(a)informationTypes.4" action="Respond">
<semanticAnnotations annotation="<validator>
	<destination name="{{Destination;The URI for the destination;string;;{http://www.jboss.org/examples/creditAgency}CreditAge... type of destination;enum;endpoint address,service name;service name}}" />
		dynamicReplyTo="{{Dynamic ReplyTo;Whether the replyTo destination is dynamic;boolean;;false}}" />
</validator>
" name="validator"/>
</exchangeDetails>
</activities>
- <activities xsi:type="org.pi4soa.cdl:Interaction" name="BuyConfirmed" operation="buy" channelVariable="//@choreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0">
+ <activities xsi:type="org.pi4soa.cdl:Interaction" name="BuyConfirmed" operation="buy" channelVariable="//@choreographies.0/(a)variableDefinitions.2" relationship="//@typeDefinitions/(a)relationshipTypes.0">
<exchangeDetails description="This is the exchange details for the respond exchange associated with interaction BuyConfirmed" name="BuyConfirmedRespondExchange" type="//@typeDefinitions/(a)informationTypes.0" action="Respond">
<semanticAnnotations annotation="<validator>
	<destination name="{{Destination;The URI for the destination;string;;{http://www.jboss.org/examples/store}StoreService}}&q... type of destination;enum;endpoint address,service name;service name}}" />
		dynamicReplyTo="{{Dynamic ReplyTo;Whether the replyTo destination is dynamic;boolean;;false}}" />
</validator>
" name="validator"/>
</exchangeDetails>
@@ -81,7 +82,7 @@
<semanticAnnotations annotation="<validator>
	<destination name="{{Destination;The URI for the destination;string;;{http://www.jboss.org/examples/creditAgency}CreditAge... type of destination;enum;endpoint address,service name;service name}}" />
		dynamicReplyTo="{{Dynamic ReplyTo;Whether the replyTo destination is dynamic;boolean;;false}}" />
</validator>
" name="validator"/>
</exchangeDetails>
</activities>
- <activities xsi:type="org.pi4soa.cdl:Interaction" name="BuyFailed" operation="buy" channelVariable="//@choreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0">
+ <activities xsi:type="org.pi4soa.cdl:Interaction" name="BuyFailed" operation="buy" channelVariable="//@choreographies.0/(a)variableDefinitions.2" relationship="//@typeDefinitions/(a)relationshipTypes.0">
<exchangeDetails description="This is the exchange details for the respond exchange associated with interaction BuyFailed" name="BuyFailedRespondExchange" type="//@typeDefinitions/(a)informationTypes.1" action="Respond" faultName="BuyFailed">
<semanticAnnotations annotation="<validator>
	<destination name="{{Destination;The URI for the destination;string;;{http://www.jboss.org/examples/store}StoreService}}&q... type of destination;enum;endpoint address,service name;service name}}" />
		dynamicReplyTo="{{Dynamic ReplyTo;Whether the replyTo destination is dynamic;boolean;;false}}" />
</validator>
" name="validator"/>
</exchangeDetails>
Modified: trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/AbstractJBossWSNativeInterceptor.java
===================================================================
--- trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/AbstractJBossWSNativeInterceptor.java 2010-09-24 14:28:04 UTC (rev 423)
+++ trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/AbstractJBossWSNativeInterceptor.java 2010-09-29 20:11:37 UTC (rev 424)
@@ -36,6 +36,7 @@
import org.apache.commons.logging.LogFactory;
import org.jboss.savara.validator.Endpoint;
import org.jboss.savara.validator.ServiceValidatorManager;
+import org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS;
import org.jboss.ws.metadata.umdm.ParameterMetaData;
import org.jboss.wsf.common.DOMWriter;
import org.jboss.wsf.common.handler.GenericSOAPHandler;
@@ -96,7 +97,7 @@
* @return The message type
* @throws SOAPException Failed to determine the message type
*/
- public static String getMessageType(SOAPMessageContext soapCtx) throws SOAPException {
+ public static String getMessageType(SOAPMessageContext soapCtx, boolean request) throws SOAPException {
String ret=null;
if (soapCtx instanceof org.jboss.ws.core.jaxws.handler.MessageContextJAXWS) {
@@ -104,21 +105,31 @@
(org.jboss.ws.core.jaxws.handler.MessageContextJAXWS)soapCtx;
org.jboss.ws.metadata.umdm.OperationMetaData opmetadata=mc.getOperationMetaData();
- if (opmetadata.getInputParameters().size() == 1) {
- ParameterMetaData pmd=opmetadata.getInputParameters().get(0);
+ if (opmetadata != null) {
+ ParameterMetaData pmd=null;
- // TODO: Find out why 'genericParam' is generated when the parameter
- // is a complex type
- if (pmd.getXmlName().getLocalPart().equals("genericParam")) {
-
- // Extract message value
- SOAPElement elem=getMessageBody(soapCtx);
-
- ret = elem.getElementQName().toString();
-
- } else {
- ret = pmd.getXmlName().toString();
- }
+ if (request && opmetadata.getInputParameters().size() == 1) {
+ pmd = opmetadata.getInputParameters().get(0);
+ } else if (!request && opmetadata.getOutputParameters().size() == 1) {
+ pmd = opmetadata.getOutputParameters().get(0);
+ }
+
+ if (pmd != null) {
+ // TODO: Find out why 'genericParam' is generated when the parameter
+ // is a complex type
+ if (pmd.getXmlName().getLocalPart().equals("genericParam")) {
+
+ // Extract message value
+ SOAPElement elem=getMessageBody(soapCtx);
+
+ if (elem != null) {
+ ret = elem.getElementQName().toString();
+ }
+
+ } else {
+ ret = pmd.getXmlName().toString();
+ }
+ }
}
}
@@ -131,7 +142,14 @@
// Extract message value
SOAPBody soapBody = soapCtx.getMessage().getSOAPPart().getEnvelope().getBody();
- ret = (SOAPElement)soapBody.getChildElements().next();
+ java.util.Iterator<?> iter=soapBody.getChildElements();
+ while (ret == null && iter.hasNext()) {
+ Object body=iter.next();
+
+ if (body instanceof SOAPElement) {
+ ret = (SOAPElement)body;
+ }
+ }
if (ret instanceof SOAPFault) {
SOAPFault fault=(SOAPFault)ret;
@@ -154,6 +172,15 @@
if (logger.isDebugEnabled()) {
logger.debug("Service for endpoint = "+service);
+
+ if (service == null && soapCtx instanceof SOAPMessageContextJAXWS) {
+ SOAPMessageContextJAXWS smc=(SOAPMessageContextJAXWS)soapCtx;
+
+ if (smc.getEndpointMetaData() != null &&
+ smc.getEndpointMetaData().getServiceMetaData() != null) {
+ service = smc.getEndpointMetaData().getServiceMetaData().getServiceName();
+ }
+ }
}
return(service == null ? null : new Endpoint(service.toString()));
Modified: trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeClientInterceptor.java
===================================================================
--- trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeClientInterceptor.java 2010-09-24 14:28:04 UTC (rev 423)
+++ trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeClientInterceptor.java 2010-09-29 20:11:37 UTC (rev 424)
@@ -53,7 +53,7 @@
for (int i=0; validators != null &&
i < validators.size(); i++) {
try {
- validators.get(i).messageReceived(getMessageType(soapCtx), getMessage(soapCtx));
+ validators.get(i).messageReceived(getMessageType(soapCtx, false), getMessage(soapCtx));
validated = true;
} catch(Exception t) {
// Ignore
@@ -108,7 +108,7 @@
for (int i=0; validators != null &&
i < validators.size(); i++) {
try {
- validators.get(i).messageSent(getMessageType(soapCtx), getMessage(soapCtx));
+ validators.get(i).messageSent(getMessageType(soapCtx, true), getMessage(soapCtx));
validated = true;
} catch(Exception t) {
// Ignore
Modified: trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeServerInterceptor.java
===================================================================
--- trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeServerInterceptor.java 2010-09-24 14:28:04 UTC (rev 423)
+++ trunk/validators/jboss/wsnative/src/main/java/org/jboss/savara/validator/jbosswsnative/JBossWSNativeServerInterceptor.java 2010-09-29 20:11:37 UTC (rev 424)
@@ -53,7 +53,7 @@
for (int i=0; validators != null &&
i < validators.size(); i++) {
try {
- validators.get(i).messageReceived(getMessageType(soapCtx), getMessage(soapCtx));
+ validators.get(i).messageReceived(getMessageType(soapCtx, true), getMessage(soapCtx));
validated = true;
} catch(Exception t) {
// Ignore
@@ -108,7 +108,7 @@
for (int i=0; validators != null &&
i < validators.size(); i++) {
try {
- validators.get(i).messageSent(getMessageType(soapCtx), getMessage(soapCtx));
+ validators.get(i).messageSent(getMessageType(soapCtx, false), getMessage(soapCtx));
validated = true;
} catch(Exception t) {
// Ignore
13 years, 7 months
- 1
- 0
Build failed in Hudson: savara-1.1.x #1
by jboss-qa-internal＠redhat.com
See <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/1/>
------------------------------------------
[...truncated 8424 lines...]
Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/ap...
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/apache/xm...
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/apache/xm... (4 KB at 2.4 KB/sec)
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...> into <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (default-generate) @ userguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...]>
[INFO] creating FOP user-config DOM
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...]>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:bundle (default-bundle) @ userguide ---
[INFO] Building jar: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (generate-docbook) @ userguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...> into <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (generate-docbook) @ userguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...]>
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ userguide >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ userguide <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ userguide ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ userguide ---
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma...
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma... (5 KB at 4.3 KB/sec)
[INFO] Installing <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/usergu...> to <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...>
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Docs::GettingStartedGuide 1.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ gettingstartedguide ---
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (default-resources) @ gettingstartedguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...> into <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (default-generate) @ gettingstartedguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...]>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:bundle (default-bundle) @ gettingstartedguide ---
[INFO] Building jar: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (generate-docbook) @ gettingstartedguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...> into <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (generate-docbook) @ gettingstartedguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...]>
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ gettingstartedguide >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ gettingstartedguide <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ gettingstartedguide ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ gettingstartedguide ---
[INFO] Installing <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/gettin...> to <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...>
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Docs::SamplesGuide 1.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ samplesguide ---
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (default-resources) @ samplesguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...> into <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (default-generate) @ samplesguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...]>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:bundle (default-bundle) @ samplesguide ---
[INFO] Building jar: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (generate-docbook) @ samplesguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...> into <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (generate-docbook) @ samplesguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...]>
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ samplesguide >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ samplesguide <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ samplesguide ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ samplesguide ---
[INFO] Installing <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/sources/docs/sample...> to <http://hudson.qa.jboss.com/hudson/job/savara-1.1.x/ws/m2-repository/org/j...>
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping Savara::Distribution
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Savara ............................................ SUCCESS [54.811s]
[INFO] Savara::Validators ................................ SUCCESS [0.027s]
[INFO] Savara::Validators::JBoss ......................... SUCCESS [0.025s]
[INFO] Savara::Validators::JBoss::Common ................. FAILURE [10:28.344s]
[INFO] Savara::Validators::JBoss::ESB .................... SKIPPED
[INFO] Savara::Validators::JBoss::WS-Native .............. SKIPPED
[INFO] Savara::Tools ..................................... SUCCESS [0.161s]
[INFO] Savara::Tools::Plugins ............................ SUCCESS [0.011s]
[INFO] Savara::Tools::Plugins::ScribbleCore .............. SUCCESS [3:49.647s]
[INFO] Savara::Tools::Plugins::ContractModel ............. SUCCESS [12.718s]
[INFO] Savara::Tools::Plugins::ScribbleConversationModel . SUCCESS [2.752s]
[INFO] Savara::Tools::Plugins::ScribbleConversationParser SUCCESS [2.646s]
[INFO] Savara::Tools::Plugins::ScribbleExpressionXPath ... SUCCESS [2.612s]
[INFO] Savara::Tools::Plugins::ScribbleEclipse ........... SUCCESS [2.970s]
[INFO] Savara::Tools::Plugins::Pi4SOACDM ................. SUCCESS [3.625s]
[INFO] Savara::Tools::Plugins::ProtocolContract .......... SUCCESS [2.838s]
[INFO] Savara::Tools::Plugins::ToolsTAPModel ............. SUCCESS [16.596s]
[INFO] Savara::Tools::Plugins::ToolsTAPValidation ........ SUCCESS [12.927s]
[INFO] Savara::Tools::Plugins::ToolsTAPValidation ........ SUCCESS [2.653s]
[INFO] Savara::Tools::Plugins::ScribbleLangModel ......... SUCCESS [2.534s]
[INFO] Savara::Tools::Plugins::ToolsWSDL ................. SUCCESS [2.896s]
[INFO] Savara::Tools::Plugins::ToolsBPEL ................. SUCCESS [4.142s]
[INFO] Savara::Tools::Plugins::ToolsValidator ............ SUCCESS [2.822s]
[INFO] Savara::Tools::Plugins::ToolsBPMN ................. SUCCESS [3.241s]
[INFO] Savara::Tools::Plugins::ToolsMonitor .............. SUCCESS [3.869s]
[INFO] Savara::Tools::Plugins::ScribbleConformance ....... SUCCESS [3.037s]
[INFO] Savara::Tools::Plugins::ScribbleConversationComparator SUCCESS [2.709s]
[INFO] Savara::Tools::Plugins::ScribbleConversationExportText SUCCESS [12.769s]
[INFO] Savara::Tools::Plugins::ScribbleConversationProjector SUCCESS [2.724s]
[INFO] Savara::Tools::Plugins::ScribbleConversationValidation SUCCESS [2.806s]
[INFO] Savara::Tools::Features ........................... SUCCESS [0.012s]
[INFO] Savara::Tools::Features::ScribbleProtocol ......... SUCCESS [1.980s]
[INFO] Savara::Tools::Features::SavaraTools .............. SUCCESS [2.297s]
[INFO] Savara::Tools::Tests .............................. SUCCESS [0.011s]
[INFO] Savara::Tools::Tests::ProtocolContract ............ SUCCESS [35:41.527s]
[INFO] Savara::Tools::Tests::ToolsWSDL ................... SUCCESS [34.558s]
[INFO] Savara::Tools::Site ............................... SUCCESS [6.247s]
[INFO] Savara::Docs ...................................... SUCCESS [0.021s]
[INFO] Savara::Docs::UserGuide ........................... SUCCESS [2:27.369s]
[INFO] Savara::Docs::GettingStartedGuide ................. SUCCESS [58.757s]
[INFO] Savara::Docs::SamplesGuide ........................ SUCCESS [41.975s]
[INFO] Savara::Distribution .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:24:19.593s
[INFO] Finished at: Fri Sep 24 07:00:57 EDT 2010
[INFO] Final Memory: 186M/725M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "jboss-nexus" could not be activated because it does not exist.
[ERROR] Failed to execute goal on project savara-validator-jboss: Missing:
----------
1) org.pi4soa:org.pi4soa.common:jar:3.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.common:jar:3.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.cdl:jar:3.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.cdl -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.cdl -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.cdl:jar:3.1.0-SNAPSHOT
3) org.pi4soa:org.pi4soa.service:jar:3.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.service -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.service -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.service:jar:3.1.0-SNAPSHOT
----------
3 required artifacts are missing.
for artifact:
org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
from the specified remote repositories:
jboss-deprecated (https://repository.jboss.org/nexus/content/repositories/deprecated/, releases=true, snapshots=false),
jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/, releases=true, snapshots=true),
pi4soa (http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools..., releases=true, snapshots=true),
central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoun...
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :savara-validator-jboss
Terminating xvnc.
[savara-1.1.x] $ vncserver -kill :36
Killing Xvnc process ID 22034
Recording test results
Archiving artifacts
13 years, 7 months
- 1
- 4
savara SVN: r423 - branches/1.1.x/docs and 2 other directories.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2010-09-24 10:28:04 -0400 (Fri, 24 Sep 2010)
New Revision: 423
Modified:
branches/1.1.x/docs/pom.xml
branches/1.1.x/pom.xml
trunk/docs/pom.xml
trunk/pom.xml
Log:
Fix missing plugin repository.
Modified: branches/1.1.x/docs/pom.xml
===================================================================
--- branches/1.1.x/docs/pom.xml 2010-09-22 15:04:06 UTC (rev 422)
+++ branches/1.1.x/docs/pom.xml 2010-09-24 14:28:04 UTC (rev 423)
@@ -22,4 +22,15 @@
<module>samplesguide</module>
</modules>
+ <pluginRepositories>
+ <pluginRepository>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ <id>jboss.release</id>
+ <name>JBoss releases</name>
+ <url>http://repository.jboss.org/maven2</url>
+ </pluginRepository>
+ </pluginRepositories>
+
</project>
Modified: branches/1.1.x/pom.xml
===================================================================
--- branches/1.1.x/pom.xml 2010-09-22 15:04:06 UTC (rev 422)
+++ branches/1.1.x/pom.xml 2010-09-24 14:28:04 UTC (rev 423)
@@ -126,9 +126,9 @@
<repositories>
<repository>
- <id>jboss-developer-repository-group</id>
- <name>JBoss Developer Maven Repository Group</name>
- <url>https://repository.jboss.org/nexus/content/groups/developer/</url>
+ <id>jboss-public-repository-group</id>
+ <name>JBoss Public Maven Repository Group</name>
+ <url>https://repository.jboss.org/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
Modified: trunk/docs/pom.xml
===================================================================
--- trunk/docs/pom.xml 2010-09-22 15:04:06 UTC (rev 422)
+++ trunk/docs/pom.xml 2010-09-24 14:28:04 UTC (rev 423)
@@ -22,4 +22,15 @@
<module>samplesguide</module>
</modules>
+ <pluginRepositories>
+ <pluginRepository>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ <id>jboss.release</id>
+ <name>JBoss releases</name>
+ <url>http://repository.jboss.org/maven2</url>
+ </pluginRepository>
+ </pluginRepositories>
+
</project>
Modified: trunk/pom.xml
===================================================================
--- trunk/pom.xml 2010-09-22 15:04:06 UTC (rev 422)
+++ trunk/pom.xml 2010-09-24 14:28:04 UTC (rev 423)
@@ -126,9 +126,9 @@
<repositories>
<repository>
- <id>jboss-developer-repository-group</id>
- <name>JBoss Developer Maven Repository Group</name>
- <url>https://repository.jboss.org/nexus/content/groups/developer/</url>
+ <id>jboss-public-repository-group</id>
+ <name>JBoss Public Maven Repository Group</name>
+ <url>https://repository.jboss.org/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
13 years, 7 months
- 1
- 0
Build failed in Hudson: savara #91
by jboss-qa-internal＠redhat.com
See <http://hudson.qa.jboss.com/hudson/job/savara/91/changes>
Changes:
[nickboldt] https://jira.jboss.org/browse/JBIDE-6938 add optional subclipse site to index.html for update site installation
------------------------------------------
[...truncated 8410 lines...]
Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/ap...
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/apache/xm...
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/apache/xm... (4 KB at 2.5 KB/sec)
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/j...> into <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (default-generate) @ userguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...]>
[INFO] creating FOP user-config DOM
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...]>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:bundle (default-bundle) @ userguide ---
[INFO] Building jar: <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (generate-docbook) @ userguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/j...> into <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (generate-docbook) @ userguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...]>
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ userguide >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ userguide <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ userguide ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ userguide ---
Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma...
Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/apache/ma... (5 KB at 4.1 KB/sec)
[INFO] Installing <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/userguide/ta...> to <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/s...>
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Docs::GettingStartedGuide 1.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ gettingstartedguide ---
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (default-resources) @ gettingstartedguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/j...> into <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (default-generate) @ gettingstartedguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...]>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:bundle (default-bundle) @ gettingstartedguide ---
[INFO] Building jar: <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (generate-docbook) @ gettingstartedguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/j...> into <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (generate-docbook) @ gettingstartedguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...]>
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ gettingstartedguide >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ gettingstartedguide <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ gettingstartedguide ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ gettingstartedguide ---
[INFO] Installing <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/gettingstart...> to <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/s...>
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Savara::Docs::SamplesGuide 1.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ samplesguide ---
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (default-resources) @ samplesguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/j...> into <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (default-generate) @ samplesguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...]>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:bundle (default-bundle) @ samplesguide ---
[INFO] Building jar: <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:resources (generate-docbook) @ samplesguide ---
[INFO] Expanding: <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/j...> into <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...>
[INFO]
[INFO] --- maven-jdocbook-plugin:2.2.3:generate (generate-docbook) @ samplesguide ---
[INFO] Processing en-US -> pdf
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...]>
[INFO] Processing en-US -> html
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...]>
[INFO] Processing en-US -> html_single
redirecting output to file [<http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...]>
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ samplesguide >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ samplesguide <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ samplesguide ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ samplesguide ---
[INFO] Installing <http://hudson.qa.jboss.com/hudson/job/savara/ws/sources/docs/samplesguide...> to <http://hudson.qa.jboss.com/hudson/job/savara/ws/m2-repository/org/jboss/s...>
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping Savara::Distribution
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Savara ............................................ SUCCESS [48.030s]
[INFO] Savara::Validators ................................ SUCCESS [0.017s]
[INFO] Savara::Validators::JBoss ......................... SUCCESS [0.016s]
[INFO] Savara::Validators::JBoss::Common ................. FAILURE [8:38.936s]
[INFO] Savara::Validators::JBoss::ESB .................... SKIPPED
[INFO] Savara::Validators::JBoss::WS-Native .............. SKIPPED
[INFO] Savara::Tools ..................................... SUCCESS [0.126s]
[INFO] Savara::Tools::Plugins ............................ SUCCESS [0.010s]
[INFO] Savara::Tools::Plugins::ScribbleCore .............. SUCCESS [2:36.641s]
[INFO] Savara::Tools::Plugins::ContractModel ............. SUCCESS [2.028s]
[INFO] Savara::Tools::Plugins::ScribbleConversationModel . SUCCESS [2.339s]
[INFO] Savara::Tools::Plugins::ScribbleConversationParser SUCCESS [2.421s]
[INFO] Savara::Tools::Plugins::ScribbleExpressionXPath ... SUCCESS [2.267s]
[INFO] Savara::Tools::Plugins::ScribbleEclipse ........... SUCCESS [1.815s]
[INFO] Savara::Tools::Plugins::Pi4SOACDM ................. SUCCESS [2.166s]
[INFO] Savara::Tools::Plugins::ProtocolContract .......... SUCCESS [1.607s]
[INFO] Savara::Tools::Plugins::ToolsTAPModel ............. SUCCESS [11.655s]
[INFO] Savara::Tools::Plugins::ToolsTAPValidation ........ SUCCESS [1.736s]
[INFO] Savara::Tools::Plugins::ToolsTAPValidation ........ SUCCESS [1.740s]
[INFO] Savara::Tools::Plugins::ScribbleLangModel ......... SUCCESS [1.565s]
[INFO] Savara::Tools::Plugins::ToolsWSDL ................. SUCCESS [1.758s]
[INFO] Savara::Tools::Plugins::ToolsBPEL ................. SUCCESS [2.433s]
[INFO] Savara::Tools::Plugins::ToolsValidator ............ SUCCESS [1.652s]
[INFO] Savara::Tools::Plugins::ToolsBPMN ................. SUCCESS [1.878s]
[INFO] Savara::Tools::Plugins::ToolsMonitor .............. SUCCESS [2.435s]
[INFO] Savara::Tools::Plugins::ScribbleConformance ....... SUCCESS [1.734s]
[INFO] Savara::Tools::Plugins::ScribbleConversationComparator SUCCESS [1.763s]
[INFO] Savara::Tools::Plugins::ScribbleConversationExportText SUCCESS [1.666s]
[INFO] Savara::Tools::Plugins::ScribbleConversationProjector SUCCESS [1.628s]
[INFO] Savara::Tools::Plugins::ScribbleConversationValidation SUCCESS [1.602s]
[INFO] Savara::Tools::Features ........................... SUCCESS [0.011s]
[INFO] Savara::Tools::Features::ScribbleProtocol ......... SUCCESS [1.236s]
[INFO] Savara::Tools::Features::SavaraTools .............. SUCCESS [1.254s]
[INFO] Savara::Tools::Tests .............................. SUCCESS [0.017s]
[INFO] Savara::Tools::Tests::ProtocolContract ............ SUCCESS [7:34.079s]
[INFO] Savara::Tools::Tests::ToolsWSDL ................... SUCCESS [14.634s]
[INFO] Savara::Tools::Site ............................... SUCCESS [3.694s]
[INFO] Savara::Docs ...................................... SUCCESS [0.015s]
[INFO] Savara::Docs::UserGuide ........................... SUCCESS [2:12.211s]
[INFO] Savara::Docs::GettingStartedGuide ................. SUCCESS [26.519s]
[INFO] Savara::Docs::SamplesGuide ........................ SUCCESS [18.509s]
[INFO] Savara::Distribution .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38:26.081s
[INFO] Finished at: Thu Sep 23 22:29:24 EDT 2010
[INFO] Final Memory: 258M/892M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "jboss-nexus" could not be activated because it does not exist.
[ERROR] Failed to execute goal on project savara-validator-jboss: Missing:
----------
1) org.pi4soa:org.pi4soa.service:jar:3.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.service -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.service -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.service:jar:3.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.common:jar:3.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.common:jar:3.1.0-SNAPSHOT
3) org.pi4soa:org.pi4soa.cdl:jar:3.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.cdl -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.pi4soa -DartifactId=org.pi4soa.cdl -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
2) org.pi4soa:org.pi4soa.cdl:jar:3.1.0-SNAPSHOT
----------
3 required artifacts are missing.
for artifact:
org.jboss.savara.validators:savara-validator-jboss:pom:1.1.0-SNAPSHOT
from the specified remote repositories:
jboss-deprecated (https://repository.jboss.org/nexus/content/repositories/deprecated/, releases=true, snapshots=false),
jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/, releases=true, snapshots=true),
pi4soa (http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools..., releases=true, snapshots=true),
central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoun...
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :savara-validator-jboss
Terminating xvnc.
[savara] $ vncserver -kill :47
Killing Xvnc process ID 22308
Recording test results
Archiving artifacts
13 years, 7 months
- 1
- 1
Build failed in Hudson: savara #88
by jboss-qa-internal＠redhat.com
See <http://hudson.qa.jboss.com/hudson/job/savara/88/>
------------------------------------------
Started by an SCM change
Building remotely on soa4-rhel5-x86_64
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
<http://hudson.qa.jboss.com/hudson/job/savara/ws/> does not exist.
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:474)
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:451)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:105)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:87)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1901)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Archiving artifacts
13 years, 7 months
- 1
- 1
Build failed in Hudson: savara #84
by jboss-qa-internal＠redhat.com
See <http://hudson.qa.jboss.com/hudson/job/savara/84/>
------------------------------------------
Started by an SCM change
Building remotely on soa4-rhel5-x86_64
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: <http://hudson.qa.jboss.com/hudson/job/savara/ws/>
at hudson.FilePath.mkdirs(FilePath.java:814)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)
Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
<http://hudson.qa.jboss.com/hudson/job/savara/ws/> does not exist.
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:474)
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:451)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:105)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:87)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1901)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Archiving artifacts
13 years, 7 months
- 1
- 3
savara SVN: r422 - branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor and 17 other directories.
by do-not-reply＠jboss.org
Author: objectiser
Date: 2010-09-22 11:04:06 -0400 (Wed, 22 Sep 2010)
New Revision: 422
Added:
branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java
branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java
branches/1.1.x/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/
branches/1.1.x/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java
trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java
trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java
trunk/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/
trunk/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java
Removed:
branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/action/
trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/action/ValidateAction.java
Modified:
branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF
branches/1.1.x/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java
branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java
branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java
branches/1.1.x/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java
trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF
trunk/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java
trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java
trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java
trunk/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java
Log:
Adding marker resolution back in with support for showing referenced descriptions.
Modified: branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF
===================================================================
--- branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF 2010-09-22 11:07:50 UTC (rev 421)
+++ branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF 2010-09-22 15:04:06 UTC (rev 422)
@@ -23,7 +23,9 @@
Scribble-Extensions: org.jboss.savara.pi4soa.cdm.parser.CDMTokenizer,
org.jboss.savara.pi4soa.cdm.parser.CDMModelParserRule,
org.jboss.savara.pi4soa.cdm.model.CDMNotation,
+ org.jboss.savara.pi4soa.cdm.model.SCNNotation,
org.jboss.savara.pi4soa.cdm.validation.TypeReferenceValidationRule,
- org.jboss.savara.pi4soa.cdm.editor.CDMEditorManager
+ org.jboss.savara.pi4soa.cdm.editor.CDMEditorManager,
+ org.jboss.savara.pi4soa.cdm.editor.SCNEditorManager
Export-Package: org.jboss.savara.pi4soa.cdm.model,
org.jboss.savara.pi4soa.cdm.parser
Added: branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java
===================================================================
--- branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java (rev 0)
+++ branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -0,0 +1,114 @@
+/*
+ * Copyright 2005-8 Pi4 Technologies Ltd
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ *
+ * Change History:
+ * 19 Jun 2008 : Initial version created by gary
+ */
+package org.jboss.savara.pi4soa.cdm.editor;
+
+import org.eclipse.emf.ecore.EValidator;
+import org.jboss.savara.pi4soa.cdm.model.*;
+import org.scribble.extensions.RegistryInfo;
+import org.scribble.model.ModelReference;
+import org.scribble.model.SourceRef;
+import org.scribble.model.admin.ModelIssue;
+import org.scribble.editor.*;
+
+/**
+ * This is the CDM designer's implementation of the EditorManager
+ * interface.
+ */
+(a)RegistryInfo(extension=EditorManager.class,notation=SCNNotation.NOTATION_CODE) //preference=10,
+public class SCNEditorManager extends AbstractEditorManager {
+
+ /**
+ * This method focuses the editor on the specified source,
+ * identified by the model reference and source reference.
+ *
+ * @param mref The model reference
+ * @param sref The component source reference
+ * @param prop Additional properties
+ */
+ public void focus(ModelReference mref, SourceRef sref,
+ java.util.Map<String,Object> props) {
+ String uri=null;
+ org.eclipse.core.resources.IFile file=
+ org.scribble.eclipse.model.admin.OSGIModelRepository.getFile(mref);
+
+ if (file == null || file.exists() == false) {
+ file = org.scribble.eclipse.model.admin.OSGIModelRepository.getGlobalFile(mref);
+ }
+
+ if (file != null && file.exists()) {
+ uri = file.getFullPath().toPortableString();
+ }
+
+ if (uri != null) {
+ org.eclipse.ui.IWorkbenchPage page=
+ org.eclipse.ui.PlatformUI.getWorkbench().
+ getActiveWorkbenchWindow().getActivePage();
+
+ org.eclipse.core.resources.IResource res=
+ org.eclipse.core.resources.ResourcesPlugin.getWorkspace().getRoot().findMember(uri);
+
+ if (res instanceof org.eclipse.core.resources.IFile) {
+ org.eclipse.ui.part.FileEditorInput input=
+ new org.eclipse.ui.part.FileEditorInput(
+ (org.eclipse.core.resources.IFile)res);
+
+ try {
+ org.eclipse.ui.IEditorPart part=page.openEditor(input,
+ "org.pi4soa.scenario.designer.Pi4SOAScenarioDesignerID");
+
+ if (part instanceof org.pi4soa.designer.editor.ChoreographyDescriptionEditor) {
+ org.pi4soa.designer.editor.ChoreographyDescriptionEditor editor=
+ (org.pi4soa.designer.editor.ChoreographyDescriptionEditor)part;
+
+ /* Other approach using marker - can be used if editor does not
+ * provide alternative way to focus on component.
+ org.eclipse.core.resources.IMarker marker=res.createMarker(EValidator.MARKER);
+ marker.setAttribute(EValidator.URI_ATTRIBUTE, ref.getComponentURI());
+ editor.gotoMarker(marker);
+ marker.delete();
+ */
+
+ editor.showComponent(sref.getComponentURI());
+ }
+
+ } catch(Exception e) {
+ e.printStackTrace();
+ }
+ }
+ }
+ }
+
+ /**
+ * This method enriches the set of properties required
+ * by the editor, using the properties associated with
+ * the model issue.
+ *
+ * @param issue The model issue
+ */
+ @Override
+ public void enrich(ModelIssue issue) {
+
+ if (issue.getModelObject() != null) {
+ // Set the EMF URI attribute
+ issue.getProperties().put(EValidator.URI_ATTRIBUTE,
+ issue.getModelObject().getSource().getComponentURI());
+ }
+ }
+}
Added: branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java
===================================================================
--- branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java (rev 0)
+++ branches/1.1.x/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -0,0 +1,67 @@
+/*
+ * Copyright 2005-8 Pi4 Technologies Ltd
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ *
+ * Change History:
+ * 17 Jun 2008 : Initial version created by gary
+ */
+package org.jboss.savara.pi4soa.cdm.model;
+
+import org.scribble.extensions.*;
+import org.scribble.model.ModelReference;
+import org.scribble.model.Notation;
+
+/**
+ * This class represents the SCN notation implementation.
+ */
+(a)RegistryInfo(extension=org.scribble.model.Notation.class)
+public class SCNNotation extends org.scribble.model.AbstractNotation {
+
+ public static final String NOTATION_CODE="scn";
+
+ /**
+ * This is the constructor for the CDM notation.
+ */
+ public SCNNotation() {
+ super(NOTATION_CODE, "SCN", false);
+ }
+
+ /**
+ * This method returns the initial description associated
+ * with the supplied reference.
+ *
+ * @param ref The reference
+ * @return The initial description, or null if no description
+ */
+ public String getInitialDescription(ModelReference ref) {
+ StringBuffer buf=new StringBuffer();
+
+ return(buf.toString());
+ }
+
+ /**
+ * This method returns the optional 'super' notation.
+ * If defined, then this notation is a derived notation
+ * from the 'super' notation.
+ *
+ * @return The optional 'super' notation
+ */
+ @Override
+ public Notation getSuperNotation() {
+ return(m_superNotation);
+ }
+
+ private Notation m_superNotation=new org.scribble.conversation.model.ConversationNotation();
+}
Modified: branches/1.1.x/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java
===================================================================
--- branches/1.1.x/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java 2010-09-22 11:07:50 UTC (rev 421)
+++ branches/1.1.x/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -100,6 +100,8 @@
}
}
+ e.printStackTrace();
+
error(e.getMessage());
}
Modified: branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java
===================================================================
--- branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java 2010-09-22 11:07:50 UTC (rev 421)
+++ branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -43,8 +43,10 @@
import org.jboss.savara.tap.model.Relationship;
import org.jboss.savara.tap.model.Resource;
import org.jboss.savara.tap.model.admin.ResourceLoader;
+import org.scribble.model.ModelReference;
import org.scribble.model.admin.ModelIssue;
import org.scribble.model.admin.ModelListener;
+import org.scribble.model.resolutions.ShowReferencedDescription;
import org.w3c.dom.Document;
import org.xml.sax.SAXException;
@@ -168,39 +170,43 @@
Resource toResource=(Resource)rel.getRef();
if (toResource !=null) {
- for (RelationshipValidator rv : m_relationshipValidators) {
+ // Obtain input stream for resource
+ ResourceLoader fromRL=getResourceLoader(resource);
+ ResourceLoader toRL=getResourceLoader(toResource);
+
+ if (fromRL == null) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00001"), resource.getId())));
+ } else if (toRL == null) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00001"), toResource.getId())));
+ } else if (!fromRL.exists(resource)) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00002"), resource.getId())));
+ } else if (!toRL.exists(toResource)) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00002"), toResource.getId())));
+ } else {
+ ModelReference ref=toRL.getModelReference(toResource);
- if (rv.isSupported(rel, resource, toResource)) {
- // Obtain input stream for resource
- ResourceLoader fromRL=getResourceLoader(resource);
- ResourceLoader toRL=getResourceLoader(toResource);
+ ModelListener proxyml=new InnerModelListener(ref, ml);
+
+ for (RelationshipValidator rv : m_relationshipValidators) {
- if (fromRL == null) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00001"), resource.getId())));
- } else if (toRL == null) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00001"), toResource.getId())));
- } else if (!fromRL.exists(resource)) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00002"), resource.getId())));
- } else if (!toRL.exists(toResource)) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00002"), toResource.getId())));
- } else {
- rv.validate(rel, resource, fromRL, toResource, toRL, ml);
+ if (rv.isSupported(rel, resource, toResource)) {
+ rv.validate(rel, resource, fromRL, toResource, toRL, proxyml);
break;
}
@@ -316,4 +322,39 @@
}
}
}
+
+ public class InnerModelListener implements ModelListener {
+
+ private ModelListener m_listener=null;
+ private ModelReference m_reference=null;
+
+ public InnerModelListener(ModelReference ref, ModelListener l) {
+ m_reference = ref;
+ m_listener = l;
+ }
+
+ public void error(ModelIssue issue) {
+
+ ShowReferencedDescription res=new ShowReferencedDescription();
+ res.setModel(m_reference);
+
+ if (issue.getModelObject() != null) {
+ res.setSourceReference(issue.getModelObject().getSource());
+ }
+
+ issue.getResolutions().add(res);
+
+ m_listener.error(issue);
+ }
+
+ public void warning(ModelIssue issue) {
+ ShowReferencedDescription res=new ShowReferencedDescription();
+ res.setModel(m_reference);
+ res.setSourceReference(issue.getModelObject().getSource());
+
+ issue.getResolutions().add(res);
+
+ m_listener.warning(issue);
+ }
+ }
}
Modified: branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java
===================================================================
--- branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java 2010-09-22 11:07:50 UTC (rev 421)
+++ branches/1.1.x/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -7,7 +7,6 @@
import org.jboss.savara.tap.validation.RelationshipValidator;
import org.jboss.savara.tap.validation.ResourceValidator;
import org.jboss.savara.tap.validation.TAPValidator;
-import org.jboss.savara.tap.validation.action.ValidateAction;
import org.osgi.framework.BundleContext;
import org.osgi.framework.ServiceReference;
Modified: branches/1.1.x/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java
===================================================================
--- branches/1.1.x/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java 2010-09-22 11:07:50 UTC (rev 421)
+++ branches/1.1.x/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -127,9 +127,15 @@
SourceRef sref=new SourceRef();
sref.setComponentURI((String)getProperties().get(SOURCE_REF_COMPONENT_URI));
sref.setModelObjectURI((String)getProperties().get(SOURCE_REF_MODEL_OBJECT_URI));
- sref.setStartPosition((Integer)getProperties().get(SOURCE_REF_START_POSITION));
- sref.setEndPosition((Integer)getProperties().get(SOURCE_REF_END_POSITION));
+ if (getProperties().containsKey(SOURCE_REF_START_POSITION)) {
+ sref.setStartPosition((Integer)getProperties().get(SOURCE_REF_START_POSITION));
+ }
+
+ if (getProperties().containsKey(SOURCE_REF_END_POSITION)) {
+ sref.setEndPosition((Integer)getProperties().get(SOURCE_REF_END_POSITION));
+ }
+
// Recover the properties for model and source ref
java.util.Iterator<String> iter=getProperties().keySet().iterator();
while (iter.hasNext()) {
Added: branches/1.1.x/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java
===================================================================
--- branches/1.1.x/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java (rev 0)
+++ branches/1.1.x/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -0,0 +1,206 @@
+/*
+ * Copyright 2007 Pi4 Technologies Ltd
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ *
+ * Change History:
+ * 1 Dec 2007 : Initial version created by gary
+ */
+package org.scribble.eclipse.resolutions;
+
+import java.util.Comparator;
+import java.util.logging.Level;
+import java.util.logging.Logger;
+
+import org.eclipse.core.resources.IMarker;
+import org.eclipse.swt.graphics.Image;
+import org.eclipse.ui.internal.UIPlugin;
+import org.scribble.eclipse.model.admin.OSGIModelListener;
+import org.scribble.model.*;
+import org.scribble.model.admin.ModelIssue;
+import org.scribble.model.resolutions.Resolution;
+import org.scribble.util.*;
+
+/**
+ * This class represents the implementation of the marker
+ * resolution generator interface, responsible for
+ * providing resolutions related to markers.
+ *
+ */
+public class MarkerResolutionGenerator
+ implements org.eclipse.ui.IMarkerResolutionGenerator2 {
+
+ /**
+ * This method determines whether there are available resolutions
+ * for the supplied marker.
+ *
+ * @param marker The marker
+ * @return Whether resolutions are available
+ */
+ public boolean hasResolutions(org.eclipse.core.resources.IMarker marker) {
+ boolean ret=false;
+
+ try {
+ ret = ModelIssueUtil.hasResolutions(marker.getAttributes());
+ } catch(Exception e) {
+ e.printStackTrace();
+ }
+
+ return(ret);
+ }
+
+ /**
+ * This method returns any available resolutions for the supplied
+ * marker.
+ *
+ * @param marker The marker
+ * @return The list of available resolutions
+ */
+ public org.eclipse.ui.IMarkerResolution[] getResolutions(org.eclipse.core.resources.IMarker marker) {
+ org.eclipse.ui.IMarkerResolution[] ret=null;
+
+ try {
+ java.util.List<Resolution> resolutions=
+ ModelIssueUtil.deserializeResolutions(marker.getAttributes());
+
+ java.util.Collections.sort(resolutions, new ResolutionComparator());
+
+ ret = new org.eclipse.ui.IMarkerResolution[resolutions.size()];
+
+ for (int i=0; i < resolutions.size(); i++) {
+ ret[i] = new MarkerResolutionWrapper(resolutions.get(i));
+ }
+ } catch(Exception e) {
+ e.printStackTrace();
+ }
+
+ /*
+ String resolutions=marker.getAttribute(org.scribble.model.ModelListener.RESOLUTIONS, null);
+
+ try {
+ java.util.List<org.eclipse.ui.IMarkerResolution> impls=
+ new java.util.Vector<org.eclipse.ui.IMarkerResolution>();
+
+ java.util.StringTokenizer st=new java.util.StringTokenizer(resolutions,",");
+
+ while (st.hasMoreTokens()) {
+ String resolution=st.nextToken();
+
+ if (resolution.equals(ModelListener.SHOW_EXTERNAL_ISSUE_RESOLUTION)) {
+ impls.add(new ShowExternalIssue());
+ } else if (resolution.equals(ModelListener.SHOW_REFERENCE_DESCRIPTION_RESOLUTION)) {
+ impls.add(new ShowReferencedDescription());
+ } else {
+ try {
+ Class<?> cls=Class.forName(resolution);
+
+ org.eclipse.ui.IMarkerResolution res=
+ (org.eclipse.ui.IMarkerResolution)cls.newInstance();
+
+ impls.add(res);
+ } catch(Exception cnfe) {
+ org.scribble.osgi.eclipse.Activator.logError(
+ "Failed to instantiate resolution '"+resolution+"'", cnfe);
+ }
+ }
+ }
+
+ ret = new org.eclipse.ui.IMarkerResolution[impls.size()];
+
+ impls.toArray(ret);
+
+ } catch(Exception e) {
+ org.scribble.osgi.eclipse.Activator.logError(
+ "Failed to instantiate resolution '"+resolutions+"'", e);
+ }
+ */
+
+ return(ret);
+ }
+
+ private static Logger logger = Logger.getLogger("org.scribble.osgi.resolutions");
+
+ public class ResolutionComparator implements Comparator<Resolution> {
+
+ public int compare(Resolution res1, Resolution res2) {
+ return(res1.getName().compareTo(res2.getName()));
+ }
+ }
+
+ public class MarkerResolutionWrapper implements org.eclipse.ui.IMarkerResolution2 {
+
+ public MarkerResolutionWrapper(Resolution res) {
+ m_resolution = res;
+ }
+
+ public String getLabel() {
+ return(m_resolution.getName());
+ }
+
+ public String getDescription() {
+ return(m_resolution.getDescription());
+ }
+
+ public Image getImage() {
+ // TODO Auto-generated method stub
+ return null;
+ }
+
+ public void run(IMarker marker) {
+ try {
+ ModelIssue issue=new ModelIssue();
+ issue.setMessage((String)marker.getAttribute(IMarker.MESSAGE));
+ issue.getProperties().putAll(marker.getAttributes());
+
+ SourceRef obj=new SourceRef();
+ obj.setStartPosition(((Integer)marker.getAttribute(IMarker.CHAR_START, 0)).intValue());
+ obj.setEndPosition(((Integer)marker.getAttribute(IMarker.CHAR_END, 0)).intValue());
+ obj.setModelObjectURI((String)marker.getAttribute(OSGIModelListener.SOURCE_MODEL_OBJECT_URI));
+ obj.setComponentURI((String)marker.getAttribute(OSGIModelListener.SOURCE_COMPONENT_URI));
+
+ ModelReference ref=new ModelReference(
+ (String)marker.getAttribute(OSGIModelListener.MODEL_NAMESPACE),
+ (String)marker.getAttribute(OSGIModelListener.MODEL_LOCALPART),
+ (String)marker.getAttribute(OSGIModelListener.MODEL_LOCATED_ROLE),
+ (String)marker.getAttribute(OSGIModelListener.MODEL_NOTATION));
+
+ // Recover the properties for model ref
+ java.util.Iterator<String> iter=
+ marker.getAttributes().keySet().iterator();
+ while (iter.hasNext()) {
+ String name=iter.next();
+
+ if (name.startsWith(OSGIModelListener.MODEL_PROP_PREFIX)) {
+ Object value=marker.getAttributes().get(name);
+
+ name = name.substring(OSGIModelListener.MODEL_PROP_PREFIX.length());
+
+ ref.setProperty(name, value);
+ }
+ }
+
+ m_resolution.resolve(ref, obj, issue);
+ } catch(Exception e) {
+
+ org.eclipse.jface.dialogs.MessageDialog.openError(
+ UIPlugin.getDefault().getWorkbench().getDisplay().getActiveShell(),
+ "Error", e.getLocalizedMessage());
+
+ logger.log(Level.SEVERE, "Failed to resolve", e);
+ }
+ }
+
+ private Resolution m_resolution=null;
+ }
+}
Modified: trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF
===================================================================
--- trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF 2010-09-22 11:07:50 UTC (rev 421)
+++ trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/META-INF/MANIFEST.MF 2010-09-22 15:04:06 UTC (rev 422)
@@ -23,7 +23,9 @@
Scribble-Extensions: org.jboss.savara.pi4soa.cdm.parser.CDMTokenizer,
org.jboss.savara.pi4soa.cdm.parser.CDMModelParserRule,
org.jboss.savara.pi4soa.cdm.model.CDMNotation,
+ org.jboss.savara.pi4soa.cdm.model.SCNNotation,
org.jboss.savara.pi4soa.cdm.validation.TypeReferenceValidationRule,
- org.jboss.savara.pi4soa.cdm.editor.CDMEditorManager
+ org.jboss.savara.pi4soa.cdm.editor.CDMEditorManager,
+ org.jboss.savara.pi4soa.cdm.editor.SCNEditorManager
Export-Package: org.jboss.savara.pi4soa.cdm.model,
org.jboss.savara.pi4soa.cdm.parser
Added: trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java
===================================================================
--- trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java (rev 0)
+++ trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/editor/SCNEditorManager.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -0,0 +1,114 @@
+/*
+ * Copyright 2005-8 Pi4 Technologies Ltd
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ *
+ * Change History:
+ * 19 Jun 2008 : Initial version created by gary
+ */
+package org.jboss.savara.pi4soa.cdm.editor;
+
+import org.eclipse.emf.ecore.EValidator;
+import org.jboss.savara.pi4soa.cdm.model.*;
+import org.scribble.extensions.RegistryInfo;
+import org.scribble.model.ModelReference;
+import org.scribble.model.SourceRef;
+import org.scribble.model.admin.ModelIssue;
+import org.scribble.editor.*;
+
+/**
+ * This is the CDM designer's implementation of the EditorManager
+ * interface.
+ */
+(a)RegistryInfo(extension=EditorManager.class,notation=SCNNotation.NOTATION_CODE) //preference=10,
+public class SCNEditorManager extends AbstractEditorManager {
+
+ /**
+ * This method focuses the editor on the specified source,
+ * identified by the model reference and source reference.
+ *
+ * @param mref The model reference
+ * @param sref The component source reference
+ * @param prop Additional properties
+ */
+ public void focus(ModelReference mref, SourceRef sref,
+ java.util.Map<String,Object> props) {
+ String uri=null;
+ org.eclipse.core.resources.IFile file=
+ org.scribble.eclipse.model.admin.OSGIModelRepository.getFile(mref);
+
+ if (file == null || file.exists() == false) {
+ file = org.scribble.eclipse.model.admin.OSGIModelRepository.getGlobalFile(mref);
+ }
+
+ if (file != null && file.exists()) {
+ uri = file.getFullPath().toPortableString();
+ }
+
+ if (uri != null) {
+ org.eclipse.ui.IWorkbenchPage page=
+ org.eclipse.ui.PlatformUI.getWorkbench().
+ getActiveWorkbenchWindow().getActivePage();
+
+ org.eclipse.core.resources.IResource res=
+ org.eclipse.core.resources.ResourcesPlugin.getWorkspace().getRoot().findMember(uri);
+
+ if (res instanceof org.eclipse.core.resources.IFile) {
+ org.eclipse.ui.part.FileEditorInput input=
+ new org.eclipse.ui.part.FileEditorInput(
+ (org.eclipse.core.resources.IFile)res);
+
+ try {
+ org.eclipse.ui.IEditorPart part=page.openEditor(input,
+ "org.pi4soa.scenario.designer.Pi4SOAScenarioDesignerID");
+
+ if (part instanceof org.pi4soa.designer.editor.ChoreographyDescriptionEditor) {
+ org.pi4soa.designer.editor.ChoreographyDescriptionEditor editor=
+ (org.pi4soa.designer.editor.ChoreographyDescriptionEditor)part;
+
+ /* Other approach using marker - can be used if editor does not
+ * provide alternative way to focus on component.
+ org.eclipse.core.resources.IMarker marker=res.createMarker(EValidator.MARKER);
+ marker.setAttribute(EValidator.URI_ATTRIBUTE, ref.getComponentURI());
+ editor.gotoMarker(marker);
+ marker.delete();
+ */
+
+ editor.showComponent(sref.getComponentURI());
+ }
+
+ } catch(Exception e) {
+ e.printStackTrace();
+ }
+ }
+ }
+ }
+
+ /**
+ * This method enriches the set of properties required
+ * by the editor, using the properties associated with
+ * the model issue.
+ *
+ * @param issue The model issue
+ */
+ @Override
+ public void enrich(ModelIssue issue) {
+
+ if (issue.getModelObject() != null) {
+ // Set the EMF URI attribute
+ issue.getProperties().put(EValidator.URI_ATTRIBUTE,
+ issue.getModelObject().getSource().getComponentURI());
+ }
+ }
+}
Added: trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java
===================================================================
--- trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java (rev 0)
+++ trunk/tools/plugins/org.jboss.savara.pi4soa.cdm/src/java/org/jboss/savara/pi4soa/cdm/model/SCNNotation.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -0,0 +1,67 @@
+/*
+ * Copyright 2005-8 Pi4 Technologies Ltd
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ *
+ * Change History:
+ * 17 Jun 2008 : Initial version created by gary
+ */
+package org.jboss.savara.pi4soa.cdm.model;
+
+import org.scribble.extensions.*;
+import org.scribble.model.ModelReference;
+import org.scribble.model.Notation;
+
+/**
+ * This class represents the SCN notation implementation.
+ */
+(a)RegistryInfo(extension=org.scribble.model.Notation.class)
+public class SCNNotation extends org.scribble.model.AbstractNotation {
+
+ public static final String NOTATION_CODE="scn";
+
+ /**
+ * This is the constructor for the CDM notation.
+ */
+ public SCNNotation() {
+ super(NOTATION_CODE, "SCN", false);
+ }
+
+ /**
+ * This method returns the initial description associated
+ * with the supplied reference.
+ *
+ * @param ref The reference
+ * @return The initial description, or null if no description
+ */
+ public String getInitialDescription(ModelReference ref) {
+ StringBuffer buf=new StringBuffer();
+
+ return(buf.toString());
+ }
+
+ /**
+ * This method returns the optional 'super' notation.
+ * If defined, then this notation is a derived notation
+ * from the 'super' notation.
+ *
+ * @return The optional 'super' notation
+ */
+ @Override
+ public Notation getSuperNotation() {
+ return(m_superNotation);
+ }
+
+ private Notation m_superNotation=new org.scribble.conversation.model.ConversationNotation();
+}
Modified: trunk/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java
===================================================================
--- trunk/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java 2010-09-22 11:07:50 UTC (rev 421)
+++ trunk/tools/plugins/org.jboss.savara.tap.eclipse/src/java/org/jboss/savara/tap/eclipse/actions/ValidateAction.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -100,6 +100,8 @@
}
}
+ e.printStackTrace();
+
error(e.getMessage());
}
Modified: trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java
===================================================================
--- trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java 2010-09-22 11:07:50 UTC (rev 421)
+++ trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/TAPValidator.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -43,8 +43,10 @@
import org.jboss.savara.tap.model.Relationship;
import org.jboss.savara.tap.model.Resource;
import org.jboss.savara.tap.model.admin.ResourceLoader;
+import org.scribble.model.ModelReference;
import org.scribble.model.admin.ModelIssue;
import org.scribble.model.admin.ModelListener;
+import org.scribble.model.resolutions.ShowReferencedDescription;
import org.w3c.dom.Document;
import org.xml.sax.SAXException;
@@ -168,39 +170,43 @@
Resource toResource=(Resource)rel.getRef();
if (toResource !=null) {
- for (RelationshipValidator rv : m_relationshipValidators) {
+ // Obtain input stream for resource
+ ResourceLoader fromRL=getResourceLoader(resource);
+ ResourceLoader toRL=getResourceLoader(toResource);
+
+ if (fromRL == null) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00001"), resource.getId())));
+ } else if (toRL == null) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00001"), toResource.getId())));
+ } else if (!fromRL.exists(resource)) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00002"), resource.getId())));
+ } else if (!toRL.exists(toResource)) {
+ l.error(new ModelIssue(null,
+ MessageFormat.format(
+ java.util.PropertyResourceBundle.getBundle(
+ "org.jboss.savara.tap.validation.Messages").
+ getString("SAVARATAPV-00002"), toResource.getId())));
+ } else {
+ ModelReference ref=toRL.getModelReference(toResource);
- if (rv.isSupported(rel, resource, toResource)) {
- // Obtain input stream for resource
- ResourceLoader fromRL=getResourceLoader(resource);
- ResourceLoader toRL=getResourceLoader(toResource);
+ ModelListener proxyml=new InnerModelListener(ref, ml);
+
+ for (RelationshipValidator rv : m_relationshipValidators) {
- if (fromRL == null) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00001"), resource.getId())));
- } else if (toRL == null) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00001"), toResource.getId())));
- } else if (!fromRL.exists(resource)) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00002"), resource.getId())));
- } else if (!toRL.exists(toResource)) {
- l.error(new ModelIssue(null,
- MessageFormat.format(
- java.util.PropertyResourceBundle.getBundle(
- "org.jboss.savara.tap.validation.Messages").
- getString("SAVARATAPV-00002"), toResource.getId())));
- } else {
- rv.validate(rel, resource, fromRL, toResource, toRL, ml);
+ if (rv.isSupported(rel, resource, toResource)) {
+ rv.validate(rel, resource, fromRL, toResource, toRL, proxyml);
break;
}
@@ -316,4 +322,39 @@
}
}
}
+
+ public class InnerModelListener implements ModelListener {
+
+ private ModelListener m_listener=null;
+ private ModelReference m_reference=null;
+
+ public InnerModelListener(ModelReference ref, ModelListener l) {
+ m_reference = ref;
+ m_listener = l;
+ }
+
+ public void error(ModelIssue issue) {
+
+ ShowReferencedDescription res=new ShowReferencedDescription();
+ res.setModel(m_reference);
+
+ if (issue.getModelObject() != null) {
+ res.setSourceReference(issue.getModelObject().getSource());
+ }
+
+ issue.getResolutions().add(res);
+
+ m_listener.error(issue);
+ }
+
+ public void warning(ModelIssue issue) {
+ ShowReferencedDescription res=new ShowReferencedDescription();
+ res.setModel(m_reference);
+ res.setSourceReference(issue.getModelObject().getSource());
+
+ issue.getResolutions().add(res);
+
+ m_listener.warning(issue);
+ }
+ }
}
Deleted: trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/action/ValidateAction.java
===================================================================
--- trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/action/ValidateAction.java 2010-09-22 11:07:50 UTC (rev 421)
+++ trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/action/ValidateAction.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -1,214 +0,0 @@
-/*
- * Copyright 2005-8 Pi4 Technologies Ltd
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- *
- *
- * Change History:
- * 17 Jan, 2008 : Initial version created by gary
- */
-package org.jboss.savara.tap.validation.action;
-
-import java.io.IOException;
-import java.util.logging.Logger;
-
-import javax.xml.XMLConstants;
-import javax.xml.parsers.DocumentBuilder;
-import javax.xml.parsers.DocumentBuilderFactory;
-import javax.xml.parsers.ParserConfigurationException;
-import javax.xml.transform.Source;
-import javax.xml.transform.dom.DOMSource;
-import javax.xml.transform.stream.StreamSource;
-import javax.xml.validation.Schema;
-import javax.xml.validation.SchemaFactory;
-import javax.xml.validation.Validator;
-
-import org.eclipse.core.resources.IFile;
-import org.eclipse.core.resources.IResource;
-import org.eclipse.core.runtime.CoreException;
-import org.eclipse.jface.action.IAction;
-import org.eclipse.jface.viewers.ISelection;
-import org.eclipse.jface.viewers.StructuredSelection;
-import org.eclipse.swt.SWT;
-import org.eclipse.swt.widgets.MessageBox;
-import org.eclipse.ui.IObjectActionDelegate;
-import org.eclipse.ui.IWorkbenchPart;
-import org.jboss.savara.tap.model.Project;
-import org.jboss.savara.tap.model.admin.TAPModelUtil;
-import org.jboss.savara.tap.validation.TAPValidator;
-import org.scribble.eclipse.model.admin.OSGIModelListener;
-import org.scribble.model.admin.ModelIssue;
-import org.scribble.model.admin.ModelListener;
-import org.w3c.dom.Document;
-import org.xml.sax.SAXException;
-
-/**
- * This class invokes the validation action on the selected
- * TAP file.
- *
- */
-public class ValidateAction implements IObjectActionDelegate {
-
- private static Logger logger = Logger.getLogger(ValidateAction.class.getName());
-
- private ISelection m_selection=null;
- private IWorkbenchPart m_targetPart=null;
- //private static TAPValidator m_validator=new TAPValidator();
-
- public ValidateAction() {
- }
-
- /**
- * This method returns the validator.
- *
- * @return The validator
- */
- /*
- public static TAPValidator getValidator() {
- return(m_validator);
- }
- */
-
- /**
- * This method implements the action's run method.
- *
- * @param action The action
- */
- public void run(IAction action) {
- /*
- if (m_selection instanceof StructuredSelection) {
- StructuredSelection sel=(StructuredSelection)m_selection;
-
- IResource res=(IResource)sel.getFirstElement();
-
- // Obtain the TAP model from the resource
- if (res instanceof IFile) {
- Project project=null;
- OSGIModelListener l=new OSGIModelListener(res);
-
- // Check the XML document is valid
- if (isValidTAPDocument((IFile)res, l)) {
-
- try {
- java.io.InputStream is=((IFile)res).getContents();
-
- project = TAPModelUtil.deserialize(is);
-
- is.close();
- } catch(Exception e) {
- error(e.getMessage());
- }
-
- if (project != null) {
- m_validator.validate(project, l);
- }
- }
-
- l.finished();
- }
- }
- */
- }
-
- protected boolean isValidTAPDocument(IFile file, ModelListener l) {
- boolean ret=false;
-
- try {
-
- // Parse an XML document into a DOM tree.
- DocumentBuilderFactory f=DocumentBuilderFactory.newInstance();
- f.setNamespaceAware(true);
-
- DocumentBuilder parser=f.newDocumentBuilder();
-
- java.io.InputStream is=file.getContents();
- Document document = parser.parse(is);
-
- is.close();
-
- // Create a SchemaFactory capable of understanding WXS schemas.
- SchemaFactory factory =
- SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
-
- // Load a WXS schema, represented by a Schema instance.
- java.io.InputStream schemais=ValidateAction.class.getResourceAsStream("/tap.xsd");
-
- Source schemaFile = new StreamSource(schemais);
- Schema schema = factory.newSchema(schemaFile);
-
- schemais.close();
-
- // Create a Validator object, which can be used to validate
- // an instance document.
- Validator validator = schema.newValidator();
-
- // Validate the DOM tree.
- validator.validate(new DOMSource(document));
-
- ret = true;
-
- } catch (ParserConfigurationException e) {
- l.error(new ModelIssue(null, "Failed to parse TAP document: "+e.getMessage()));
- } catch (SAXException e) {
- l.error(new ModelIssue(null, "Invalid TAP document: "+e.getMessage()));
- } catch (IOException e) {
- l.error(new ModelIssue(null, "Failed to load TAP document: "+e.getMessage()));
- } catch (CoreException e) {
- l.error(new ModelIssue(null, "Failed to load TAP document: "+e.getMessage()));
- }
-
- return(ret);
- }
-
- /**
- * This method is used to report an error.
- *
- * @param mesg The error message
- */
- public void error(String mesg) {
-
- logger.severe("Error occurred: "+mesg);
-
- MessageBox mbox=new MessageBox(m_targetPart.getSite().getShell(),
- SWT.ICON_ERROR|SWT.OK);
-
- if (mesg == null) {
- mesg = "Null pointer exception has occurred";
- }
-
- mbox.setMessage(mesg);
- mbox.open();
- }
-
- /**
- * This method indicates that the selection has changed.
- *
- * @param action The action
- * @param selection The selection
- */
- public void selectionChanged(IAction action,
- ISelection selection) {
- m_selection = selection;
- }
-
- /**
- * This method sets the currently active workbench part.
- *
- * @param action The action
- * @param targetPart The active workbench part
- */
- public void setActivePart(IAction action,
- IWorkbenchPart targetPart) {
- m_targetPart = targetPart;
- }
-}
Modified: trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java
===================================================================
--- trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java 2010-09-22 11:07:50 UTC (rev 421)
+++ trunk/tools/plugins/org.jboss.savara.tap.validation/src/java/org/jboss/savara/tap/validation/osgi/Activator.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -7,7 +7,6 @@
import org.jboss.savara.tap.validation.RelationshipValidator;
import org.jboss.savara.tap.validation.ResourceValidator;
import org.jboss.savara.tap.validation.TAPValidator;
-import org.jboss.savara.tap.validation.action.ValidateAction;
import org.osgi.framework.BundleContext;
import org.osgi.framework.ServiceReference;
Modified: trunk/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java
===================================================================
--- trunk/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java 2010-09-22 11:07:50 UTC (rev 421)
+++ trunk/tools/plugins/org.scribble.core/src/java/org/scribble/model/resolutions/ShowReferencedDescription.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -127,9 +127,15 @@
SourceRef sref=new SourceRef();
sref.setComponentURI((String)getProperties().get(SOURCE_REF_COMPONENT_URI));
sref.setModelObjectURI((String)getProperties().get(SOURCE_REF_MODEL_OBJECT_URI));
- sref.setStartPosition((Integer)getProperties().get(SOURCE_REF_START_POSITION));
- sref.setEndPosition((Integer)getProperties().get(SOURCE_REF_END_POSITION));
+ if (getProperties().containsKey(SOURCE_REF_START_POSITION)) {
+ sref.setStartPosition((Integer)getProperties().get(SOURCE_REF_START_POSITION));
+ }
+
+ if (getProperties().containsKey(SOURCE_REF_END_POSITION)) {
+ sref.setEndPosition((Integer)getProperties().get(SOURCE_REF_END_POSITION));
+ }
+
// Recover the properties for model and source ref
java.util.Iterator<String> iter=getProperties().keySet().iterator();
while (iter.hasNext()) {
Added: trunk/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java
===================================================================
--- trunk/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java (rev 0)
+++ trunk/tools/plugins/org.scribble.eclipse/src/java/org/scribble/eclipse/resolutions/MarkerResolutionGenerator.java 2010-09-22 15:04:06 UTC (rev 422)
@@ -0,0 +1,206 @@
+/*
+ * Copyright 2007 Pi4 Technologies Ltd
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ *
+ * Change History:
+ * 1 Dec 2007 : Initial version created by gary
+ */
+package org.scribble.eclipse.resolutions;
+
+import java.util.Comparator;
+import java.util.logging.Level;
+import java.util.logging.Logger;
+
+import org.eclipse.core.resources.IMarker;
+import org.eclipse.swt.graphics.Image;
+import org.eclipse.ui.internal.UIPlugin;
+import org.scribble.eclipse.model.admin.OSGIModelListener;
+import org.scribble.model.*;
+import org.scribble.model.admin.ModelIssue;
+import org.scribble.model.resolutions.Resolution;
+import org.scribble.util.*;
+
+/**
+ * This class represents the implementation of the marker
+ * resolution generator interface, responsible for
+ * providing resolutions related to markers.
+ *
+ */
+public class MarkerResolutionGenerator
+ implements org.eclipse.ui.IMarkerResolutionGenerator2 {
+
+ /**
+ * This method determines whether there are available resolutions
+ * for the supplied marker.
+ *
+ * @param marker The marker
+ * @return Whether resolutions are available
+ */
+ public boolean hasResolutions(org.eclipse.core.resources.IMarker marker) {
+ boolean ret=false;
+
+ try {
+ ret = ModelIssueUtil.hasResolutions(marker.getAttributes());
+ } catch(Exception e) {
+ e.printStackTrace();
+ }
+
+ return(ret);
+ }
+
+ /**
+ * This method returns any available resolutions for the supplied
+ * marker.
+ *
+ * @param marker The marker
+ * @return The list of available resolutions
+ */
+ public org.eclipse.ui.IMarkerResolution[] getResolutions(org.eclipse.core.resources.IMarker marker) {
+ org.eclipse.ui.IMarkerResolution[] ret=null;
+
+ try {
+ java.util.List<Resolution> resolutions=
+ ModelIssueUtil.deserializeResolutions(marker.getAttributes());
+
+ java.util.Collections.sort(resolutions, new ResolutionComparator());
+
+ ret = new org.eclipse.ui.IMarkerResolution[resolutions.size()];
+
+ for (int i=0; i < resolutions.size(); i++) {
+ ret[i] = new MarkerResolutionWrapper(resolutions.get(i));
+ }
+ } catch(Exception e) {
+ e.printStackTrace();
+ }
+
+ /*
+ String resolutions=marker.getAttribute(org.scribble.model.ModelListener.RESOLUTIONS, null);
+
+ try {
+ java.util.List<org.eclipse.ui.IMarkerResolution> impls=
+ new java.util.Vector<org.eclipse.ui.IMarkerResolution>();
+
+ java.util.StringTokenizer st=new java.util.StringTokenizer(resolutions,",");
+
+ while (st.hasMoreTokens()) {
+ String resolution=st.nextToken();
+
+ if (resolution.equals(ModelListener.SHOW_EXTERNAL_ISSUE_RESOLUTION)) {
+ impls.add(new ShowExternalIssue());
+ } else if (resolution.equals(ModelListener.SHOW_REFERENCE_DESCRIPTION_RESOLUTION)) {
+ impls.add(new ShowReferencedDescription());
+ } else {
+ try {
+ Class<?> cls=Class.forName(resolution);
+
+ org.eclipse.ui.IMarkerResolution res=
+ (org.eclipse.ui.IMarkerResolution)cls.newInstance();
+
+ impls.add(res);
+ } catch(Exception cnfe) {
+ org.scribble.osgi.eclipse.Activator.logError(
+ "Failed to instantiate resolution '"+resolution+"'", cnfe);
+ }
+ }
+ }
+
+ ret = new org.eclipse.ui.IMarkerResolution[impls.size()];
+
+ impls.toArray(ret);
+
+ } catch(Exception e) {
+ org.scribble.osgi.eclipse.Activator.logError(
+ "Failed to instantiate resolution '"+resolutions+"'", e);
+ }
+ */
+
+ return(ret);
+ }
+
+ private static Logger logger = Logger.getLogger("org.scribble.osgi.resolutions");
+
+ public class ResolutionComparator implements Comparator<Resolution> {
+
+ public int compare(Resolution res1, Resolution res2) {
+ return(res1.getName().compareTo(res2.getName()));
+ }
+ }
+
+ public class MarkerResolutionWrapper implements org.eclipse.ui.IMarkerResolution2 {
+
+ public MarkerResolutionWrapper(Resolution res) {
+ m_resolution = res;
+ }
+
+ public String getLabel() {
+ return(m_resolution.getName());
+ }
+
+ public String getDescription() {
+ return(m_resolution.getDescription());
+ }
+
+ public Image getImage() {
+ // TODO Auto-generated method stub
+ return null;
+ }
+
+ public void run(IMarker marker) {
+ try {
+ ModelIssue issue=new ModelIssue();
+ issue.setMessage((String)marker.getAttribute(IMarker.MESSAGE));
+ issue.getProperties().putAll(marker.getAttributes());
+
+ SourceRef obj=new SourceRef();
+ obj.setStartPosition(((Integer)marker.getAttribute(IMarker.CHAR_START, 0)).intValue());
+ obj.setEndPosition(((Integer)marker.getAttribute(IMarker.CHAR_END, 0)).intValue());
+ obj.setModelObjectURI((String)marker.getAttribute(OSGIModelListener.SOURCE_MODEL_OBJECT_URI));
+ obj.setComponentURI((String)marker.getAttribute(OSGIModelListener.SOURCE_COMPONENT_URI));
+
+ ModelReference ref=new ModelReference(
+ (String)marker.getAttribute(OSGIModelListener.MODEL_NAMESPACE),
+ (String)marker.getAttribute(OSGIModelListener.MODEL_LOCALPART),
+ (String)marker.getAttribute(OSGIModelListener.MODEL_LOCATED_ROLE),
+ (String)marker.getAttribute(OSGIModelListener.MODEL_NOTATION));
+
+ // Recover the properties for model ref
+ java.util.Iterator<String> iter=
+ marker.getAttributes().keySet().iterator();
+ while (iter.hasNext()) {
+ String name=iter.next();
+
+ if (name.startsWith(OSGIModelListener.MODEL_PROP_PREFIX)) {
+ Object value=marker.getAttributes().get(name);
+
+ name = name.substring(OSGIModelListener.MODEL_PROP_PREFIX.length());
+
+ ref.setProperty(name, value);
+ }
+ }
+
+ m_resolution.resolve(ref, obj, issue);
+ } catch(Exception e) {
+
+ org.eclipse.jface.dialogs.MessageDialog.openError(
+ UIPlugin.getDefault().getWorkbench().getDisplay().getActiveShell(),
+ "Error", e.getLocalizedMessage());
+
+ logger.log(Level.SEVERE, "Failed to resolve", e);
+ }
+ }
+
+ private Resolution m_resolution=null;
+ }
+}
13 years, 7 months
- 1
- 0