savara-commits November 2009

savara-commits@lists.jboss.org

1 participants
25 discussions

savara SVN: r96 - in runtime/trunk/samples/jbossesb: brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier and 5 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-30 12:00:08 -0500 (Mon, 30 Nov 2009) New Revision: 96 Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetCreditCheckRequestMessageAction.java runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderConfirmRequestAction.java runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderRejectMessageAction.java runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetQuotesListAction.java runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetRequestQuoteMessageAction.java runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetOrderConfirmResponseAction.java runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetQuoteMessageAction.java runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BrokerClient.java runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BuyerClient.java runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckInvalidMessageAction.java runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckResponseMessageAction.java runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/wsdl/CreditAgencyService.java runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyFailedMessageAction.java runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyResponseMessageAction.java runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetCreditCheckRequestMessageAction.java Log: SAVARA-7 - updated ESB action code to use message type with namespace. Still need to check web service access. Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetCreditCheckRequestMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetCreditCheckRequestMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetCreditCheckRequestMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -42,7 +42,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - sbuffer.append("<CreditCheckRequest id=\"" + idValue +"\">"); + sbuffer.append("<CreditCheckRequest xmlns=\"http://www.jboss.org/examples/creditAgency\" id=\"" + idValue +"\">"); NodeList list = node.getChildNodes(); for (int i =0; i < list.getLength(); i++) { Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderConfirmRequestAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderConfirmRequestAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderConfirmRequestAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -44,7 +44,7 @@ public Message process(Message message) throws Exception { Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - message.getBody().add("<orderConfirmed id=\"" + idValue +"\" supplierDesc=\"{http://www.jboss.org/savara/loanBroker}Supplier1\" quoteValue=\"10\">" + + message.getBody().add("<orderConfirmed xmlns=\"http://www.jboss.org/examples/supplier\" id=\"" + idValue +"\" supplierDesc=\"{http://www.jboss.org/savara/loanBroker}Supplier1\" quoteValue=\"10\">" + "</orderConfirmed>"); logger.info(message.getBody().get()); Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderRejectMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderRejectMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetOrderRejectMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -44,7 +44,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - message.getBody().add("<orderRejected id=\"" + idValue + "\">Credit Card is invalid!</orderRejected>"); + message.getBody().add("<orderRejected xmlns=\"http://www.jboss.org/examples/broker\" id=\"" + idValue + "\">Credit Card is invalid!</orderRejected>"); logger.info(message.getBody().get()); Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetQuotesListAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetQuotesListAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetQuotesListAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -50,7 +50,7 @@ String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); StringBuffer sbuffer = new StringBuffer(); - sbuffer.append("<quoteList id=\"" + idValue + "\">"); + sbuffer.append("<quoteList xmlns=\"http://www.jboss.org/examples/broker\" id=\"" + idValue + "\">"); for(Quote quote : quotes) { sbuffer.append("<quote supplierDesc=\"" + quote.getServiceDescription() + "\">"); Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetRequestQuoteMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetRequestQuoteMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/broker/src/main/java/org/jboss/savara/examples/broker/SetRequestQuoteMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -46,7 +46,7 @@ String serviceDescription = (String)message.getProperties().getProperty("serviceDescriptionName"); - message.getBody().add("<requestForQuote id=\"" + idValue +"\" supplierDesc=\"" + serviceDescription+ "\" ></requestForQuote>"); + message.getBody().add("<requestForQuote xmlns=\"http://www.jboss.org/examples/supplier\" id=\"" + idValue +"\" supplierDesc=\"" + serviceDescription+ "\" ></requestForQuote>"); logger.info("Set 'requestForQuote' : " + message.getBody().get()); Modified: runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetOrderConfirmResponseAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetOrderConfirmResponseAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetOrderConfirmResponseAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -31,7 +31,7 @@ String supplierDesc = "{http://www.jboss.org/savara/loanBroker}Supplier1"; String confirmation = "The quote of " + quoteValue + " has been confirmed."; - String body = "<bookingReference id=\"" + idValue + "\" supplierDesc = \"" + String body = "<bookingReference xmlns=\"http://www.jboss.org/examples/supplier\" id=\"" + idValue + "\" supplierDesc = \"" + supplierDesc+ "\">"+confirmation +"</bookingReference>"; message.getBody().add(body); Modified: runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetQuoteMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetQuoteMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/java/org/jboss/savara/examples/supplier/SetQuoteMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -27,7 +27,7 @@ String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); String supplierDesc = "{http://www.jboss.org/savara/loanBroker}Supplier1"; - String body = "<quote id=\"" + idValue + "\" supplierDesc = \"" + String body = "<quote xmlns=\"http://www.jboss.org/examples/supplier\" id=\"" + idValue + "\" supplierDesc = \"" + supplierDesc+ "\">10</quote>"; message.getBody().add(body); Modified: runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml 2009-11-30 17:00:08 UTC (rev 96) @@ -26,7 +26,7 @@ <property name="conversationType" value="savara.samples.LoanBroker@SupplierTxnProcessor"/> <property name="paths"> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_SupplierTxnProcessor__1"> - <message type="orderConfirmed"/> + <message type="{http://www.jboss.org/examples/supplier}orderConfirmed"/> </case> </property> </action> @@ -63,7 +63,7 @@ <property name="conversationType" value="savara.samples.LoanBroker@SupplierQuoteEngine"/> <property name="paths"> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_SupplierQuoteEngine__1"> - <message type="requestForQuote"/> + <message type="{http://www.jboss.org/examples/supplier}requestForQuote"/> </case> </property> </action> Modified: runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BrokerClient.java =================================================================== --- runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BrokerClient.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BrokerClient.java 2009-11-30 17:00:08 UTC (rev 96) @@ -50,7 +50,7 @@ String id = "20"; - String quoteReq="<enquiry id=\"" + id +"\" ></enquiry>"; + String quoteReq="<enquiry xmlns=\"http://www.jboss.org/examples/broker\" id=\"" + id +"\" ></enquiry>"; Message mesg = MessageFactory.getInstance().getMessage(MessageType.JBOSS_XML); mesg.getBody().add(quoteReq); @@ -65,7 +65,7 @@ Thread.sleep(5000);//Waiting... StringBuffer sbuffer = new StringBuffer(); - sbuffer.append("<buy id=\"" + id + "\" supplierDesc=\"{http://www.jboss.org/overlord/loanBroker}Supplier1\" quoteValue=\"10\">"); + sbuffer.append("<buy xmlns=\"http://www.jboss.org/examples/broker\" id=\"" + id + "\" supplierDesc=\"{http://www.jboss.org/overlord/loanBroker}Supplier1\" quoteValue=\"10\">"); sbuffer.append("<account>105</account>"); sbuffer.append("<amount>253</amount>"); sbuffer.append("</buy>"); Modified: runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BuyerClient.java =================================================================== --- runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BuyerClient.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/client/src/main/java/org/jboss/savara/examples/client/BuyerClient.java 2009-11-30 17:00:08 UTC (rev 96) @@ -50,7 +50,7 @@ public void run() { StringBuffer sbuffer = new StringBuffer(); - sbuffer.append("<BuyRequest id=\"5\">"); + sbuffer.append("<BuyRequest xmlns=\"http://www.jboss.org/examples/store\" id=\"5\">"); sbuffer.append("<account>105</account>"); sbuffer.append("<amount>253</amount>"); sbuffer.append("</BuyRequest>"); Modified: runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckInvalidMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckInvalidMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckInvalidMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -42,7 +42,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - sbuffer.append("<CreditCheckInvalid id=\"" + idValue +"\">"); + sbuffer.append("<CreditCheckInvalid xmlns=\"http://www.jboss.org/examples/creditAgency\" id=\"" + idValue +"\">"); NodeList list = node.getChildNodes(); for (int i =0; i < list.getLength(); i++) { Modified: runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckResponseMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckResponseMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/creditAgency/SetCreditCheckResponseMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -42,7 +42,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - sbuffer.append("<CreditCheckOk id=\"" + idValue +"\">"); + sbuffer.append("<CreditCheckOk xmlns=\"http://www.jboss.org/examples/creditAgency\" id=\"" + idValue +"\">"); NodeList list = node.getChildNodes(); for (int i =0; i < list.getLength(); i++) { Modified: runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/wsdl/CreditAgencyService.java =================================================================== --- runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/wsdl/CreditAgencyService.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/common/creditAgency/src/main/java/org/jboss/savara/examples/wsdl/CreditAgencyService.java 2009-11-30 17:00:08 UTC (rev 96) @@ -93,7 +93,7 @@ private Message getRequestMessage(PurchaseDetailsType creditCheckRequest) { Message message = MessageFactory.getInstance().getMessage(MessageType.JBOSS_XML); StringBuffer sbuffer = new StringBuffer(); - sbuffer.append("<CreditCheckRequest id=\"" + creditCheckRequest.getId() +"\">"); + sbuffer.append("<CreditCheckRequest xmlns=\"http://www.jboss.org/examples/creditAgency\" id=\"" + creditCheckRequest.getId() +"\">"); sbuffer.append("<account>" + creditCheckRequest.getAccount() + "</account>"); sbuffer.append("<amount>" + creditCheckRequest.getAmount() + "</amount>"); sbuffer.append("</CreditCheckRequest>"); Modified: runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyFailedMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyFailedMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyFailedMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -46,7 +46,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - sbuffer.append("<BuyFailed id=\"" + idValue +"\">"); + sbuffer.append("<BuyFailed xmlns=\"http://www.jboss.org/examples/store\" id=\"" + idValue +"\">"); NodeList list = node.getChildNodes(); for (int i =0; i < list.getLength(); i++) { Modified: runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyResponseMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyResponseMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetBuyResponseMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -42,7 +42,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - sbuffer.append("<BuyConfirmed id=\"" + idValue +"\">"); + sbuffer.append("<BuyConfirmed xmlns=\"http://www.jboss.org/examples/store\" id=\"" + idValue +"\">"); NodeList list = node.getChildNodes(); for (int i =0; i < list.getLength(); i++) { Modified: runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetCreditCheckRequestMessageAction.java =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetCreditCheckRequestMessageAction.java 2009-11-30 15:45:25 UTC (rev 95) +++ runtime/trunk/samples/jbossesb/purchasing/store/src/main/java/org/jboss/savara/examples/store/SetCreditCheckRequestMessageAction.java 2009-11-30 17:00:08 UTC (rev 96) @@ -42,7 +42,7 @@ Node node = XMLUtils.getNode((String)message.getBody().get()); String idValue = node.getAttributes().getNamedItem("id").getNodeValue(); - sbuffer.append("<CreditCheckRequest id=\"" + idValue +"\">"); + sbuffer.append("<CreditCheckRequest xmlns=\"http://www.jboss.org/examples/creditAgency\" id=\"" + idValue +"\">"); NodeList list = node.getChildNodes(); for (int i =0; i < list.getLength(); i++) {

14 years, 4 months

1
0
0 / 0

savara SVN: r95 - in runtime/trunk/samples/jbossesb: brokerage/models and 4 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-30 10:45:25 -0500 (Mon, 30 Nov 2009) New Revision: 95 Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/resources/META-INF/jboss-esb.xml runtime/trunk/samples/jbossesb/brokerage/models/ESBBroker.cdm runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml runtime/trunk/samples/jbossesb/common/creditAgency/src/main/resources/META-INF/jboss-esb.xml runtime/trunk/samples/jbossesb/purchasing/models/BuyConfirmed.xml runtime/trunk/samples/jbossesb/purchasing/models/BuyRequest.xml runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckInvalid.xml runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckOk.xml runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckRequest.xml runtime/trunk/samples/jbossesb/purchasing/models/InvalidPurchase.scn runtime/trunk/samples/jbossesb/purchasing/models/PurchaseGoods.cdm runtime/trunk/samples/jbossesb/purchasing/models/SuccessfulPurchase.scn runtime/trunk/samples/jbossesb/purchasing/store/src/main/resources/META-INF/jboss-esb.xml Log: SAVARA-7 - added namespace to messages and models. Need to update runtime tests. Also appears that generation of ESBBroker.cdm Broker participant is not complete - need to raise bug. Modified: runtime/trunk/samples/jbossesb/brokerage/broker/src/main/resources/META-INF/jboss-esb.xml =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/src/main/resources/META-INF/jboss-esb.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/brokerage/broker/src/main/resources/META-INF/jboss-esb.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -56,16 +56,16 @@ <property name="conversationType" value="savara.samples.LoanBroker@Broker"/> <property name="paths"> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_Broker__1"> - <message type="enquiry"/> + <message type="{http://www.jboss.org/examples/broker}enquiry"/> </case> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_Broker__7"> <event description="Event trigger to send quoteList message type(s)"/> </case> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_Broker__8"> - <message type="buy"/> + <message type="{http://www.jboss.org/examples/broker}buy"/> </case> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_Broker__12"> - <message type="cancel"/> + <message type="{http://www.jboss.org/examples/broker}cancel"/> </case> </property> </action> @@ -78,7 +78,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__1_action_1" process="process"> <property name="operation" value="makeEnquiry"/> - <property name="messageType" value="enquiry"/> + <property name="messageType" value="{http://www.jboss.org/examples/broker}enquiry"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.broker.MemoryEPRStorage" /> </action> @@ -101,7 +101,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__2_action_1" process="process"> <property name="operation" value="getQuote"/> - <property name="messageType" value="requestForQuote"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}requestForQuote"/> <property name="serviceCategory" value="org.jboss.savara.examples.esbbroker"/> <property name="serviceName" value="ESBBrokerProcess_SupplierQuoteEngine"/> <property name="responseServiceCategory" value="org.jboss.savara.examples.esbbroker"/> @@ -125,7 +125,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__4_action_1" process="process"> <property name="operation" value="getQuote"/> - <property name="messageType" value="quote"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}quote"/> </action> <action class="org.jboss.savara.examples.broker.SetQuoteAction" name="b-2" process="process"> </action> @@ -145,7 +145,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__5_action_1" process="process"> <property name="operation" value="getQuote"/> - <property name="messageType" value="requestForQuote"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}requestForQuote"/> <property name="serviceCategory" value="org.jboss.savara.examples.esbbroker"/> <property name="serviceName" value="ESBBrokerProcess_SupplierQuoteEngine"/> <property name="responseServiceCategory" value="org.jboss.savara.examples.esbbroker"/> @@ -171,7 +171,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__7_action_1" process="process"> <property name="operation" value="makeEnquiry"/> - <property name="messageType" value="quoteList"/> + <property name="messageType" value="{http://www.jboss.org/examples/broker}quoteList"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.broker.MemoryEPRStorage" /> </action> @@ -184,7 +184,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__8_action_1" process="process"> <property name="operation" value="buy"/> - <property name="messageType" value="buy"/> + <property name="messageType" value="{http://www.jboss.org/examples/broker}buy"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.broker.MemoryEPRStorage" /> </action> @@ -192,7 +192,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__8_action_2" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckRequest"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest"/> <property name="serviceCategory" value="org.jboss.savara.examples.purchasegoods"/> <property name="serviceName" value="PurchaseGoodsProcess_CreditAgency"/> <property name="responseServiceCategory" value="org.jboss.savara.examples.esbbroker"/> @@ -207,13 +207,13 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__9_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckOk"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckOk"/> </action> <action name="set-orderConfirm" class="org.jboss.savara.examples.broker.SetOrderConfirmRequestAction"> </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__9_action_2" process="process"> <property name="operation" value="confirm"/> - <property name="messageType" value="orderConfirmed"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}orderConfirmed"/> <property name="serviceCategory" value="org.jboss.savara.examples.esbbroker"/> <property name="serviceName" value="ESBBrokerProcess_SupplierTxnProcessor"/> <property name="responseServiceCategory" value="org.jboss.savara.examples.esbbroker"/> @@ -228,11 +228,11 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__10_action_1" process="process"> <property name="operation" value="confirm"/> - <property name="messageType" value="bookingReference"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}bookingReference"/> </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__10_action_2" process="process"> <property name="operation" value="buy"/> - <property name="messageType" value="bookingReference"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}bookingReference"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.broker.MemoryEPRStorage" /> </action> @@ -245,14 +245,14 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__11_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckInvalid"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid"/> </action> <action name="set-orderRejected" class="org.jboss.savara.examples.broker.SetOrderRejectMessageAction"></action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_Broker__11_action_2" process="process"> <property name="operation" value="buy"/> - <property name="messageType" value="orderRejected"/> + <property name="messageType" value="{http://www.jboss.org/examples/broker}orderRejected"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.broker.MemoryEPRStorage" /> </action> @@ -265,7 +265,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_Broker__12_action_1" process="process"> <property name="operation" value="cancel"/> - <property name="messageType" value="cancel"/> + <property name="messageType" value="{http://www.jboss.org/examples/broker}cancel"/> </action> </actions> </service> @@ -277,10 +277,10 @@ <action class="org.jboss.savara.jbossesb.actions.SwitchAction" name="checkCredit_action_1" process="process"> <property name="paths"> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_Broker__9"> - <message type="CreditCheckOk"/> + <message type="{http://www.jboss.org/examples/creditAgency}CreditCheckOk"/> </case> <case service-category="org.jboss.savara.examples.esbbroker" service-name="ESBBrokerProcess_Broker__11"> - <message type="CreditCheckInvalid"/> + <message type="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid"/> </case> </property> </action> Modified: runtime/trunk/samples/jbossesb/brokerage/models/ESBBroker.cdm =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/models/ESBBroker.cdm 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/brokerage/models/ESBBroker.cdm 2009-11-30 15:45:25 UTC (rev 95) @@ -1,124 +1,127 @@ -<?xml version="1.0" encoding="Cp1252"?> -<org.pi4soa.cdl:Package xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.pi4soa.cdl="http:///org/pi4soa/cdl.ecore" description="The choreography description for ESBBroker" name="ESBBroker" author="gary" version="0.3" targetNamespace="http://www.jboss.org/savara/examples"> - <typeDefinitions> - <nameSpaces description="Target Namespace for ESBBroker" prefix="tns" uRI="http://www.jboss.org/savara/examples"/> - <nameSpaces description="XML Schema Namespace" prefix="xsd" uRI="http://www.w3.org/2001/XMLSchema"/> - <informationTypes description="This is the information type BookingReference" name="BookingReference" elementName="bookingReference"/> - <informationTypes description="This is the information type Buy" name="Buy" elementName="buy"/> - <informationTypes description="This is the information type Cancel" name="Cancel" elementName="cancel"/> - <informationTypes description="This is the information type CreditInformation" name="CreditInformation" elementName="CreditCheckRequest"/> - <informationTypes description="This is the information type CreditInvalid" name="CreditInvalid" elementName="CreditCheckInvalid"/> - <informationTypes description="This is the information type CreditValid" name="CreditValid" elementName="CreditCheckOk"/> - <informationTypes description="This is the information type Enquiry" name="Enquiry" typeName="" elementName="enquiry"/> - <informationTypes description="This is the information type OrderConfirmed" name="OrderConfirmed" elementName="orderConfirmed"/> - <informationTypes description="This is the information type OrderRejected" name="OrderRejected" elementName="orderRejected"/> - <informationTypes description="This is the information type Quote" name="Quote" elementName="quote"/> - <informationTypes description="This is the information type QuoteList" name="QuoteList" elementName="quoteList"/> - <informationTypes description="This is the information type RequestForQuote" name="RequestForQuote" elementName="requestForQuote"/> - <informationTypes description="This is the information type URIType" name="URIType"/> - <tokens description="This is the token URI" name="URI" informationType="//@typeDefinitions/(a)informationTypes.12"/> - <roleTypes description="This is the role type Broker" name="Broker"> - <behaviors description="This is the behavior BrokerBehavior" name="BrokerBehavior"/> - </roleTypes> - <roleTypes description="This is the role type Buyer" name="Buyer"> - <behaviors description="This is the behavior BuyerBehavior" name="BuyerBehavior"/> - </roleTypes> - <roleTypes description="This is the role type CreditAgency" name="CreditAgency"> - <behaviors description="This is the behavior CreditAgencyBehavior" name="CreditAgencyBehavior"/> - </roleTypes> - <roleTypes description="This is the role type Supplier" name="Supplier"> - <behaviors description="This is the behavior SupplierBehavior" name="SupplierBehavior"/> - </roleTypes> - <relationshipTypes description="Relationship between Broker and CreditAgency" name="BrokerToCreditAgencyRel" firstRoleType="//@typeDefinitions/(a)roleTypes.0" secondRoleType="//@typeDefinitions/(a)roleTypes.2"/> - <relationshipTypes description="Relationship between Broker and Supplier" name="BrokerToSupplierRel" firstRoleType="//@typeDefinitions/(a)roleTypes.0" secondRoleType="//@typeDefinitions/(a)roleTypes.3"/> - <relationshipTypes description="Relationship between Buyer and Broker" name="BuyerToBrokerRel" firstRoleType="//@typeDefinitions/(a)roleTypes.1" secondRoleType="//@typeDefinitions/(a)roleTypes.0"/> - <participantTypes description="This is the participant type Broker" name="Broker" roleTypes="//@typeDefinitions/(a)roleTypes.0"> - <semanticAnnotations annotation="savara.samples.LoanBroker@Broker" name="conversationType"/> - </participantTypes> - <participantTypes description="This is the participant type Buyer" name="Buyer" roleTypes="//@typeDefinitions/(a)roleTypes.1"> - <semanticAnnotations annotation="savara.samples.LoanBroker@Buyer" name="conversationType"/> - </participantTypes> - <participantTypes description="This is the participant type CreditAgency" name="CreditAgency" roleTypes="//@typeDefinitions/(a)roleTypes.2"> - <semanticAnnotations annotation="savara.samples.Common@CreditAgency" name="conversationType"/> - </participantTypes> - <participantTypes description="This is the participant type Supplier" name="Supplier" roleTypes="//@typeDefinitions/(a)roleTypes.3"> - <semanticAnnotations annotation="" name="conversationType"/> - </participantTypes> - <channelTypes description="This is the channel type BrokerChannelType" name="BrokerChannelType" referenceToken="//@typeDefinitions/(a)tokens.0" roleType="//@typeDefinitions/(a)roleTypes.0"/> - <channelTypes description="This is the channel type CreditAgencyChannelType" name="CreditAgencyChannelType" referenceToken="//@typeDefinitions/(a)tokens.0" roleType="//@typeDefinitions/(a)roleTypes.2"/> - <channelTypes description="This is the channel type SupplierChannelType" name="SupplierChannelType" referenceToken="//@typeDefinitions/(a)tokens.0" roleType="//@typeDefinitions/(a)roleTypes.3"/> - </typeDefinitions> - <choreographies description="Choreography flow for the ESBBroker process" name="ESBBrokerProcess" root="true"> - <enclosedChoreographies name="CompleteTransaction"> - <participantDefinitions name="SupplierTxnProcessor" roleTypes="//@typeDefinitions/(a)roleTypes.3"> - <semanticAnnotations annotation="savara.samples.LoanBroker@SupplierTxnProcessor" name="conversationType"/> - </participantDefinitions> - <variableDefinitions description="Channel to facilitate interaction to Broker" name="BrokerChannel" type="//@typeDefinitions/(a)channelTypes.0" free="true" roleTypes="//@typeDefinitions/(a)roleTypes.0 //@typeDefinitions/(a)roleTypes.1"/> - <variableDefinitions description="Channel to facilitate interaction to CreditAgency" name="CreditAgencyChannel" type="//@typeDefinitions/(a)channelTypes.1"/> - <variableDefinitions description="Channel to facilitate interaction to Supplier" name="SupplierChannel" type="//@typeDefinitions/(a)channelTypes.2"/> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="Buy" operation="buy" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction Buy" name="BuyRequestExchange" type="//@typeDefinitions/(a)informationTypes.1"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="CheckCredit" operation="checkCredit" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0"> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction CheckCredit" name="CheckCreditRequestExchange" type="//@typeDefinitions/(a)informationTypes.3"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:Choice" description="Evaluate Credit Check Result"> - <activities xsi:type="org.pi4soa.cdl:Sequence" description="Sufficient Credit"> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="CheckCreditResponse" operation="checkCredit" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0"> - <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction CheckCreditResponse" name="CheckCreditResponseRespondExchange" type="//@typeDefinitions/(a)informationTypes.5" action="Respond"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="ConfirmBooking" operation="confirm" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.2" relationship="//@typeDefinitions/(a)relationshipTypes.1" toParticipant="//@choreographies.0/@enclosedChoreographies.0/(a)participantDefinitions.0"> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction ConfirmBooking" name="ConfirmBookingRequestExchange" type="//@typeDefinitions/(a)informationTypes.7"/> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction ConfirmBooking" name="ConfirmBookingRequestExchange" type="//@typeDefinitions/(a)informationTypes.0" action="Respond"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="Buy" operation="buy" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> - <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction Buy" name="BuyRespondExchange" type="//@typeDefinitions/(a)informationTypes.0" action="Respond" faultName=""/> - </activities> - </activities> - <activities xsi:type="org.pi4soa.cdl:Sequence" description="Insufficient Credit"> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="CheckCreditFailed" operation="checkCredit" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0"> - <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction CheckCreditFailed" name="CheckCreditFailedRespondExchange" type="//@typeDefinitions/(a)informationTypes.4" action="Respond" faultName="invalidCredit"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="Buy" operation="buy" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> - <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction Buy" name="BuyRespondExchange" type="//@typeDefinitions/(a)informationTypes.8" action="Respond" faultName="rejected"/> - </activities> - </activities> - </activities> - </enclosedChoreographies> - <enclosedChoreographies name="RequestForQuote"> - <participantDefinitions name="SupplierQuoteEngine" roleTypes="//@typeDefinitions/(a)roleTypes.3"> - <semanticAnnotations annotation="savara.samples.LoanBroker@SupplierQuoteEngine" name="conversationType"/> - </participantDefinitions> - <variableDefinitions description="Channel to facilitate interaction to Supplier" name="SupplierChannel" type="//@typeDefinitions/(a)channelTypes.2"/> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="RFQ" operation="getQuote" channelVariable="//@choreographies.0/@enclosedChoreographies.1/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.1" toParticipant="//@choreographies.0/@enclosedChoreographies.1/(a)participantDefinitions.0"> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction RFQ" name="RFQRequestExchange" type="//@typeDefinitions/(a)informationTypes.11"/> - <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction RFQ" name="RFQRespondExchange" type="//@typeDefinitions/(a)informationTypes.9" action="Respond"/> - </activities> - </enclosedChoreographies> - <variableDefinitions description="Channel to facilitate interaction to Broker" name="BrokerChannel" type="//@typeDefinitions/(a)channelTypes.0" roleTypes="//@typeDefinitions/(a)roleTypes.0 //@typeDefinitions/(a)roleTypes.1"/> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="Enquiry" operation="makeEnquiry" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction Enquiry" name="EnquiryRequestExchange" type="//@typeDefinitions/(a)informationTypes.6"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:While" name="SendRFQToSuppliers"> - <activities xsi:type="org.pi4soa.cdl:Perform" choreography="//@choreographies.0/(a)enclosedChoreographies.1"/> - </activities> - <activities xsi:type="org.pi4soa.cdl:When" name="WhenQuotesReceivedOrTimeout"> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="Enquiry" operation="makeEnquiry" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> - <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction Enquiry" name="EnquiryRespondExchange" type="//@typeDefinitions/(a)informationTypes.10" action="Respond"/> - </activities> - </activities> - <activities xsi:type="org.pi4soa.cdl:Choice"> - <activities xsi:type="org.pi4soa.cdl:Sequence"> - <activities xsi:type="org.pi4soa.cdl:Perform" choreography="//@choreographies.0/(a)enclosedChoreographies.0"> - <bindDetails name="BindBrokerChannel" thisVariable="//@choreographies.0/(a)variableDefinitions.0" thisRole="//@typeDefinitions/(a)roleTypes.1" freeVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" freeRole="//@typeDefinitions/(a)roleTypes.1"/> - <bindDetails name="BindBrokerChannel" thisVariable="//@choreographies.0/(a)variableDefinitions.0" thisRole="//@typeDefinitions/(a)roleTypes.0" freeVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" freeRole="//@typeDefinitions/(a)roleTypes.0"/> - </activities> - </activities> - <activities xsi:type="org.pi4soa.cdl:Sequence"> - <activities xsi:type="org.pi4soa.cdl:Interaction" name="Cancel" operation="cancel" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> - <exchangeDetails description="This is the exchange details for the request exchange associated with interaction Cancel" name="CancelRequestExchange" type="//@typeDefinitions/(a)informationTypes.2"/> - </activities> - </activities> - </activities> - </choreographies> -</org.pi4soa.cdl:Package> +<?xml version="1.0" encoding="UTF-8"?> +<org.pi4soa.cdl:Package xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.pi4soa.cdl="http:///org/pi4soa/cdl.ecore" description="The choreography description for ESBBroker" name="ESBBroker" author="gary" version="0.3" targetNamespace="http://www.jboss.org/savara/examples"> + <typeDefinitions> + <nameSpaces description="Target Namespace for ESBBroker" prefix="tns" uRI="http://www.jboss.org/savara/examples"/> + <nameSpaces description="XML Schema Namespace" prefix="xsd" uRI="http://www.w3.org/2001/XMLSchema"/> + <nameSpaces prefix="bro" uRI="http://www.jboss.org/examples/broker"/> + <nameSpaces prefix="sup" uRI="http://www.jboss.org/examples/supplier"/> + <nameSpaces prefix="ca" uRI="http://www.jboss.org/examples/creditAgency"/> + <informationTypes description="This is the information type BookingReference" name="BookingReference" typeName="sup:bookingReference" elementName=""/> + <informationTypes description="This is the information type Buy" name="Buy" typeName="bro:buy" elementName=""/> + <informationTypes description="This is the information type Cancel" name="Cancel" typeName="bro:cancel" elementName=""/> + <informationTypes description="This is the information type CreditInformation" name="CreditInformation" typeName="ca:CreditCheckRequest" elementName=""/> + <informationTypes description="This is the information type CreditInvalid" name="CreditInvalid" typeName="ca:CreditCheckInvalid" elementName=""/> + <informationTypes description="This is the information type CreditValid" name="CreditValid" typeName="ca:CreditCheckOk" elementName=""/> + <informationTypes description="This is the information type Enquiry" name="Enquiry" typeName="bro:enquiry" elementName=""/> + <informationTypes description="This is the information type OrderConfirmed" name="OrderConfirmed" typeName="sup:orderConfirmed" elementName=""/> + <informationTypes description="This is the information type OrderRejected" name="OrderRejected" typeName="bro:orderRejected" elementName=""/> + <informationTypes description="This is the information type Quote" name="Quote" typeName="sup:quote" elementName=""/> + <informationTypes description="This is the information type QuoteList" name="QuoteList" typeName="bro:quoteList" elementName=""/> + <informationTypes description="This is the information type RequestForQuote" name="RequestForQuote" typeName="sup:requestForQuote" elementName=""/> + <informationTypes description="This is the information type URIType" name="URIType" typeName="xsd:anyURI"/> + <tokens description="This is the token URI" name="URI" informationType="//@typeDefinitions/(a)informationTypes.12"/> + <roleTypes description="This is the role type Broker" name="Broker"> + <behaviors description="This is the behavior BrokerBehavior" name="BrokerBehavior" interface="bro:BrokerInterface"/> + </roleTypes> + <roleTypes description="This is the role type Buyer" name="Buyer"> + <behaviors description="This is the behavior BuyerBehavior" name="BuyerBehavior"/> + </roleTypes> + <roleTypes description="This is the role type CreditAgency" name="CreditAgency"> + <behaviors description="This is the behavior CreditAgencyBehavior" name="CreditAgencyBehavior" interface="ca:CreditAgencyInterface"/> + </roleTypes> + <roleTypes description="This is the role type Supplier" name="Supplier"> + <behaviors description="This is the behavior SupplierBehavior" name="SupplierBehavior" interface="sup:SupplierInterface"/> + </roleTypes> + <relationshipTypes description="Relationship between Broker and CreditAgency" name="BrokerToCreditAgencyRel" firstRoleType="//@typeDefinitions/(a)roleTypes.0" secondRoleType="//@typeDefinitions/(a)roleTypes.2"/> + <relationshipTypes description="Relationship between Broker and Supplier" name="BrokerToSupplierRel" firstRoleType="//@typeDefinitions/(a)roleTypes.0" secondRoleType="//@typeDefinitions/(a)roleTypes.3"/> + <relationshipTypes description="Relationship between Buyer and Broker" name="BuyerToBrokerRel" firstRoleType="//@typeDefinitions/(a)roleTypes.1" secondRoleType="//@typeDefinitions/(a)roleTypes.0"/> + <participantTypes description="This is the participant type Buyer" name="Buyer" roleTypes="//@typeDefinitions/(a)roleTypes.1"> + <semanticAnnotations annotation="savara.samples.LoanBroker@Buyer" name="conversationType"/> + </participantTypes> + <participantTypes description="This is the participant type bro:Broker" name="bro:Broker" roleTypes="//@typeDefinitions/(a)roleTypes.0"> + <semanticAnnotations annotation="savara.samples.LoanBroker@Broker" name="conversationType"/> + </participantTypes> + <participantTypes description="This is the participant type ca:CreditAgency" name="ca:CreditAgency" roleTypes="//@typeDefinitions/(a)roleTypes.2"> + <semanticAnnotations annotation="savara.samples.Common@CreditAgency" name="conversationType"/> + </participantTypes> + <participantTypes description="This is the participant type sup:Supplier" name="sup:Supplier" roleTypes="//@typeDefinitions/(a)roleTypes.3"> + <semanticAnnotations annotation="" name="conversationType"/> + </participantTypes> + <channelTypes description="This is the channel type BrokerChannelType" name="BrokerChannelType" referenceToken="//@typeDefinitions/(a)tokens.0" roleType="//@typeDefinitions/(a)roleTypes.0"/> + <channelTypes description="This is the channel type CreditAgencyChannelType" name="CreditAgencyChannelType" referenceToken="//@typeDefinitions/(a)tokens.0" roleType="//@typeDefinitions/(a)roleTypes.2"/> + <channelTypes description="This is the channel type SupplierChannelType" name="SupplierChannelType" referenceToken="//@typeDefinitions/(a)tokens.0" roleType="//@typeDefinitions/(a)roleTypes.3"/> + </typeDefinitions> + <choreographies description="Choreography flow for the ESBBroker process" name="ESBBrokerProcess" root="true"> + <enclosedChoreographies name="CompleteTransaction"> + <participantDefinitions name="SupplierTxnProcessor" roleTypes="//@typeDefinitions/(a)roleTypes.3"> + <semanticAnnotations annotation="savara.samples.LoanBroker@SupplierTxnProcessor" name="conversationType"/> + </participantDefinitions> + <variableDefinitions description="Channel to facilitate interaction to Broker" name="BrokerChannel" type="//@typeDefinitions/(a)channelTypes.0" free="true" roleTypes="//@typeDefinitions/(a)roleTypes.0 //@typeDefinitions/(a)roleTypes.1"/> + <variableDefinitions description="Channel to facilitate interaction to CreditAgency" name="CreditAgencyChannel" type="//@typeDefinitions/(a)channelTypes.1"/> + <variableDefinitions description="Channel to facilitate interaction to Supplier" name="SupplierChannel" type="//@typeDefinitions/(a)channelTypes.2"/> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="Buy" operation="buy" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction Buy" name="BuyRequestExchange" type="//@typeDefinitions/(a)informationTypes.1"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="CheckCredit" operation="checkCredit" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0"> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction CheckCredit" name="CheckCreditRequestExchange" type="//@typeDefinitions/(a)informationTypes.3"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:Choice" description="Evaluate Credit Check Result"> + <activities xsi:type="org.pi4soa.cdl:Sequence" description="Sufficient Credit"> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="CheckCreditResponse" operation="checkCredit" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0"> + <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction CheckCreditResponse" name="CheckCreditResponseRespondExchange" type="//@typeDefinitions/(a)informationTypes.5" action="Respond"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="ConfirmBooking" operation="confirm" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.2" relationship="//@typeDefinitions/(a)relationshipTypes.1" toParticipant="//@choreographies.0/@enclosedChoreographies.0/(a)participantDefinitions.0"> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction ConfirmBooking" name="ConfirmBookingRequestExchange" type="//@typeDefinitions/(a)informationTypes.7"/> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction ConfirmBooking" name="ConfirmBookingRequestExchange" type="//@typeDefinitions/(a)informationTypes.0" action="Respond"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="Buy" operation="buy" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> + <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction Buy" name="BuyRespondExchange" type="//@typeDefinitions/(a)informationTypes.0" action="Respond" faultName=""/> + </activities> + </activities> + <activities xsi:type="org.pi4soa.cdl:Sequence" description="Insufficient Credit"> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="CheckCreditFailed" operation="checkCredit" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.1" relationship="//@typeDefinitions/(a)relationshipTypes.0"> + <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction CheckCreditFailed" name="CheckCreditFailedRespondExchange" type="//@typeDefinitions/(a)informationTypes.4" action="Respond" faultName="invalidCredit"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="Buy" operation="buy" channelVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> + <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction Buy" name="BuyRespondExchange" type="//@typeDefinitions/(a)informationTypes.8" action="Respond" faultName="rejected"/> + </activities> + </activities> + </activities> + </enclosedChoreographies> + <enclosedChoreographies name="RequestForQuote"> + <participantDefinitions name="SupplierQuoteEngine" roleTypes="//@typeDefinitions/(a)roleTypes.3"> + <semanticAnnotations annotation="savara.samples.LoanBroker@SupplierQuoteEngine" name="conversationType"/> + </participantDefinitions> + <variableDefinitions description="Channel to facilitate interaction to Supplier" name="SupplierChannel" type="//@typeDefinitions/(a)channelTypes.2"/> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="RFQ" operation="getQuote" channelVariable="//@choreographies.0/@enclosedChoreographies.1/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.1" toParticipant="//@choreographies.0/@enclosedChoreographies.1/(a)participantDefinitions.0"> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction RFQ" name="RFQRequestExchange" type="//@typeDefinitions/(a)informationTypes.11"/> + <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction RFQ" name="RFQRespondExchange" type="//@typeDefinitions/(a)informationTypes.9" action="Respond"/> + </activities> + </enclosedChoreographies> + <variableDefinitions description="Channel to facilitate interaction to Broker" name="BrokerChannel" type="//@typeDefinitions/(a)channelTypes.0" roleTypes="//@typeDefinitions/(a)roleTypes.0 //@typeDefinitions/(a)roleTypes.1"/> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="Enquiry" operation="makeEnquiry" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction Enquiry" name="EnquiryRequestExchange" type="//@typeDefinitions/(a)informationTypes.6"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:While" name="SendRFQToSuppliers"> + <activities xsi:type="org.pi4soa.cdl:Perform" choreography="//@choreographies.0/(a)enclosedChoreographies.1"/> + </activities> + <activities xsi:type="org.pi4soa.cdl:When" name="WhenQuotesReceivedOrTimeout"> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="Enquiry" operation="makeEnquiry" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> + <exchangeDetails description="This is the exchange details for the respond exchange associated with interaction Enquiry" name="EnquiryRespondExchange" type="//@typeDefinitions/(a)informationTypes.10" action="Respond"/> + </activities> + </activities> + <activities xsi:type="org.pi4soa.cdl:Choice"> + <activities xsi:type="org.pi4soa.cdl:Sequence"> + <activities xsi:type="org.pi4soa.cdl:Perform" choreography="//@choreographies.0/(a)enclosedChoreographies.0"> + <bindDetails name="BindBrokerChannel" thisVariable="//@choreographies.0/(a)variableDefinitions.0" thisRole="//@typeDefinitions/(a)roleTypes.1" freeVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" freeRole="//@typeDefinitions/(a)roleTypes.1"/> + <bindDetails name="BindBrokerChannel" thisVariable="//@choreographies.0/(a)variableDefinitions.0" thisRole="//@typeDefinitions/(a)roleTypes.0" freeVariable="//@choreographies.0/@enclosedChoreographies.0/(a)variableDefinitions.0" freeRole="//@typeDefinitions/(a)roleTypes.0"/> + </activities> + </activities> + <activities xsi:type="org.pi4soa.cdl:Sequence"> + <activities xsi:type="org.pi4soa.cdl:Interaction" name="Cancel" operation="cancel" channelVariable="//@choreographies.0/(a)variableDefinitions.0" relationship="//@typeDefinitions/(a)relationshipTypes.2"> + <exchangeDetails description="This is the exchange details for the request exchange associated with interaction Cancel" name="CancelRequestExchange" type="//@typeDefinitions/(a)informationTypes.2"/> + </activities> + </activities> + </activities> + </choreographies> +</org.pi4soa.cdl:Package> Modified: runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/brokerage/supplier/src/main/resources/META-INF/jboss-esb.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -39,7 +39,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_SupplierTxnProcessor__1_action_1" process="process"> <property name="operation" value="confirm"/> - <property name="messageType" value="orderConfirmed"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}orderConfirmed"/> <property name="clientRole" value="Broker" /> <property name="eprStore" value="org.jboss.savara.examples.supplier.MemoryEPRStorage" /> </action> @@ -47,7 +47,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_SupplierTxnProcessor__1_action_2" process="process"> <property name="operation" value="confirm"/> - <property name="messageType" value="bookingReference"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}bookingReference"/> <property name="clientRole" value="Broker"/> <property name="eprStore" value="org.jboss.savara.examples.supplier.MemoryEPRStorage" /> </action> @@ -76,7 +76,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="ESBBrokerProcess_SupplierQuoteEngine__1_action_1" process="process"> <property name="operation" value="getQuote"/> - <property name="messageType" value="requestForQuote"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}requestForQuote"/> <property name="clientRole" value="Broker" /> <property name="eprStore" value="org.jboss.savara.examples.supplier.MemoryEPRStorage" /> </action> @@ -84,7 +84,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="ESBBrokerProcess_SupplierQuoteEngine__1_action_2" process="process"> <property name="operation" value="getQuote"/> - <property name="messageType" value="quote"/> + <property name="messageType" value="{http://www.jboss.org/examples/supplier}quote"/> <property name="clientRole" value="Broker"/> <property name="eprStore" value="org.jboss.savara.examples.supplier.MemoryEPRStorage" /> </action> Modified: runtime/trunk/samples/jbossesb/common/creditAgency/src/main/resources/META-INF/jboss-esb.xml =================================================================== --- runtime/trunk/samples/jbossesb/common/creditAgency/src/main/resources/META-INF/jboss-esb.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/common/creditAgency/src/main/resources/META-INF/jboss-esb.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -45,7 +45,7 @@ <property name="conversationType" value="savara.samples.Common@CreditAgency"/> <property name="paths"> <case service-category="org.jboss.savara.examples.purchasegoods" service-name="PurchaseGoodsProcess_CreditAgency__1"> - <message type="CreditCheckRequest"/> + <message type="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest"/> </case> </property> </action> @@ -58,7 +58,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="PurchaseGoodsProcess_CreditAgency__1_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckRequest"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest"/> <property name="clientRole" value="Store" /> <property name="eprStore" value="org.jboss.savara.examples.creditAgency.MemoryEPRStorage" /> </action> @@ -79,7 +79,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="PurchaseGoodsProcess_CreditAgency__2_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckOk"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckOk"/> <property name="clientRole" value="Store"/> <property name="eprStore" value="org.jboss.savara.examples.creditAgency.MemoryEPRStorage" /> </action> @@ -94,7 +94,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="PurchaseGoodsProcess_CreditAgency__3_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckInvalid"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid"/> <property name="clientRole" value="Store"/> <property name="eprStore" value="org.jboss.savara.examples.creditAgency.MemoryEPRStorage" /> </action> Modified: runtime/trunk/samples/jbossesb/purchasing/models/BuyConfirmed.xml =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/BuyConfirmed.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/BuyConfirmed.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -1 +1 @@ -<BuyConfirmed id="1" /> \ No newline at end of file +<BuyConfirmed xmlns="http://www.jboss.org/examples/store" id="1" /> \ No newline at end of file Modified: runtime/trunk/samples/jbossesb/purchasing/models/BuyRequest.xml =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/BuyRequest.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/BuyRequest.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -1 +1 @@ -<BuyRequest id="1" /> \ No newline at end of file +<BuyRequest xmlns="http://www.jboss.org/examples/store" id="1" /> \ No newline at end of file Modified: runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckInvalid.xml =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckInvalid.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckInvalid.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -1 +1 @@ -<CreditCheckInvalid id="1" /> \ No newline at end of file +<CreditCheckInvalid xmlns="http://www.jboss.org/examples/creditAgency" id="1" /> \ No newline at end of file Modified: runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckOk.xml =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckOk.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckOk.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -1 +1 @@ -<CreditCheckOk id="1" /> \ No newline at end of file +<CreditCheckOk xmlns="http://www.jboss.org/examples/creditAgency" id="1" /> \ No newline at end of file Modified: runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckRequest.xml =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckRequest.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/CreditCheckRequest.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -1 +1 @@ -<CreditCheckRequest id="1" /> \ No newline at end of file +<CreditCheckRequest xmlns="http://www.jboss.org/examples/creditAgency" id="1" /> \ No newline at end of file Modified: runtime/trunk/samples/jbossesb/purchasing/models/InvalidPurchase.scn =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/InvalidPurchase.scn 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/InvalidPurchase.scn 2009-11-30 15:45:25 UTC (rev 95) @@ -1,18 +1,18 @@ -<?xml version="1.0" encoding="Cp1252"?> -<scn:Scenario xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:scn="http://www.pi4soa.org/scenario" name="InvalidPurchase" description="Invalid purchase goods" author="" choreographyDescriptionURL="PurchaseGoods.cdm"> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" messageType="BuyRequest" valueURL="BuyRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" direction="receive" messageType="BuyRequest" valueURL="BuyRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" messageType="CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" direction="receive" messageType="CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" faultName="{http://www.pi4soa.org/purchase}CreditCheckFailed" isRequest="false" messageType="CreditCheckInvalid" valueURL="CreditCheckInvalid.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" faultName="{http://www.pi4soa.org/purchase}CreditCheckFailed" isRequest="false" direction="receive" messageType="CreditCheckInvalid" valueURL="CreditCheckInvalid.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" isRequest="false" messageType="BuyConfirmed" valueURL="BuyConfirmed.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" isRequest="false" direction="receive" messageType="BuyConfirmed" valueURL="BuyConfirmed.xml"/> - <messageLinks source="//(a)scenarioObjects.0" target="//(a)scenarioObjects.1"/> - <messageLinks source="//(a)scenarioObjects.2" target="//(a)scenarioObjects.3"/> - <messageLinks source="//(a)scenarioObjects.4" target="//(a)scenarioObjects.5"/> - <messageLinks source="//(a)scenarioObjects.6" target="//(a)scenarioObjects.7"/> - <participants type="Buyer"/> - <participants type="Store"/> - <participants type="CreditAgency"/> -</scn:Scenario> +<?xml version="1.0" encoding="UTF-8"?> +<scn:Scenario xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:scn="http://www.pi4soa.org/scenario" name="InvalidPurchase" description="Invalid purchase goods" author="" choreographyDescriptionURL="PurchaseGoods.cdm"> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" messageType="{http://www.jboss.org/examples/store}BuyRequest" valueURL="BuyRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" direction="receive" messageType="{http://www.jboss.org/examples/store}BuyRequest" valueURL="BuyRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" direction="receive" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" faultName="{http://www.jboss.org/savara/examples}CreditCheckFailed" isRequest="false" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid" valueURL="CreditCheckInvalid.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" faultName="{http://www.jboss.org/savara/examples}CreditCheckFailed" isRequest="false" direction="receive" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid" valueURL="CreditCheckInvalid.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" isRequest="false" messageType="{http://www.jboss.org/examples/store}BuyConfirmed" valueURL="BuyConfirmed.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" isRequest="false" direction="receive" messageType="{http://www.jboss.org/examples/store}BuyConfirmed" valueURL="BuyConfirmed.xml"/> + <messageLinks source="//(a)scenarioObjects.0" target="//(a)scenarioObjects.1"/> + <messageLinks source="//(a)scenarioObjects.2" target="//(a)scenarioObjects.3"/> + <messageLinks source="//(a)scenarioObjects.4" target="//(a)scenarioObjects.5"/> + <messageLinks source="//(a)scenarioObjects.6" target="//(a)scenarioObjects.7"/> + <participants type="Buyer"/> + <participants type="sto:Store"/> + <participants type="ca:CreditAgency"/> +</scn:Scenario> Modified: runtime/trunk/samples/jbossesb/purchasing/models/PurchaseGoods.cdm =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/PurchaseGoods.cdm 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/PurchaseGoods.cdm 2009-11-30 15:45:25 UTC (rev 95) @@ -3,13 +3,15 @@ <typeDefinitions> <nameSpaces description="Target Namespace for PurchaseGoods" prefix="tns" uRI="http://www.jboss.org/savara/examples"/> <nameSpaces description="XML Schema Namespace" prefix="xsd" uRI="http://www.w3.org/2001/XMLSchema"/> - <nameSpaces prefix="pur" uRI="java:org.jboss.savara.examples.purchasing"/> - <informationTypes description="This is the information type BuyConfirmed" name="BuyConfirmed" elementName="BuyConfirmed"/> - <informationTypes description="This is the information type BuyFailed" name="BuyFailed" elementName="BuyFailed"/> - <informationTypes description="This is the information type BuyRequest" name="BuyRequest" typeName="" elementName="BuyRequest"/> - <informationTypes description="This is the information type CreditCheckInvalid" name="CreditCheckInvalid" elementName="CreditCheckInvalid"/> - <informationTypes description="This is the information type CreditCheckOk" name="CreditCheckOk" elementName="CreditCheckOk"/> - <informationTypes description="This is the information type CreditCheckRequest" name="CreditCheckRequest" elementName="CreditCheckRequest"/> + <nameSpaces prefix="pur" uRI="http://www.jboss.org/examples/purchasing"/> + <nameSpaces prefix="sto" uRI="http://www.jboss.org/examples/store"/> + <nameSpaces prefix="ca" uRI="http://www.jboss.org/examples/creditAgency"/> + <informationTypes description="This is the information type BuyConfirmed" name="BuyConfirmed" typeName="sto:BuyConfirmed" elementName=""/> + <informationTypes description="This is the information type BuyFailed" name="BuyFailed" typeName="sto:BuyFailed" elementName=""/> + <informationTypes description="This is the information type BuyRequest" name="BuyRequest" typeName="sto:BuyRequest" elementName=""/> + <informationTypes description="This is the information type CreditCheckInvalid" name="CreditCheckInvalid" typeName="ca:CreditCheckInvalid" elementName=""/> + <informationTypes description="This is the information type CreditCheckOk" name="CreditCheckOk" typeName="ca:CreditCheckOk" elementName=""/> + <informationTypes description="This is the information type CreditCheckRequest" name="CreditCheckRequest" typeName="ca:CreditCheckRequest" elementName=""/> <informationTypes description="This is the information type IDType" name="IDType" typeName="xsd:string"/> <informationTypes description="This is the information type URITokenType" name="URITokenType" typeName="xsd:anyURI"/> <tokens description="This is the token ID" name="ID" informationType="//@typeDefinitions/(a)informationTypes.6"/> @@ -24,20 +26,20 @@ <behaviors description="This is the behavior BuyerBehavior" name="BuyerBehavior"/> </roleTypes> <roleTypes description="This is the role type CreditAgency" name="CreditAgency"> - <behaviors description="This is the behavior CreditAgencyBehavior" name="CreditAgencyBehavior"/> + <behaviors description="This is the behavior CreditAgencyBehavior" name="CreditAgencyBehavior" interface="ca:CreditAgencyInterface"/> </roleTypes> <roleTypes description="This is the role type Store" name="Store"> - <behaviors description="This is the behavior StoreBehavior" name="StoreBehavior"/> + <behaviors description="This is the behavior StoreBehavior" name="StoreBehavior" interface="sto:StoreInterface"/> </roleTypes> <relationshipTypes description="Relationship between Buyer and Store" name="BuyerToStoreRel" firstRoleType="//@typeDefinitions/(a)roleTypes.0" secondRoleType="//@typeDefinitions/(a)roleTypes.2"/> <relationshipTypes description="Relationship between Store and CreditAgency" name="StoreToCreditAgencyRel" firstRoleType="//@typeDefinitions/(a)roleTypes.2" secondRoleType="//@typeDefinitions/(a)roleTypes.1"/> <participantTypes description="This is the participant type Buyer" name="Buyer" roleTypes="//@typeDefinitions/(a)roleTypes.0"> <semanticAnnotations annotation="savara.samples.Purchasing@Buyer" name="conversationType"/> </participantTypes> - <participantTypes description="This is the participant type CreditAgency" name="CreditAgency" roleTypes="//@typeDefinitions/(a)roleTypes.1"> + <participantTypes description="This is the participant type ca:CreditAgency" name="ca:CreditAgency" roleTypes="//@typeDefinitions/(a)roleTypes.1"> <semanticAnnotations annotation="savara.samples.Common@CreditAgency" name="conversationType"/> </participantTypes> - <participantTypes description="This is the participant type Store" name="Store" roleTypes="//@typeDefinitions/(a)roleTypes.2"> + <participantTypes description="This is the participant type sto:Store" name="sto:Store" roleTypes="//@typeDefinitions/(a)roleTypes.2"> <semanticAnnotations annotation="savara.samples.Purchasing@Store" name="conversationType"/> </participantTypes> <channelTypes description="This is the channel type CreditAgencyChannelType" name="CreditAgencyChannelType" referenceToken="//@typeDefinitions/(a)tokens.1" roleType="//@typeDefinitions/(a)roleTypes.1"> Modified: runtime/trunk/samples/jbossesb/purchasing/models/SuccessfulPurchase.scn =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/models/SuccessfulPurchase.scn 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/models/SuccessfulPurchase.scn 2009-11-30 15:45:25 UTC (rev 95) @@ -1,18 +1,18 @@ -<?xml version="1.0" encoding="Cp1252"?> -<scn:Scenario xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:scn="http://www.pi4soa.org/scenario" name="SuccessfulPurchase" description="Successfully purchase goods" author="" choreographyDescriptionURL="PurchaseGoods.cdm"> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" messageType="BuyRequest" valueURL="BuyRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" direction="receive" messageType="BuyRequest" valueURL="BuyRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" messageType="CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" direction="receive" messageType="CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" isRequest="false" messageType="CreditCheckOk" valueURL="CreditCheckOk.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" isRequest="false" direction="receive" messageType="CreditCheckOk" valueURL="CreditCheckOk.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" isRequest="false" messageType="BuyConfirmed" valueURL="BuyConfirmed.xml"/> - <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" isRequest="false" direction="receive" messageType="BuyConfirmed" valueURL="BuyConfirmed.xml"/> - <messageLinks source="//(a)scenarioObjects.0" target="//(a)scenarioObjects.1"/> - <messageLinks source="//(a)scenarioObjects.2" target="//(a)scenarioObjects.3"/> - <messageLinks source="//(a)scenarioObjects.4" target="//(a)scenarioObjects.5"/> - <messageLinks source="//(a)scenarioObjects.6" target="//(a)scenarioObjects.7"/> - <participants type="Buyer"/> - <participants type="Store"/> - <participants type="CreditAgency"/> -</scn:Scenario> +<?xml version="1.0" encoding="UTF-8"?> +<scn:Scenario xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:scn="http://www.pi4soa.org/scenario" name="SuccessfulPurchase" description="Successfully purchase goods" author="" choreographyDescriptionURL="PurchaseGoods.cdm"> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" messageType="{http://www.jboss.org/examples/store}BuyRequest" valueURL="BuyRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" direction="receive" messageType="{http://www.jboss.org/examples/store}BuyRequest" valueURL="BuyRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" direction="receive" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest" valueURL="CreditCheckRequest.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.2" operationName="checkCredit" isRequest="false" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckOk" valueURL="CreditCheckOk.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="checkCredit" isRequest="false" direction="receive" messageType="{http://www.jboss.org/examples/creditAgency}CreditCheckOk" valueURL="CreditCheckOk.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.1" operationName="buy" isRequest="false" messageType="{http://www.jboss.org/examples/store}BuyConfirmed" valueURL="BuyConfirmed.xml"/> + <scenarioObjects xsi:type="scn:MessageEvent" participant="//(a)participants.0" operationName="buy" isRequest="false" direction="receive" messageType="{http://www.jboss.org/examples/store}BuyConfirmed" valueURL="BuyConfirmed.xml"/> + <messageLinks source="//(a)scenarioObjects.0" target="//(a)scenarioObjects.1"/> + <messageLinks source="//(a)scenarioObjects.2" target="//(a)scenarioObjects.3"/> + <messageLinks source="//(a)scenarioObjects.4" target="//(a)scenarioObjects.5"/> + <messageLinks source="//(a)scenarioObjects.6" target="//(a)scenarioObjects.7"/> + <participants type="Buyer"/> + <participants type="sto:Store"/> + <participants type="ca:CreditAgency"/> +</scn:Scenario> Modified: runtime/trunk/samples/jbossesb/purchasing/store/src/main/resources/META-INF/jboss-esb.xml =================================================================== --- runtime/trunk/samples/jbossesb/purchasing/store/src/main/resources/META-INF/jboss-esb.xml 2009-11-27 18:54:32 UTC (rev 94) +++ runtime/trunk/samples/jbossesb/purchasing/store/src/main/resources/META-INF/jboss-esb.xml 2009-11-30 15:45:25 UTC (rev 95) @@ -29,7 +29,7 @@ <property name="conversationType" value="savara.samples.Purchasing@Store"/> <property name="paths"> <case service-category="org.jboss.savara.examples.purchasegoods" service-name="PurchaseGoodsProcess_Store__1"> - <message type="BuyRequest"/> + <message type="{http://www.jboss.org/examples/store}BuyRequest"/> </case> </property> </action> @@ -42,7 +42,7 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="PurchaseGoodsProcess_Store__1_action_1" process="process"> <property name="operation" value="buy"/> - <property name="messageType" value="BuyRequest"/> + <property name="messageType" value="{http://www.jboss.org/examples/store}BuyRequest"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.store.MemoryEPRStorage" /> </action> @@ -50,7 +50,7 @@ </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="PurchaseGoodsProcess_Store__1_action_2" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckRequest"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckRequest"/> <property name="serviceCategory" value="org.jboss.savara.examples.purchasegoods"/> <property name="serviceName" value="PurchaseGoodsProcess_CreditAgency"/> <property name="responseServiceCategory" value="org.jboss.savara.examples.purchasegoods"/> @@ -65,13 +65,13 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="PurchaseGoodsProcess_Store__2_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckOk"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckOk"/> </action> <action name="purchasing-success" class="org.jboss.savara.examples.store.SetBuyResponseMessageAction"> </action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="PurchaseGoodsProcess_Store__2_action_2" process="process"> <property name="operation" value="buy"/> - <property name="messageType" value="BuyConfirmed"/> + <property name="messageType" value="{http://www.jboss.org/examples/store}BuyConfirmed"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.store.MemoryEPRStorage" /> </action> @@ -84,12 +84,12 @@ <actions mep="OneWay"> <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" name="PurchaseGoodsProcess_Store__3_action_1" process="process"> <property name="operation" value="checkCredit"/> - <property name="messageType" value="CreditCheckInvalid"/> + <property name="messageType" value="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid"/> </action> <action name="purchasing-failed" class="org.jboss.savara.examples.store.SetBuyFailedMessageAction"></action> <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" name="PurchaseGoodsProcess_Store__3_action_2" process="process"> <property name="operation" value="buy"/> - <property name="messageType" value="BuyFailed"/> + <property name="messageType" value="{http://www.jboss.org/examples/store}BuyFailed"/> <property name="clientRole" value="Buyer"/> <property name="eprStore" value="org.jboss.savara.examples.store.MemoryEPRStorage" /> </action> @@ -103,10 +103,10 @@ <action class="org.jboss.savara.jbossesb.actions.SwitchAction" name="checkCredit_action_1" process="process"> <property name="paths"> <case service-category="org.jboss.savara.examples.purchasegoods" service-name="PurchaseGoodsProcess_Store__2"> - <message type="CreditCheckOk"/> + <message type="{http://www.jboss.org/examples/creditAgency}CreditCheckOk"/> </case> <case service-category="org.jboss.savara.examples.purchasegoods" service-name="PurchaseGoodsProcess_Store__3"> - <message type="CreditCheckInvalid"/> + <message type="{http://www.jboss.org/examples/creditAgency}CreditCheckInvalid"/> </case> </property> </action>

14 years, 4 months

1
0
0 / 0

savara SVN: r94 - in runtime/trunk: distribution/src/main/release/install and 3 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-27 13:54:32 -0500 (Fri, 27 Nov 2009) New Revision: 94 Modified: runtime/trunk/distribution/src/main/release/README.txt runtime/trunk/distribution/src/main/release/install/README.txt runtime/trunk/distribution/src/main/release/install/build.xml runtime/trunk/distribution/src/main/release/install/deployment.properties runtime/trunk/distribution/src/main/release/samples/jbossesb/common_build.xml runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml runtime/trunk/samples/jbossesb/client/build.xml Log: Updated docs based on getting the purchasing example build and deploy working. Modified: runtime/trunk/distribution/src/main/release/README.txt =================================================================== --- runtime/trunk/distribution/src/main/release/README.txt 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/distribution/src/main/release/README.txt 2009-11-27 18:54:32 UTC (rev 94) @@ -1,14 +1,13 @@ -Savara README -=================== +SAVARA Runtime README +===================== -Please refer to the Installation section, within the Getting Started Guide in the docs -folder, which explains how to install the CDL governance capabilities into the -JBossESB environment. +Please refer to the README.txt in the 'install' folder for instructions on +how to install the SAVARA Runtime capabilities into the JBossESB environment. -If you are new to SOA Governance using CDL, then please refer to the Getting Started -Guide in the docs folder. Otherwise more detailed information can be found in the -User Guide within the docs folder. +If you are new to "conversation aware" ESB action concept, then please refer +to the Getting Started Guide and User Guide associated with the SAVARA Eclipse Tools for +more information. The Samples Guide in the docs folder explains how to run some examples demonstrating -the CDL based Governance capabilities. +the execution of ESB services that use the "conversation aware" ESB actions. Modified: runtime/trunk/distribution/src/main/release/install/README.txt =================================================================== --- runtime/trunk/distribution/src/main/release/install/README.txt 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/distribution/src/main/release/install/README.txt 2009-11-27 18:54:32 UTC (rev 94) @@ -1,3 +1,20 @@ -The build.xml script in this directory is responsible for deploying the validator and conversational runtime for JBoss ESB. +Installation instructions for SAVARA Runtime +============================================ -The usage and instructions please refer to $doc/gettingstartedguide Installation chapter for detail. +1) Download JBossAS (http://www.jboss.org/jbossas) - version 5.1.0.GA or higher. Follow the installation +instructions that accompany this distribution. + +2) Download JBossESB (http://www.jboss.org/jbossesb) - version 4.7 or higher. Follow the installation +instructions that accompany this distribution, on how to install the ESB into the JBossAS environment. + +3) Edit the deployment.properties file in this ${SAVARA-Runtime}/install folder. Set the org.jboss.as.home +property to the root directory where the JBossAS environment is located, and change the +org.jboss.as.config property from default if you wish to start your JBossAS using a different +configuration. + +4) Start a command window and execute the command 'ant deploy'. + +5) You should now start your JBossAS server. + +When you wish to uninstall this component, simply go back to the ${SAVARA-Runtime}/install folder +and execute the command 'ant undeploy'. Modified: runtime/trunk/distribution/src/main/release/install/build.xml =================================================================== --- runtime/trunk/distribution/src/main/release/install/build.xml 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/distribution/src/main/release/install/build.xml 2009-11-27 18:54:32 UTC (rev 94) @@ -1,12 +1,12 @@ <project name="SAVARA_Runtime_Installer" default="deploy" basedir=".">  - <property name="org.jboss.esb.deployment.properties" location="deployment.properties"/> + <property name="org.jboss.as.deployment.properties" location="deployment.properties"/>  - <property file="${org.jboss.esb.deployment.properties}"/> + <property file="${org.jboss.as.deployment.properties}"/> - <property name="server.dir" value="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}"/> + <property name="server.dir" value="${org.jboss.as.home}/server/${org.jboss.as.config}"/> <property name="conf.dir" value="${server.dir}/conf"/> <property name="deploy.dir" value="${server.dir}/deploy"/> <property name="server.lib.dir" value="${server.dir}/lib"/> @@ -14,27 +14,26 @@ <property name="modules" value="../modules" /> <target name="check.deploy.props"> - <condition property="esb.server.configured"> + <condition property="as.configured"> <and> - <isset property="org.jboss.esb.server.home"/> - <isset property="org.jboss.esb.server.config"/> + <isset property="org.jboss.as.home"/> + <isset property="org.jboss.as.config"/> </and> </condition> - <fail unless="esb.server.configured" message="Cannot determine target deployment, please check deployment.properties"/> + <fail unless="as.configured" message="Cannot determine target deployment, please check deployment.properties"/> </target> - <target name="deploy" description="Deploys Savara Runtime to the server"> - <echo message="Deploy savara runtime to JBoss ESB server" /> + <target name="deploy" description="Deploys SAVARA Runtime to the server"> + <echo message="Deploy SAVARA Runtime to JBoss AS/ESB server" /> <copy todir="${deploy.dir}/savara-runtime-jbossesb.esb"> <fileset dir="${modules}/savara-runtime-jbossesb.esb"/> </copy> </target> - <target name="undeploy" description="Undeploys Savara Runtime"> - <echo message="Undeploy the savara runtime jbossesb from JBoss ESB server" /> + <target name="undeploy" description="Undeploys SAVARA Runtime"> + <echo message="Undeploy the SAVARA Runtime from JBoss AS/ESB server" /> <delete dir="${deploy.dir}/savara-runtime-jbossesb.esb" /> </target> - </project> Modified: runtime/trunk/distribution/src/main/release/install/deployment.properties =================================================================== --- runtime/trunk/distribution/src/main/release/install/deployment.properties 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/distribution/src/main/release/install/deployment.properties 2009-11-27 18:54:32 UTC (rev 94) @@ -6,12 +6,14 @@ # EJB3 has been installed. # This path should not include spaces. # Use of relative paths or paths with spaces will cause runtime errors -# when deploying and executing the quickstart and the trailblazers. +# when deploying and executing the samples. # (e.g. /local/deploy/jboss-5.1.0.GA) -org.jboss.esb.server.home=/local/deploy/jboss-5.1.0.GA +org.jboss.as.home=/local/deploy/jboss-5.1.0.GA + # The Configuration of JBoss AS to Use # (e.g. default) -org.jboss.esb.server.config=default +org.jboss.as.config=default + # The directory for JBossESB home -# (e.g. /local/deploy/jbossesb-4.6.GA) -org.jboss.esb.home=/local/deploy/jbossesb-4.6.GA +# (e.g. /local/deploy/jbossesb-4.7) +org.jboss.esb.home=/local/deploy/jbossesb-4.7 Modified: runtime/trunk/distribution/src/main/release/samples/jbossesb/common_build.xml =================================================================== --- runtime/trunk/distribution/src/main/release/samples/jbossesb/common_build.xml 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/distribution/src/main/release/samples/jbossesb/common_build.xml 2009-11-27 18:54:32 UTC (rev 94) @@ -2,12 +2,14 @@ <property file="../../../install/deployment.properties" /> + <property name="modules" value="../../../modules" /> + <property name="build.dir" value="${basedir}/target" /> <property name="classes" value="${build.dir}/classes" /> <property name="libs" value="${basedir}/lib" /> <property name="src" value="src" /> - <property name="server.dir" value="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}"/> + <property name="server.dir" value="${org.jboss.as.home}/server/${org.jboss.as.config}"/> <path id="example-classpath"> <fileset dir="${libs}" includes="*.jar" /> @@ -28,8 +30,8 @@ <target name="messaging-config" depends="jbossesb-dependencies-as4, jbossesb-dependencies-as5"> <condition property="messaging.present"> <or> - <available file="${org.jboss.esb.server.deploy.dir}/jboss-messaging"/> - <available file="${org.jboss.esb.server.deploy.dir}/messaging"/> + <available file="${org.jboss.as.deploy.dir}/jboss-messaging"/> + <available file="${org.jboss.as.deploy.dir}/messaging"/> </or> </condition> <condition property="messaging.present"> @@ -91,32 +93,32 @@    - - + +  <target name="check-as-version"> - <property name="org.jboss.esb.server.server" location="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}"/> - <echo message="${org.jboss.esb.server.server}"/> + <property name="org.jboss.as.server" location="${org.jboss.as.home}/server/${org.jboss.as.config}"/> + <echo message="${org.jboss.as.server}"/>  <condition property="jbossas5"> - <available file="${org.jboss.esb.server.server}/deployers"/> + <available file="${org.jboss.as.server}/deployers"/> </condition>  <condition property="jbossas4"> <not> - <available file="${org.jboss.esb.server.server}/deployers"/> + <available file="${org.jboss.as.server}/deployers"/> </not> </condition> </target> <target name="classpath-dependencies-as4" if="jbossas4" depends="messaging-dependencies, jbossmq-dependencies"> <path id="compile-classpath"> - <fileset dir="${org.jboss.esb.server.home}/client" includes="hibernate-client.jar" />  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="hibernate3.jar quartz-all.jar"/>  + <fileset dir="${org.jboss.as.home}/client" includes="hibernate-client.jar" />  + <fileset dir="${org.jboss.as.server}/lib" includes="hibernate3.jar quartz-all.jar"/>  <path refid="deployment-classpath" /> <path refid="example-classpath" /> - <fileset dir="${org.jboss.esb.server.home}/client" includes="*.jar" />  + <fileset dir="${org.jboss.as.home}/client" includes="*.jar" />  </path> <property name="compile-classpath" refid="compile-classpath"/> @@ -124,11 +126,11 @@ <pathelement location="." /> <pathelement location="${classes}" /> <pathelement location="${basedir}/src" /> - <fileset dir="${org.jboss.esb.server.server}/lib" includes="jboss-remoting.jar jboss-j2ee.jar jboss-messaging-client.jar" />  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="hibernate3.jar commons-collections.jar hsqldb.jar" />  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="bsh.jar" />  - <fileset dir="${org.jboss.esb.server.home}/lib/endorsed" includes="*.jar" />  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jboss-aop-jdk50.deployer" includes="jboss-aop-jdk50.jar" />  + <fileset dir="${org.jboss.as.server}/lib" includes="jboss-remoting.jar jboss-j2ee.jar jboss-messaging-client.jar" />  + <fileset dir="${org.jboss.as.server}/lib" includes="hibernate3.jar commons-collections.jar hsqldb.jar" />  + <fileset dir="${org.jboss.as.server}/lib" includes="bsh.jar" />  + <fileset dir="${org.jboss.as.home}/lib/endorsed" includes="*.jar" />  + <fileset dir="${org.jboss.as.deploy.dir}/jboss-aop-jdk50.deployer" includes="jboss-aop-jdk50.jar" />  <path refid="compile-classpath" /> <pathelement location="${pwd}/anttasks/classes" /> </path> @@ -138,12 +140,13 @@ <target name="classpath-dependencies-as5" if="jbossas5" depends="messaging-dependencies, jbossmq-dependencies"> <path id="compile-classpath"> - <fileset dir="${org.jboss.esb.server.home}/common/lib" includes="hibernate-*.jar" />  - <fileset dir="${org.jboss.esb.server.home}/common/lib" includes="quartz.jar"/>  + <fileset dir="${modules}/savara-runtime-jbossesb.esb" includes="savara-runtime-jbossesb*.jar"/> + <fileset dir="${org.jboss.as.home}/common/lib" includes="hibernate-*.jar" />  + <fileset dir="${org.jboss.as.home}/common/lib" includes="quartz.jar"/>  <pathelement location="${org.jboss.esb.server.common.lib}/commons-httpclient.jar"/> <path refid="deployment-classpath" /> <path refid="example-classpath" /> - <fileset dir="${org.jboss.esb.server.home}/client" excludes="jbossws-native-jaxws.jar jbossws-native-jaxws-ext.jar jaxws-rt.jar jaxws-tools.jar" /> + <fileset dir="${org.jboss.as.home}/client" excludes="jbossws-native-jaxws.jar jbossws-native-jaxws-ext.jar jaxws-rt.jar jaxws-tools.jar" /> </path> <property name="compile-classpath" refid="compile-classpath"/> @@ -151,12 +154,12 @@ <pathelement location="." /> <pathelement location="${classes}" /> <pathelement location="${basedir}/src" /> - <fileset dir="${org.jboss.esb.server.home}/common/lib" includes="jboss-remoting.jar jboss-javaee.jar jboss-messaging-client.jar" />  - <fileset dir="${org.jboss.esb.server.home}/client" includes="jboss-messaging-client.jar" />  - <fileset dir="${org.jboss.esb.server.home}/common/lib" includes="hibernate-*.jar commons-collections.jar hsqldb.jar" />  - <fileset dir="${org.jboss.esb.server.home}/common/lib" includes="bsh.jar" />  - <fileset dir="${org.jboss.esb.server.home}/lib/endorsed" includes="*.jar" />  - <fileset dir="${org.jboss.esb.server.home}/lib" includes="jboss-aop.jar" />  + <fileset dir="${org.jboss.as.home}/common/lib" includes="jboss-remoting.jar jboss-javaee.jar jboss-messaging-client.jar" />  + <fileset dir="${org.jboss.as.home}/client" includes="jboss-messaging-client.jar" />  + <fileset dir="${org.jboss.as.home}/common/lib" includes="hibernate-*.jar commons-collections.jar hsqldb.jar" />  + <fileset dir="${org.jboss.as.home}/common/lib" includes="bsh.jar" />  + <fileset dir="${org.jboss.as.home}/lib/endorsed" includes="*.jar" />  + <fileset dir="${org.jboss.as.home}/lib" includes="jboss-aop.jar" />  <path refid="compile-classpath" /> <pathelement location="${pwd}/anttasks/classes" /> </path> @@ -166,121 +169,121 @@  <target name="jbossesb-dependencies-as4" if="jbossas4" depends="check-as-version"> - <property name="org.jboss.esb.server.server" location="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}"/> - <property name="org.jboss.esb.server.deploy.dir" location="${org.jboss.esb.server.server}/deploy"/> + <property name="org.jboss.as.server" location="${org.jboss.as.home}/server/${org.jboss.as.config}"/> + <property name="org.jboss.as.deploy.dir" location="${org.jboss.as.server}/deploy"/> <path id="deployment-classpath">  - <fileset dir="${org.jboss.esb.server.home}/client" includes="jboss-jaxws.jar jboss-saaj.jar jbossws-common.jar jbossws-spi.jar"/> + <fileset dir="${org.jboss.as.home}/client" includes="jboss-jaxws.jar jboss-saaj.jar jbossws-common.jar jbossws-spi.jar"/> - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib" includes="*.jar"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbossesb.sar/lib" includes="*.jar"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbossesb.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbossesb.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/jbossesb.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbpm.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/jbpm.esb"/> - <pathelement location="${org.jboss.esb.server.server}/lib/cglib.jar"/> - <pathelement location="${org.jboss.esb.server.server}/lib/dom4j.jar"/> - <pathelement location="${org.jboss.esb.server.server}/lib/antlr.jar"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbpm.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/jbpm.esb"/> + <pathelement location="${org.jboss.as.server}/lib/cglib.jar"/> + <pathelement location="${org.jboss.as.server}/lib/dom4j.jar"/> + <pathelement location="${org.jboss.as.server}/lib/antlr.jar"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/smooks.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/smooks.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/smooks.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/smooks.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbrules.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/jbrules.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbrules.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/jbrules.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/spring.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/spring.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/spring.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/spring.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/soap.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/soap.esb"/> - <fileset dir="${org.jboss.esb.server.server}/lib" includes="activation.jar, mail.jar, jboss-ejb3x.jar"/> + <fileset dir="${org.jboss.as.deploy.dir}/soap.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/soap.esb"/> + <fileset dir="${org.jboss.as.server}/lib" includes="activation.jar, mail.jar, jboss-ejb3x.jar"/>  - <pathelement location="${org.jboss.esb.server.home}/lib/commons-logging.jar"/> - <pathelement location="${org.jboss.esb.server.home}/lib/commons-codec.jar"/> - <pathelement location="${org.jboss.esb.server.home}/lib/jboss-system.jar"/> - <pathelement location="${org.jboss.esb.server.home}/lib/jboss-xml-binding.jar"/> - <pathelement location="${org.jboss.esb.server.server}/lib/jbossts-common.jar"/> - <pathelement location="${org.jboss.esb.server.server}/lib/quartz.jar"/> + <pathelement location="${org.jboss.as.home}/lib/commons-logging.jar"/> + <pathelement location="${org.jboss.as.home}/lib/commons-codec.jar"/> + <pathelement location="${org.jboss.as.home}/lib/jboss-system.jar"/> + <pathelement location="${org.jboss.as.home}/lib/jboss-xml-binding.jar"/> + <pathelement location="${org.jboss.as.server}/lib/jbossts-common.jar"/> + <pathelement location="${org.jboss.as.server}/lib/quartz.jar"/>  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="jboss-cache*.jar"/> - <pathelement location="${org.jboss.esb.server.server}/lib/jgroups.jar"/> + <fileset dir="${org.jboss.as.server}/lib" includes="jboss-cache*.jar"/> + <pathelement location="${org.jboss.as.server}/lib/jgroups.jar"/>  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="h2*.jar"/> + <fileset dir="${org.jboss.as.server}/lib" includes="h2*.jar"/>  - <fileset dir="${org.jboss.esb.server.home}/client" includes="jaxb-api.jar jaxb-impl.jar jaxb-xjc.jar"/> - <fileset dir="${org.jboss.esb.server.home}/client" includes="jbossall-client.jar"/> + <fileset dir="${org.jboss.as.home}/client" includes="jaxb-api.jar jaxb-impl.jar jaxb-xjc.jar"/> + <fileset dir="${org.jboss.as.home}/client" includes="jbossall-client.jar"/>  - <fileset dir="${org.jboss.esb.server.home}/lib" includes="commons-httpclient.jar"/> - <fileset dir="${org.jboss.esb.server.home}/lib/endorsed" includes="xalan.jar"/> + <fileset dir="${org.jboss.as.home}/lib" includes="commons-httpclient.jar"/> + <fileset dir="${org.jboss.as.home}/lib/endorsed" includes="xalan.jar"/> </path> </target>  <target name="jbossesb-dependencies-as5" if="jbossas5" depends="check-as-version"> - <property name="org.jboss.esb.server.server" location="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}"/> - <property name="org.jboss.esb.server.deploy.dir" location="${org.jboss.esb.server.server}/deploy"/> - <property name="org.jboss.esb.server.common.lib" location="${org.jboss.esb.server.home}/common/lib"/> + <property name="org.jboss.as.server" location="${org.jboss.as.home}/server/${org.jboss.as.config}"/> + <property name="org.jboss.as.deploy.dir" location="${org.jboss.as.server}/deploy"/> + <property name="org.jboss.as.common.lib" location="${org.jboss.as.home}/common/lib"/> <path id="deployment-classpath">  - <fileset dir="${org.jboss.esb.server.common.lib}" includes="jbossws-native-jaxws.jar jbossws-native-jaxws-ext.jar jboss-saaj.jar jbossws-common.jar"/> - <fileset dir="${org.jboss.esb.server.common.lib}" includes="jbossws-common.jar jbossws-framework.jar jbossws-native-jaxrpc.jar jbossws-native-saaj.jar jbossws-spi.jar"/> + <fileset dir="${org.jboss.as.common.lib}" includes="jbossws-native-jaxws.jar jbossws-native-jaxws-ext.jar jboss-saaj.jar jbossws-common.jar"/> + <fileset dir="${org.jboss.as.common.lib}" includes="jbossws-common.jar jbossws-framework.jar jbossws-native-jaxrpc.jar jbossws-native-saaj.jar jbossws-spi.jar"/> - <fileset dir="${org.jboss.esb.server.server}/deployers/esb.deployer/lib" includes="*.jar"/> + <fileset dir="${org.jboss.as.server}/deployers/esb.deployer/lib" includes="*.jar"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbossesb.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbossesb.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/jbossesb.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbpm.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/jbpm.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbpm.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/jbpm.esb"/> - <pathelement location="${org.jboss.esb.server.home}/lib/dom4j.jar"/> - <pathelement location="${org.jboss.esb.server.common.lib}/antlr.jar"/> + <pathelement location="${org.jboss.as.home}/lib/dom4j.jar"/> + <pathelement location="${org.jboss.as.common.lib}/antlr.jar"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/smooks.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/smooks.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/smooks.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/smooks.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/jbrules.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/jbrules.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/jbrules.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/jbrules.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/spring.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/spring.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/spring.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/spring.esb"/>  - <fileset dir="${org.jboss.esb.server.deploy.dir}/soap.esb" includes="*.jar"/> - <pathelement location="${org.jboss.esb.server.deploy.dir}/soap.esb"/> + <fileset dir="${org.jboss.as.deploy.dir}/soap.esb" includes="*.jar"/> + <pathelement location="${org.jboss.as.deploy.dir}/soap.esb"/> - <fileset dir="${org.jboss.esb.server.home}/lib/endorsed" includes="activation.jar"/> - <fileset dir="${org.jboss.esb.server.common.lib}" includes="mail.jar, jboss-ejb3x.jar"/> + <fileset dir="${org.jboss.as.home}/lib/endorsed" includes="activation.jar"/> + <fileset dir="${org.jboss.as.common.lib}" includes="mail.jar, jboss-ejb3x.jar"/>  - <pathelement location="${org.jboss.esb.server.common.lib}/commons-logging.jar"/> - <pathelement location="${org.jboss.esb.server.common.lib}/quartz.jar"/> + <pathelement location="${org.jboss.as.common.lib}/commons-logging.jar"/> + <pathelement location="${org.jboss.as.common.lib}/quartz.jar"/> - <pathelement location="${org.jboss.esb.server.home}/lib/jboss-system.jar"/> - <pathelement location="${org.jboss.esb.server.home}/lib/jboss-xml-binding.jar"/> + <pathelement location="${org.jboss.as.home}/lib/jboss-system.jar"/> + <pathelement location="${org.jboss.as.home}/lib/jboss-xml-binding.jar"/>  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="jbosscache-*.jar"/> + <fileset dir="${org.jboss.as.server}/lib" includes="jbosscache-*.jar"/>  - <fileset dir="${org.jboss.esb.server.server}/lib" includes="h2*.jar"/> + <fileset dir="${org.jboss.as.server}/lib" includes="h2*.jar"/> - <fileset dir="${org.jboss.esb.server.home}/lib/endorsed" includes="xalan.jar"/> + <fileset dir="${org.jboss.as.home}/lib/endorsed" includes="xalan.jar"/>  - <fileset dir="${org.jboss.esb.server.home}/client" includes="jaxb-api.jar jaxb-impl.jar jaxb-xjc.jar"/> - <fileset dir="${org.jboss.esb.server.home}/client" includes="jbossall-client.jar"/> + <fileset dir="${org.jboss.as.home}/client" includes="jaxb-api.jar jaxb-impl.jar jaxb-xjc.jar"/> + <fileset dir="${org.jboss.as.home}/client" includes="jbossall-client.jar"/>  - <fileset dir="${org.jboss.esb.server.common.lib}" includes="commons-httpclient.jar"/> + <fileset dir="${org.jboss.as.common.lib}" includes="commons-httpclient.jar"/> </path> </target> Modified: runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml 2009-11-27 18:54:32 UTC (rev 94) @@ -54,7 +54,7 @@ <para> To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>purchasing-models</filename> project contains the CDL used to perform conformance +The <filename>purchasing-models</filename> project contains the choreography used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the @@ -97,8 +97,8 @@ <title>Running the Example</title> <orderedlist> <listitem> - First step is to install the ESB services. (Presumely the JBoss ESB server started already) - In a command window, Go to the the <filename>${SAVARA-Runtime}/samples</filename> folder, + After starting the JBoss AS server, the first step is to install the ESB services. + In a command window, go to the <filename>${SAVARA-Runtime}/samples</filename> folder, execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. </listitem> <listitem> @@ -173,7 +173,7 @@ <para> To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on +The <filename>brokerage-models</filename> project contains the choreography used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the Modified: runtime/trunk/samples/jbossesb/client/build.xml =================================================================== --- runtime/trunk/samples/jbossesb/client/build.xml 2009-11-26 21:24:56 UTC (rev 93) +++ runtime/trunk/samples/jbossesb/client/build.xml 2009-11-27 18:54:32 UTC (rev 94) @@ -1,6 +1,8 @@ <project name="client" default="runPurchasingClient" basedir="."> <property file="../../install/deployment.properties" /> + <property name="modules" value="../../modules" /> + <import file="../common_build.xml"/> <target name="runPurchasingClient" depends="compile">

14 years, 4 months

1
0
0 / 0

savara SVN: r93 - runtime/trunk/docs/samplesguide/src/main and 3 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-26 16:24:56 -0500 (Thu, 26 Nov 2009) New Revision: 93 Added: validator/trunk/docs/samplesguide/src/main/module/servicevalidator.xml Removed: runtime/trunk/docs/userguide/ validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml Modified: runtime/trunk/docs/pom.xml runtime/trunk/docs/samplesguide/src/main/master.xml runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml runtime/trunk/docs/samplesguide/src/main/module/overview.xml validator/trunk/docs/samplesguide/src/main/master.xml validator/trunk/docs/samplesguide/src/main/module/overview.xml Log: Further updates to convert from Overlord CDL based to SAVARA docs. Modified: runtime/trunk/docs/pom.xml =================================================================== --- runtime/trunk/docs/pom.xml 2009-11-25 22:14:32 UTC (rev 92) +++ runtime/trunk/docs/pom.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -16,7 +16,6 @@ </parent> <modules> - <module>userguide</module> <module>samplesguide</module> </modules> Modified: runtime/trunk/docs/samplesguide/src/main/master.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/master.xml 2009-11-25 22:14:32 UTC (rev 92) +++ runtime/trunk/docs/samplesguide/src/main/master.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -5,7 +5,7 @@ <book lang="en"> <bookinfo> - <title>JBoss Savara 1.0-SNAPSHOT</title> + <title>SAVARA Runtime 1.0-SNAPSHOT</title> <subtitle>Samples Guide</subtitle> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/author_group.xml"/> </bookinfo> Modified: runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml 2009-11-25 22:14:32 UTC (rev 92) +++ runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -5,16 +5,25 @@ <title>"Conversation Aware" ESB Services</title> <para> -There are two examples to demonstrate the conversation aware ESB actions(for both stateful and stateless), and the conformance checking against a choreography. +There are two examples to demonstrate the <emphasis>conversation aware</emphasis> ESB actions. </para> <para> -These are <filename>purchasing</filename>, a simple customer/supplier example with two associated Eclipse projects (<filename>purchasing-store-stateful/less</filename> and <filename>purchasing-models</filename>), and <filename>brokerage</filename> which extends the purchasing example through the introduction of a broker that mediates between potentially multiple suppliers to find the best deal, defined within three Eclipse projects (<filename>brokerage-broker-stateful/less</filename>, <filename>brokerage-supplier-stateful/less</filename> and <filename>brokerage-models</filename>). +These are <filename>purchasing</filename>, a simple customer/supplier example with two associated +Eclipse projects (<filename>purchasing-store</filename> and <filename>purchasing-models</filename>), +and <filename>brokerage</filename> which extends the purchasing example through the introduction +of a broker that mediates between potentially multiple suppliers to find the best deal, defined +within three Eclipse projects (<filename>brokerage-broker</filename>, +<filename>brokerage-supplier</filename> and <filename>brokerage-models</filename>). </para> + <para> -These examples make use of a common <emphasis>Credit Agency</emphasis> service, defined within the <filename>common-creditAgency-stateful/less</filename> Eclipse project, and are executed through the use of client applications defined in the <filename>${OverlordCDL}/samples/client</filename> folder. +These examples make use of a common <emphasis>Credit Agency</emphasis> service, defined within +the <filename>common-creditAgency</filename> Eclipse project, and are executed through the use +of client applications defined in the <filename>${SAVARA-Runtime}/samples/client</filename> folder. </para> <warning> + JEFF - DOES THIS STILL APPLY??? At the moment, the conversation aware ESB runtime doesn't support the hot-deploy. That means if you update the business pojo class, such as <emphasis role="bold">$creditAgency/src/main/com/acme/services/creditAgency/CreditAgencyPurchase.java</emphasis> file, You need to re-deploy it, and then <emphasis role="bold">restart the server </emphasis> to cause it to take effect. This issue has been tracked under <ulink url="https://jira.jboss.org/jira/browse/SOAG-72">https://jira.jboss.org/jira/browse/SOAG-72</ulink>. Will be fixed in the next release. </warning> @@ -24,7 +33,8 @@ <section> <title>Overview</title> <para> -The purchasing example describes the interactions between a Buyer, Store and Credit Agency. The flow for this example would be: +The purchasing example describes the interactions between a Buyer, Store and Credit Agency. +The flow for this example would be: </para> <itemizedlist> <listitem> @@ -42,18 +52,24 @@ </itemizedlist> <para> -To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>purchasing-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. +To check conformance, we need to refer to the model and service implementation projects in the +Eclipse environment. +The <filename>purchasing-models</filename> project contains the CDL used to perform conformance +checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the +other projects. A full explanation of the conversation aware ESB actions can be found in the +<emphasis>Conversational Aware ESB</emphasis> section of the +<emphasis>SAVARA Eclipse Tools User Guide</emphasis>. </para> <para> To provide a simple demonstration of the conformance checking: </para> <orderedlist> <listitem> -Double click on <filename>purchasing-store[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> +Double click on <filename>purchasing-store/src/main/resources/META-INF/jboss-esb.xml</filename> </listitem> <listitem> -Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. +Scroll down to the second action, within the first service. This represents a +<emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. </listitem> <listitem> Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. @@ -63,35 +79,47 @@ </listitem> </orderedlist> <para> -The information regarding the expected message type is obtained from the choreography description in the <filename>purchasing-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. +The information regarding the expected message type is obtained from the choreography +description in the <filename>purchasing-models</filename> project. To identify the precise +interaction within the choreography that this error relates to, select the context menu associated +with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, +select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the +relevant interaction within the choreography description to be displayed. </para> <para> -Another Quick Fix option associated with this error is <emphasis>Update from Referenced Description</emphasis>. By selecting this option, you will notice that the message type is changed back to the value without the 'X'. +Another Quick Fix option associated with this error is +<emphasis>Update from Referenced Description</emphasis>. By selecting this option, you will notice +that the message type is changed back to the value without the 'X'. </para> </section> <section> <title>Running the Example</title> - <para> - This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. - One is the stateful purchasing example (this is the example that we had since M1 release),the other is stateless purchasing example that is introduced in the M2 release. - </para> <orderedlist> <listitem> First step is to install the ESB services. (Presumely the JBoss ESB server started already) - In a command window, Go to the the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/sample/stateless</filename> in the stateless approach), execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. + In a command window, Go to the the <filename>${SAVARA-Runtime}/samples</filename> folder, + execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. </listitem> <listitem> - Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runPurchasingClient</emphasis> (or <emphasis role="bold"> ant runStatelessPurchasingClient</emphasis> in stateless approach.), which will send a 'BuyRequest' message to the Store, which will then perform the credit check before returning a response to the client. + Go to the <filename>${SAVARA-Runtime}/samples/client</filename> folder and execute + <emphasis role="bold">ant runPurchasingClient</emphasis>, which will send a 'BuyRequest' + message to the Store, which will then perform the credit check before returning a + response to the client. </listitem> </orderedlist> <para> -To see a different response from the client, change the <emphasis>isCreditValid</emphasis> method on the <emphasis>CreditAgencyPurchase</emphasis> class to return <emphasis>false</emphasis>, within the <filename>common/creditAgency</filename> ESB service implementation, and then re-deploy the Credit Agency service. Then when the client is re-run, a 'BuyFailed' message will be returned. +To see a different response from the client, change the <emphasis>isCreditValid</emphasis> method +on the <emphasis>CreditAgencyPurchase</emphasis> class to return <emphasis>false</emphasis>, within +the <filename>common/creditAgency</filename> ESB service implementation, and then re-deploy the +Credit Agency service. Then when the client is re-run, a 'BuyFailed' message will be returned. </para> <tip> - <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-purchasing</command> in the <filename>$Overlord/samples/stateful</filename> folder or <filename>$Overlord/samples/stateless</filename> folder respectively.</para> + <para>You can undeploy the corresponding esb artifact by through command + <command>ant undeploy-purchasing</command> in the <filename>${SAVARA-Runtime}/samples</filename> + folder.</para> </tip> </section> @@ -105,7 +133,8 @@ <title>Overview</title> <para> -The brokerage example describes the interactions between a Customer, Broker, Supplier and Credit Agency. The flow for this example would be: +The brokerage example describes the interactions between a Customer, Broker, Supplier and Credit Agency. +The flow for this example would be: </para> <itemizedlist> @@ -116,7 +145,8 @@ Broker sends the request to one or more Suppliers concurrently </listitem> <listitem> -When all of the quote responses have been received, or a timeout expires, the available information is returned to the Customer +When all of the quote responses have been received, or a timeout expires, the available information is +returned to the Customer </listitem> <listitem> Customer decides whether to: @@ -133,7 +163,8 @@ If a 'buy' request is received by the Broker, it will send a 'credit check' request to the Credit Agency </listitem> <listitem> -If the Credit Agency returns a successful message, then the Broker sends a 'buy' request to the Supplier selected by the Customer (in the 'buy' request), followed by a confirmation back to the Customer +If the Credit Agency returns a successful message, then the Broker sends a 'buy' request to the Supplier +selected by the Customer (in the 'buy' request), followed by a confirmation back to the Customer </listitem> <listitem> If the Credit Agency returns a failed message, then the Broker will inform the Customer @@ -142,17 +173,22 @@ <para> To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. +The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on +the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. +A full explanation of the conversation aware ESB actions can be found in the +<emphasis>Conversational Aware ESB</emphasis> section of the +<emphasis>SAVARA Eclipse Tools User Guide</emphasis>. </para> <para> To provide a simple demonstration of the conformance checking: </para> <orderedlist> <listitem> -Double click on <filename>brokerage-broker[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> +Double click on <filename>brokerage-broker/src/main/resources/META-INF/jboss-esb.xml</filename> </listitem> <listitem> -Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. +Scroll down to the second action, within the first service. This represents a +<emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. </listitem> <listitem> Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. @@ -162,28 +198,35 @@ </listitem> </orderedlist> <para> -The information regarding the expected message type is obtained from the choreography description in the <filename>brokerage-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. +The information regarding the expected message type is obtained from the choreography description +in the <filename>brokerage-models</filename> project. To identify the precise interaction within the +choreography that this error relates to, select the context menu associated with the error and choose +the Quick Fix menu item. This will display a dialog with a list of fixes, select the +<emphasis>Show referenced description</emphasis> option and press OK. This will cause the +relevant interaction within the choreography description to be displayed. </para> </section> <section> <title>Running the Example</title> - <para> - This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. - one is the sateful broker example (this is the example that we had since M1 release), the other is stateless broker example that is introduced in the M2 release. - </para> <orderedlist> <listitem> First step is to install the ESB services (Presumely the JBoss ESB server started already) - In a command window, Go to the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/samples/stateless</filename> in the stateless approach), execute <emphasis role="bold">ant deploy-broker</emphasis> + In a command window, Go to the <filename>${SAVARA-Runtime}/samples</filename> folder, + execute <emphasis role="bold">ant deploy-broker</emphasis> </listitem> <listitem> - Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runBrokerageClient</emphasis> (or <emphasis role="bold"> ant runStatelessBrokerageClient</emphasis> in stateless approach), which will initially send an 'enquiry' message to the Broker, which will communicate with the set of Suppliers to obtain the best quote. The client will then send a 'buy' request, which will result in the Broker performing a credit check before returning a response to the client. + Go to the <filename>${SAVARA-Runtime}/samples/client</filename> folder and execute + <emphasis role="bold">ant runBrokerageClient</emphasis>, which will initially send an + 'enquiry' message to the Broker, which will communicate with the set of Suppliers to + obtain the best quote. The client will then send a 'buy' request, which will result in + the Broker performing a credit check before returning a response to the client. </listitem> </orderedlist> <tip> - <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-broker</command> in $Overlord/samples/stateful or $Overlord/samples/stateless respectively.</para> + <para>You can undeploy the corresponding esb artifact by through command + <command>ant undeploy-broker</command> in ${SAVARA-Runtime}/samples.</para> </tip> </section> Modified: runtime/trunk/docs/samplesguide/src/main/module/overview.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/module/overview.xml 2009-11-25 22:14:32 UTC (rev 92) +++ runtime/trunk/docs/samplesguide/src/main/module/overview.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -3,27 +3,24 @@ ]> <chapter id="overview"> <title>Overview</title> - <para>The Overlord CDL distribution contains two main types of functionality:</para> - <orderedlist> - <listitem> - the ability to validate executing services against a choreography description (an example of runtime governance). - </listitem> - <listitem> - the ability to build an ESB using 'conversation aware' actions which can be checked for conformance against a choreography description (an example of design time governance). - </listitem> - </orderedlist> <para> - This document will describe the samples available to demonstrate each aspect of the functionality. + This document will describe the samples available to demonstrate the runtime capabilities using + the "conversation aware" ESB actions. </para> <para> - Further information about configuring the runtime validation of services against a choreography can be found in the <emphasis role="bold">UserGuide</emphasis>. - Information regarding the conversation aware ESB actions, and how to use them in conjunction with conformance checking against a choreography description, can also be found in the <emphasis role="bold">UserGuide</emphasis>. + Information regarding the conversation aware ESB actions, and how to use them in conjunction with + conformance checking against a choreography description, can also be found in the + <emphasis role="bold">SAVARA Eclipse Tools User Guide</emphasis>. </para> <note> <para> - Before attempting to install and run these examples, you must follow the instructions in the <emphasis role="bold">"Installation" Chapter</emphasis> of the <emphasis role="bold">Getting Started Guide</emphasis> regarding installing Overlord CDL into a JBossAS environment, and importing the samples into the Eclipse environment. + Before attempting to deploy and run these examples, you must install the SAVARA Runtime + by following the instructions + in the <filename>${SAVARA-Runtime}/install</filename> folder. To be able to + examine and modify the examples, it is advisable to install the SAVARA Eclipse Tools, + and import the samples into the Eclipse environment. </para> </note> Modified: validator/trunk/docs/samplesguide/src/main/master.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/master.xml 2009-11-25 22:14:32 UTC (rev 92) +++ validator/trunk/docs/samplesguide/src/main/master.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -12,6 +12,6 @@ <toc/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/cdlvalidator.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/servicevalidator.xml"/> </book> Deleted: validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml 2009-11-25 22:14:32 UTC (rev 92) +++ validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -1,132 +0,0 @@ -<?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="cdlvalidator"> - <title>CDL Validator</title> - - <section> - <title>Trailblazer Example</title> - - <para> -This example can be found in the <filename>trailblazer</filename> folder, which contains an enhanced version of the trailblazer example found in the JBossESB distribution. See the TrailBlazer Guide in the JBossESB distribution (<filename>$JBossESB/docs/samples/TBGuide.pdf</filename>) for more information about the example. The main changes are the introduction of a File Based Bank, and modifications to the message structures to enable a consistent conversation id to be carried with the messages. - </para> - -<note> - <para> -The choreography description for the Trailblazer example can be found in the <emphasis>trailblazer-models</emphasis> project in the Eclipse environment. If the project has not yet been imported, then please refer to the instructions in the <emphasis>Getting Started Guide</emphasis>. - </para> - <para> -You can open the choreography for the trailblazer (trailblazer.cdm) and also a scenario representing a valid transaction associated with the choreography (LoanRequest.scn). In the choreography description editor, view the "Choreography Flows" tab to see the structure of the process. - </para> - <para> -To simulate the scenario against the choreography, to ensure that the choreography correctly caters for the valid business scenario, the user should press the green 'play' button in the toolbar, associated with the Scenario Editor. - </para> -</note> - - - <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. If the selected folders do not exist, then please ensure they are created prior to running the example. - </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> - <listitem> -From the <filename>trailblazer</filename> folder, execute the command to start 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> - <listitem> - <para> -In the Eclipse environment, select the popup menu associated with the <filename>trailblazer.cdm</filename> file, and choose the <emphasis>Choreography->Monitor</emphasis> menu item. - </para> - - <imageobject> - <imagedata fileref="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="images/ChoreoMonReady.jpg" align="center" width="4in" /> - </imageobject> - - </listitem> - <listitem> - <para> -Start a browser and enter the URL: <ulink url="http://localhost:8080/trailblazer">localhost:8080/trailblazer</ulink>. - </para> - - <imageobject> - <imagedata fileref="images/TrailblazerWebPage.jpg" align="center" width="4in" /> - </imageobject> - - </listitem> - <listitem> -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. - </listitem> - </orderedlist> - <para> -To demonstrate what occurs when the implementation deviates from the expected behaviour as defined in the choreography description, try the following steps: - </para> - <orderedlist> - <listitem> - Run the ant task <emphasis role="bold">ant deploy-error-client</emphasis> to redeploy the trailblaizer example. - </listitem> - <listitem> - Run the commands from step 6 above. - </listitem> - </orderedlist> - <para> - The above steps show how changing the service implementation without updating a choreography can result in behavioural validation errors being detected. - </para> - <tip> - <title>What is changed when we run ant deploy-error-client</title> - <para> - Compared to command of <emphasis role="bold">ant deploy</emphasis>, basically, we have just updated the following code in - <emphasis role="bold">$Overlord/samples/trailblazer/client/src/org/jboss/soa/esb/samples/trailblazer/loanbroker/LoanBroker.java</emphasis> file. - </para> - <para> - In the following code within the <emphasis role="bold">processLoanRequest</emphasis> method, we've changed the "4" to "7" - -<programlisting> - //step 2 - check if score is acceptable - if (score >= 4) { -</programlisting> - </para> - </tip> - - <para> - Issue further loan requests, remembering to change the quote reference each time, until a Credit Check result of between 4 and 6 inclusive occurs, which will result in an out of sequence message being reported (in red) to the Choreography Monitor - - <note> - <para> - It is currently a requirement that the choreography used within the Choreography Monitor is the same as the description used to locally monitor the services (i.e. within the overlord-cdl-validator.esb/models directory). - </para> - </note> - </para> - - </section> - -</chapter> Modified: validator/trunk/docs/samplesguide/src/main/module/overview.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/module/overview.xml 2009-11-25 22:14:32 UTC (rev 92) +++ validator/trunk/docs/samplesguide/src/main/module/overview.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -3,27 +3,22 @@ ]> <chapter id="overview"> <title>Overview</title> - <para>The Overlord CDL distribution contains two main types of functionality:</para> - <orderedlist> - <listitem> - the ability to validate executing services against a choreography description (an example of runtime governance). - </listitem> - <listitem> - the ability to build an ESB using 'conversation aware' actions which can be checked for conformance against a choreography description (an example of design time governance). - </listitem> - </orderedlist> - + <para>The SAVARA Validator component provides the ability to validate executing services + against a choreography description, demonstrating a form runtime governance. + </para> + <para> - This document will describe the samples available to demonstrate each aspect of the functionality. + Further information about configuring the runtime validation of services against a choreography + can be found in the <emphasis role="bold">SAVARA Validator User Guide</emphasis> and the + <emphasis role="bold">SAVARA Eclipse Tools User Guide</emphasis>. </para> - <para> - Further information about configuring the runtime validation of services against a choreography can be found in the <emphasis role="bold">UserGuide</emphasis>. - Information regarding the conversation aware ESB actions, and how to use them in conjunction with conformance checking against a choreography description, can also be found in the <emphasis role="bold">UserGuide</emphasis>. - </para> <note> <para> - Before attempting to install and run these examples, you must follow the instructions in the <emphasis role="bold">"Installation" Chapter</emphasis> of the <emphasis role="bold">Getting Started Guide</emphasis> regarding installing Overlord CDL into a JBossAS environment, and importing the samples into the Eclipse environment. + Before attempting to deploy and run these examples, you must follow the instructions + in the <filename>${SAVARA-Validator}/install</filename> folder. To be able to + examine and modify the examples, it is advisable to install the SAVARA Eclipse Tools, + and import the samples into the Eclipse environment. </para> </note> Copied: validator/trunk/docs/samplesguide/src/main/module/servicevalidator.xml (from rev 92, validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml) =================================================================== --- validator/trunk/docs/samplesguide/src/main/module/servicevalidator.xml (rev 0) +++ validator/trunk/docs/samplesguide/src/main/module/servicevalidator.xml 2009-11-26 21:24:56 UTC (rev 93) @@ -0,0 +1,171 @@ +<?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="servicevalidator"> + <title>Service Validator</title> + + <section> + <title>Trailblazer Example</title> + + <para> +This example can be found in the <filename>trailblazer</filename> folder. See the TrailBlazer Guide +(<filename>${SAVARA-Validator}/docs/samples/TBGuide.pdf</filename>) for more information about the example. + </para> + +<note> + <para> +The choreography description for the Trailblazer example can be found in the +<emphasis>trailblazer-models</emphasis> project in the Eclipse environment. If the project has +not yet been imported, then please refer to the instructions in the +<emphasis>SAVARA Eclipse Tools Getting Started Guide</emphasis>. + </para> + <para> +You can open the choreography for the trailblazer (trailblazer.cdm) and also a scenario representing +a valid transaction associated with the choreography (LoanRequest.scn). In the choreography description +editor, view the "Choreography Flows" tab to see the structure of the process. + </para> + <para> +To simulate the scenario against the choreography, to ensure that the choreography correctly caters +for the valid business scenario, the user should press the green 'play' button in the toolbar, associated +with the Scenario Editor. + </para> +</note> + + + <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. +If the selected folders do not exist, then please ensure they are created prior to running the example. + </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> + <listitem> +From the <filename>trailblazer</filename> folder, execute the command to start 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 File based +Bank service: <emphasis role="bold">ant runFileBank</emphasis>. + </listitem> + <listitem> + <para> +In the Eclipse environment, select the popup menu associated with the <filename>trailblazer.cdm</filename> +file, and choose the <emphasis>Choreography->Monitor</emphasis> menu item. + </para> + +<note> +<para> +TO BE UPDATED WITH JOPR APPROACH +</para> +</note> + <imageobject> + <imagedata fileref="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="images/ChoreoMonReady.jpg" align="center" width="4in" /> + </imageobject> + + </listitem> + <listitem> + <para> +Start a browser and enter the URL: +<ulink url="http://localhost:8080/trailblazer">localhost:8080/trailblazer</ulink>. + </para> + + <imageobject> + <imagedata fileref="images/TrailblazerWebPage.jpg" align="center" width="4in" /> + </imageobject> + + </listitem> + <listitem> +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. + </listitem> + </orderedlist> + <para> +To demonstrate what occurs when the implementation deviates from the expected behaviour as defined +in the choreography description, try the following steps: + </para> + <orderedlist> + <listitem> + Run the ant task <emphasis role="bold">ant deploy-error-client</emphasis> to redeploy the + trailblaizer example. + </listitem> + <listitem> + Run the commands from step 6 above. + </listitem> + </orderedlist> + <para> + The above steps show how changing the service implementation without updating a choreography + can result in behavioural validation errors being detected. + </para> + <tip> + <title>What is changed when we run ant deploy-error-client</title> + <para> + Compared to command of <emphasis role="bold">ant deploy</emphasis>, basically, we have + just updated the following code in + <emphasis role="bold">${SAVARA-Validator}/samples/trailblazer/client/src/org/jboss/soa/esb/samples/trailblazer/loanbroker/LoanBroker.java</emphasis> file. + </para> + <para> + In the following code within the <emphasis role="bold">processLoanRequest</emphasis> + method, we've changed the "4" to "7" + +<programlisting> + //step 2 - check if score is acceptable + if (score >= 4) { +</programlisting> + </para> + </tip> + + <para> + TO BE UPDATED WITH JOPR APPROACH: + Issue further loan requests, remembering to change the quote reference each time, until a Credit + Check result of between 4 and 6 inclusive occurs, which will result in an out of sequence message + being reported (in red) to the Choreography Monitor + + <note> + <para> + It is currently a requirement that the choreography used within the Choreography Monitor is + the same as the description used to locally monitor the services + (i.e. within the savara-validator-jbossesb.esb/models directory). + </para> + </note> + </para> + + </section> + +</chapter>

14 years, 4 months

1
0
0 / 0

savara SVN: r92 - runtime/trunk/docs/samplesguide and 13 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-25 17:14:32 -0500 (Wed, 25 Nov 2009) New Revision: 92 Added: runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml tools/eclipse/trunk/docs/userguide/src/main/module/bpel.xml tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation.xml validator/trunk/docs/pom.xml validator/trunk/docs/samplesguide/ validator/trunk/docs/samplesguide/pom.xml validator/trunk/docs/samplesguide/src/ validator/trunk/docs/samplesguide/src/main/ validator/trunk/docs/samplesguide/src/main/images/ validator/trunk/docs/samplesguide/src/main/images/ChoreoMonReady.jpg validator/trunk/docs/samplesguide/src/main/images/MonitorMenu.jpg validator/trunk/docs/samplesguide/src/main/images/TrailblazerWebPage.jpg validator/trunk/docs/samplesguide/src/main/master.xml validator/trunk/docs/samplesguide/src/main/module/ validator/trunk/docs/samplesguide/src/main/module/author_group.xml validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml validator/trunk/docs/samplesguide/src/main/module/overview.xml validator/trunk/docs/samplesguide/src/main/xslt/ validator/trunk/docs/samplesguide/src/main/xslt/pdf.xsl validator/trunk/pom.xml Removed: runtime/trunk/docs/samplesguide/src/main/module/cdlconformance.xml runtime/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml Modified: runtime/trunk/docs/samplesguide/pom.xml runtime/trunk/docs/samplesguide/src/main/master.xml runtime/trunk/pom.xml runtime/trunk/samples/jbossesb/brokerage/broker/pom.xml tools/eclipse/trunk/docs/userguide/src/main/master.xml Log: Further reorganisation of the documentation - still changes to make from overlord-cdl to savara. Modified: runtime/trunk/docs/samplesguide/pom.xml =================================================================== --- runtime/trunk/docs/samplesguide/pom.xml 2009-11-24 23:47:13 UTC (rev 91) +++ runtime/trunk/docs/samplesguide/pom.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -4,10 +4,10 @@ <modelVersion>4.0.0</modelVersion> - <groupId>org.jboss.savara.docs</groupId> + <groupId>org.jboss.savara.runtime.docs</groupId> <artifactId>samplesguide</artifactId> <packaging>jdocbook</packaging> - <name>Savara::Runtime::docs::samplesguide</name> + <name>Savara::Runtime::Docs::SamplesGuide</name> <parent> <groupId>org.jboss.savara.runtime</groupId> @@ -59,7 +59,7 @@ <format> <formatName>pdf</formatName> <stylesheetResource>file:///${basedir}/src/main/xslt/pdf.xsl</stylesheetResource> - <finalName>SamplesGuide.pdf</finalName> + <finalName>SAVARA-Runtime-SamplesGuide.pdf</finalName> </format> <format> <formatName>html</formatName> Modified: runtime/trunk/docs/samplesguide/src/main/master.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/master.xml 2009-11-24 23:47:13 UTC (rev 91) +++ runtime/trunk/docs/samplesguide/src/main/master.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -12,7 +12,6 @@ <toc/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/cdlvalidator.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/cdlconformance.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/convawareesb.xml"/> </book> Deleted: runtime/trunk/docs/samplesguide/src/main/module/cdlconformance.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/module/cdlconformance.xml 2009-11-24 23:47:13 UTC (rev 91) +++ runtime/trunk/docs/samplesguide/src/main/module/cdlconformance.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -1,192 +0,0 @@ -<?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="cdlconformance"> - <title>CDL Conformance</title> - - <para> -There are two examples to demonstrate the conversation aware ESB actions(for both stateful and stateless), and the conformance checking against a choreography. - </para> - <para> -These are <filename>purchasing</filename>, a simple customer/supplier example with two associated Eclipse projects (<filename>purchasing-store-stateful/less</filename> and <filename>purchasing-models</filename>), and <filename>brokerage</filename> which extends the purchasing example through the introduction of a broker that mediates between potentially multiple suppliers to find the best deal, defined within three Eclipse projects (<filename>brokerage-broker-stateful/less</filename>, <filename>brokerage-supplier-stateful/less</filename> and <filename>brokerage-models</filename>). - </para> - <para> -These examples make use of a common <emphasis>Credit Agency</emphasis> service, defined within the <filename>common-creditAgency-stateful/less</filename> Eclipse project, and are executed through the use of client applications defined in the <filename>${OverlordCDL}/samples/client</filename> folder. - </para> - - <warning> - At the moment, the conversation aware ESB runtime doesn't support the hot-deploy. That means if you update the business pojo class, such as <emphasis role="bold">$creditAgency/src/main/com/acme/services/creditAgency/CreditAgencyPurchase.java</emphasis> file, - You need to re-deploy it, and then <emphasis role="bold">restart the server </emphasis> to cause it to take effect. This issue has been tracked under <ulink url="https://jira.jboss.org/jira/browse/SOAG-72">https://jira.jboss.org/jira/browse/SOAG-72</ulink>. Will be fixed in the next release. - </warning> - - <section> - <title>Purchasing Example</title> - <section> - <title>Overview</title> - <para> -The purchasing example describes the interactions between a Buyer, Store and Credit Agency. The flow for this example would be: - </para> - <itemizedlist> - <listitem> -Buyer send a 'buy' request to Store - </listitem> - <listitem> -Store send a 'credit check' request to the Credit Agency. - </listitem> - <listitem> -If the Credit Agency returns a successful message, then the Store will send a 'BuyConfirmed' to user. - </listitem> - <listitem> -If the Credit Agency returns a failed message, then the Store will send a 'BuyFailed' to user. - </listitem> - </itemizedlist> - - <para> -To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>purchasing-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. - </para> - <para> -To provide a simple demonstration of the conformance checking: - </para> - <orderedlist> - <listitem> -Double click on <filename>purchasing-store[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> - </listitem> - <listitem> -Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. - </listitem> - <listitem> -Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. - </listitem> - <listitem> -Then save the file. This should result in an error being generated, complaining about a type mismatch. - </listitem> - </orderedlist> - <para> -The information regarding the expected message type is obtained from the choreography description in the <filename>purchasing-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. - </para> - <para> -Another Quick Fix option associated with this error is <emphasis>Update from Referenced Description</emphasis>. By selecting this option, you will notice that the message type is changed back to the value without the 'X'. - </para> - </section> - - <section> - <title>Running the Example</title> - <para> - This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. - One is the stateful purchasing example (this is the example that we had since M1 release),the other is stateless purchasing example that is introduced in the M2 release. - </para> - <orderedlist> - <listitem> - First step is to install the ESB services. (Presumely the JBoss ESB server started already) - In a command window, Go to the the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/sample/stateless</filename> in the stateless approach), execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. - </listitem> - <listitem> - Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runPurchasingClient</emphasis> (or <emphasis role="bold"> ant runStatelessPurchasingClient</emphasis> in stateless approach.), which will send a 'BuyRequest' message to the Store, which will then perform the credit check before returning a response to the client. - </listitem> - </orderedlist> - - <para> -To see a different response from the client, change the <emphasis>isCreditValid</emphasis> method on the <emphasis>CreditAgencyPurchase</emphasis> class to return <emphasis>false</emphasis>, within the <filename>common/creditAgency</filename> ESB service implementation, and then re-deploy the Credit Agency service. Then when the client is re-run, a 'BuyFailed' message will be returned. - </para> - - <tip> - <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-purchasing</command> in the <filename>$Overlord/samples/stateful</filename> folder or <filename>$Overlord/samples/stateless</filename> folder respectively.</para> - </tip> - - </section> - - </section> - - <section> - <title>Brokerage Example</title> - - <section> - <title>Overview</title> - - <para> -The brokerage example describes the interactions between a Customer, Broker, Supplier and Credit Agency. The flow for this example would be: - </para> - - <itemizedlist> - <listitem> -Customer sends an 'enquiry' request to Broker - </listitem> - <listitem> -Broker sends the request to one or more Suppliers concurrently - </listitem> - <listitem> -When all of the quote responses have been received, or a timeout expires, the available information is returned to the Customer - </listitem> - <listitem> -Customer decides whether to: - <itemizedlist> - <listitem> - Cancel the transaction, or - </listitem> - <listitem> - Send a 'buy' request to the Broker - </listitem> - </itemizedlist> - </listitem> - <listitem> -If a 'buy' request is received by the Broker, it will send a 'credit check' request to the Credit Agency - </listitem> - <listitem> -If the Credit Agency returns a successful message, then the Broker sends a 'buy' request to the Supplier selected by the Customer (in the 'buy' request), followed by a confirmation back to the Customer - </listitem> - <listitem> -If the Credit Agency returns a failed message, then the Broker will inform the Customer - </listitem> - </itemizedlist> - - <para> -To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. - </para> - <para> -To provide a simple demonstration of the conformance checking: - </para> - <orderedlist> - <listitem> -Double click on <filename>brokerage-broker[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> - </listitem> - <listitem> -Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. - </listitem> - <listitem> -Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. - </listitem> - <listitem> -Then save the file. This should result in an error being generated, complaining about a type mismatch. - </listitem> - </orderedlist> - <para> -The information regarding the expected message type is obtained from the choreography description in the <filename>brokerage-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. - </para> - </section> - - <section> - <title>Running the Example</title> - <para> - This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. - one is the sateful broker example (this is the example that we had since M1 release), the other is stateless broker example that is introduced in the M2 release. - </para> - <orderedlist> - <listitem> - First step is to install the ESB services (Presumely the JBoss ESB server started already) - In a command window, Go to the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/samples/stateless</filename> in the stateless approach), execute <emphasis role="bold">ant deploy-broker</emphasis> - </listitem> - <listitem> - Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runBrokerageClient</emphasis> (or <emphasis role="bold"> ant runStatelessBrokerageClient</emphasis> in stateless approach), which will initially send an 'enquiry' message to the Broker, which will communicate with the set of Suppliers to obtain the best quote. The client will then send a 'buy' request, which will result in the Broker performing a credit check before returning a response to the client. - </listitem> - </orderedlist> - - <tip> - <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-broker</command> in $Overlord/samples/stateful or $Overlord/samples/stateless respectively.</para> - </tip> - </section> - - </section> - -</chapter> Deleted: runtime/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml =================================================================== --- runtime/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml 2009-11-24 23:47:13 UTC (rev 91) +++ runtime/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -1,132 +0,0 @@ -<?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="cdlvalidator"> - <title>CDL Validator</title> - - <section> - <title>Trailblazer Example</title> - - <para> -This example can be found in the <filename>trailblazer</filename> folder, which contains an enhanced version of the trailblazer example found in the JBossESB distribution. See the TrailBlazer Guide in the JBossESB distribution (<filename>$JBossESB/docs/samples/TBGuide.pdf</filename>) for more information about the example. The main changes are the introduction of a File Based Bank, and modifications to the message structures to enable a consistent conversation id to be carried with the messages. - </para> - -<note> - <para> -The choreography description for the Trailblazer example can be found in the <emphasis>trailblazer-models</emphasis> project in the Eclipse environment. If the project has not yet been imported, then please refer to the instructions in the <emphasis>Getting Started Guide</emphasis>. - </para> - <para> -You can open the choreography for the trailblazer (trailblazer.cdm) and also a scenario representing a valid transaction associated with the choreography (LoanRequest.scn). In the choreography description editor, view the "Choreography Flows" tab to see the structure of the process. - </para> - <para> -To simulate the scenario against the choreography, to ensure that the choreography correctly caters for the valid business scenario, the user should press the green 'play' button in the toolbar, associated with the Scenario Editor. - </para> -</note> - - - <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. If the selected folders do not exist, then please ensure they are created prior to running the example. - </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> - <listitem> -From the <filename>trailblazer</filename> folder, execute the command to start 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> - <listitem> - <para> -In the Eclipse environment, select the popup menu associated with the <filename>trailblazer.cdm</filename> file, and choose the <emphasis>Choreography->Monitor</emphasis> menu item. - </para> - - <imageobject> - <imagedata fileref="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="images/ChoreoMonReady.jpg" align="center" width="4in" /> - </imageobject> - - </listitem> - <listitem> - <para> -Start a browser and enter the URL: <ulink url="http://localhost:8080/trailblazer">localhost:8080/trailblazer</ulink>. - </para> - - <imageobject> - <imagedata fileref="images/TrailblazerWebPage.jpg" align="center" width="4in" /> - </imageobject> - - </listitem> - <listitem> -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. - </listitem> - </orderedlist> - <para> -To demonstrate what occurs when the implementation deviates from the expected behaviour as defined in the choreography description, try the following steps: - </para> - <orderedlist> - <listitem> - Run the ant task <emphasis role="bold">ant deploy-error-client</emphasis> to redeploy the trailblaizer example. - </listitem> - <listitem> - Run the commands from step 6 above. - </listitem> - </orderedlist> - <para> - The above steps show how changing the service implementation without updating a choreography can result in behavioural validation errors being detected. - </para> - <tip> - <title>What is changed when we run ant deploy-error-client</title> - <para> - Compared to command of <emphasis role="bold">ant deploy</emphasis>, basically, we have just updated the following code in - <emphasis role="bold">$Overlord/samples/trailblazer/client/src/org/jboss/soa/esb/samples/trailblazer/loanbroker/LoanBroker.java</emphasis> file. - </para> - <para> - In the following code within the <emphasis role="bold">processLoanRequest</emphasis> method, we've changed the "4" to "7" - -<programlisting> - //step 2 - check if score is acceptable - if (score >= 4) { -</programlisting> - </para> - </tip> - - <para> - Issue further loan requests, remembering to change the quote reference each time, until a Credit Check result of between 4 and 6 inclusive occurs, which will result in an out of sequence message being reported (in red) to the Choreography Monitor - - <note> - <para> - It is currently a requirement that the choreography used within the Choreography Monitor is the same as the description used to locally monitor the services (i.e. within the overlord-cdl-validator.esb/models directory). - </para> - </note> - </para> - - </section> - -</chapter> Copied: runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml (from rev 91, runtime/trunk/docs/samplesguide/src/main/module/cdlconformance.xml) =================================================================== --- runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml (rev 0) +++ runtime/trunk/docs/samplesguide/src/main/module/convawareesb.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,192 @@ +<?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="convawareesb"> + <title>"Conversation Aware" ESB Services</title> + + <para> +There are two examples to demonstrate the conversation aware ESB actions(for both stateful and stateless), and the conformance checking against a choreography. + </para> + <para> +These are <filename>purchasing</filename>, a simple customer/supplier example with two associated Eclipse projects (<filename>purchasing-store-stateful/less</filename> and <filename>purchasing-models</filename>), and <filename>brokerage</filename> which extends the purchasing example through the introduction of a broker that mediates between potentially multiple suppliers to find the best deal, defined within three Eclipse projects (<filename>brokerage-broker-stateful/less</filename>, <filename>brokerage-supplier-stateful/less</filename> and <filename>brokerage-models</filename>). + </para> + <para> +These examples make use of a common <emphasis>Credit Agency</emphasis> service, defined within the <filename>common-creditAgency-stateful/less</filename> Eclipse project, and are executed through the use of client applications defined in the <filename>${OverlordCDL}/samples/client</filename> folder. + </para> + + <warning> + At the moment, the conversation aware ESB runtime doesn't support the hot-deploy. That means if you update the business pojo class, such as <emphasis role="bold">$creditAgency/src/main/com/acme/services/creditAgency/CreditAgencyPurchase.java</emphasis> file, + You need to re-deploy it, and then <emphasis role="bold">restart the server </emphasis> to cause it to take effect. This issue has been tracked under <ulink url="https://jira.jboss.org/jira/browse/SOAG-72">https://jira.jboss.org/jira/browse/SOAG-72</ulink>. Will be fixed in the next release. + </warning> + + <section> + <title>Purchasing Example</title> + <section> + <title>Overview</title> + <para> +The purchasing example describes the interactions between a Buyer, Store and Credit Agency. The flow for this example would be: + </para> + <itemizedlist> + <listitem> +Buyer send a 'buy' request to Store + </listitem> + <listitem> +Store send a 'credit check' request to the Credit Agency. + </listitem> + <listitem> +If the Credit Agency returns a successful message, then the Store will send a 'BuyConfirmed' to user. + </listitem> + <listitem> +If the Credit Agency returns a failed message, then the Store will send a 'BuyFailed' to user. + </listitem> + </itemizedlist> + + <para> +To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. +The <filename>purchasing-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. + </para> + <para> +To provide a simple demonstration of the conformance checking: + </para> + <orderedlist> + <listitem> +Double click on <filename>purchasing-store[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> + </listitem> + <listitem> +Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. + </listitem> + <listitem> +Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. + </listitem> + <listitem> +Then save the file. This should result in an error being generated, complaining about a type mismatch. + </listitem> + </orderedlist> + <para> +The information regarding the expected message type is obtained from the choreography description in the <filename>purchasing-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. + </para> + <para> +Another Quick Fix option associated with this error is <emphasis>Update from Referenced Description</emphasis>. By selecting this option, you will notice that the message type is changed back to the value without the 'X'. + </para> + </section> + + <section> + <title>Running the Example</title> + <para> + This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. + One is the stateful purchasing example (this is the example that we had since M1 release),the other is stateless purchasing example that is introduced in the M2 release. + </para> + <orderedlist> + <listitem> + First step is to install the ESB services. (Presumely the JBoss ESB server started already) + In a command window, Go to the the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/sample/stateless</filename> in the stateless approach), execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. + </listitem> + <listitem> + Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runPurchasingClient</emphasis> (or <emphasis role="bold"> ant runStatelessPurchasingClient</emphasis> in stateless approach.), which will send a 'BuyRequest' message to the Store, which will then perform the credit check before returning a response to the client. + </listitem> + </orderedlist> + + <para> +To see a different response from the client, change the <emphasis>isCreditValid</emphasis> method on the <emphasis>CreditAgencyPurchase</emphasis> class to return <emphasis>false</emphasis>, within the <filename>common/creditAgency</filename> ESB service implementation, and then re-deploy the Credit Agency service. Then when the client is re-run, a 'BuyFailed' message will be returned. + </para> + + <tip> + <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-purchasing</command> in the <filename>$Overlord/samples/stateful</filename> folder or <filename>$Overlord/samples/stateless</filename> folder respectively.</para> + </tip> + + </section> + + </section> + + <section> + <title>Brokerage Example</title> + + <section> + <title>Overview</title> + + <para> +The brokerage example describes the interactions between a Customer, Broker, Supplier and Credit Agency. The flow for this example would be: + </para> + + <itemizedlist> + <listitem> +Customer sends an 'enquiry' request to Broker + </listitem> + <listitem> +Broker sends the request to one or more Suppliers concurrently + </listitem> + <listitem> +When all of the quote responses have been received, or a timeout expires, the available information is returned to the Customer + </listitem> + <listitem> +Customer decides whether to: + <itemizedlist> + <listitem> + Cancel the transaction, or + </listitem> + <listitem> + Send a 'buy' request to the Broker + </listitem> + </itemizedlist> + </listitem> + <listitem> +If a 'buy' request is received by the Broker, it will send a 'credit check' request to the Credit Agency + </listitem> + <listitem> +If the Credit Agency returns a successful message, then the Broker sends a 'buy' request to the Supplier selected by the Customer (in the 'buy' request), followed by a confirmation back to the Customer + </listitem> + <listitem> +If the Credit Agency returns a failed message, then the Broker will inform the Customer + </listitem> + </itemizedlist> + + <para> +To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. +The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. + </para> + <para> +To provide a simple demonstration of the conformance checking: + </para> + <orderedlist> + <listitem> +Double click on <filename>brokerage-broker[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> + </listitem> + <listitem> +Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. + </listitem> + <listitem> +Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. + </listitem> + <listitem> +Then save the file. This should result in an error being generated, complaining about a type mismatch. + </listitem> + </orderedlist> + <para> +The information regarding the expected message type is obtained from the choreography description in the <filename>brokerage-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. + </para> + </section> + + <section> + <title>Running the Example</title> + <para> + This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. + one is the sateful broker example (this is the example that we had since M1 release), the other is stateless broker example that is introduced in the M2 release. + </para> + <orderedlist> + <listitem> + First step is to install the ESB services (Presumely the JBoss ESB server started already) + In a command window, Go to the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/samples/stateless</filename> in the stateless approach), execute <emphasis role="bold">ant deploy-broker</emphasis> + </listitem> + <listitem> + Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runBrokerageClient</emphasis> (or <emphasis role="bold"> ant runStatelessBrokerageClient</emphasis> in stateless approach), which will initially send an 'enquiry' message to the Broker, which will communicate with the set of Suppliers to obtain the best quote. The client will then send a 'buy' request, which will result in the Broker performing a credit check before returning a response to the client. + </listitem> + </orderedlist> + + <tip> + <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-broker</command> in $Overlord/samples/stateful or $Overlord/samples/stateless respectively.</para> + </tip> + </section> + + </section> + +</chapter> Modified: runtime/trunk/pom.xml =================================================================== --- runtime/trunk/pom.xml 2009-11-24 23:47:13 UTC (rev 91) +++ runtime/trunk/pom.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -6,7 +6,7 @@ <artifactId>runtime</artifactId> <version>1.0-SNAPSHOT</version> <packaging>pom</packaging> - <name>Savara Runtime</name> + <name>Savara::Runtime</name> <url>http://www.jboss.org/savara</url> <description> The JBoss SAVARA Runtime. Modified: runtime/trunk/samples/jbossesb/brokerage/broker/pom.xml =================================================================== --- runtime/trunk/samples/jbossesb/brokerage/broker/pom.xml 2009-11-24 23:47:13 UTC (rev 91) +++ runtime/trunk/samples/jbossesb/brokerage/broker/pom.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -5,7 +5,7 @@ <groupId>org.jboss.savara.runtime.samples</groupId> <artifactId>samples-broker</artifactId> <packaging>jar</packaging> - <name>Savara::Samples::Broker</name> + <name>Savara::Runtime::Samples::Broker</name> <parent> <groupId>org.jboss.savara.runtime</groupId> Modified: tools/eclipse/trunk/docs/userguide/src/main/master.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/master.xml 2009-11-24 23:47:13 UTC (rev 91) +++ tools/eclipse/trunk/docs/userguide/src/main/master.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -12,9 +12,8 @@ <toc/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/bpel-governance.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/cdlconformance.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/bpel.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/conversation-aware-esb.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/conversation-validation-with-cdl.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/conversation-validation.xml"/> </book> Deleted: tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml 2009-11-24 23:47:13 UTC (rev 91) +++ tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -1,71 +0,0 @@ -<?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="bpelgovernance"> - <title>BPEL Governance</title> - - <section> - <title>Overview</title> - <para> -This section will describe governance features related to WS-BPEL. This initial release provides basic support for generating BPEL processes from a choreography description. Subsequent releases will also provide conformance checking, to ensure that changes to a BPEL process are validated to ensure the process remains conformant with the choreography. - </para> - </section> - - <section> - <title>Generating a BPEL process from CDL</title> - <section> - <title>Overview</title> - <para> -This section explains how to generate a template BPEL process from a pi4soa choreography description (.cdm) file. - </para> - </section> - <section> - <title>Generating the BPEL Process</title> - <para> -When the choreography description has been completed, and has no errors, the user should select the "Overlord->Generate->WS-BPEL" menu item from the popup menu associated with the choreography description (.cdm) file. - </para> - - <imageobject> - <imagedata fileref="images/genbpel1.png" width="4in" /> - </imageobject> - - <para> -When the dialog window is displayed, it will contain the list of services that can be generated, along with the project names that will be created. The user can unselect the services they do not wish to generate (also using the 'Check All' or 'Clear All' buttons). - </para> - - <imageobject> - <imagedata fileref="images/genbpel2.png" /> - </imageobject> - - <para> -The user can also select their preferred build system, which will create the relevant build structure. - </para> - <para> -If there is a problem with the name of the project select, such as invalid characters used in the name, or the project name already exists, then it will be displayed in red. - </para> - - <para> -Once the BPEL is generated, it can be viewed using the Eclipse BPEL editor, e.g. - </para> - - <imageobject> - <imagedata fileref="images/genbpel3.png" /> - </imageobject> - - </section> - - <section> - <title>Limitations with the current CDL to BPEL mapping</title> - - <para> -This initial version of the BPEL generation is primarily targeted at generating the interactions and grouping constructs. These are the important components that will be required when doing conformance checking as part of the next milestone. - </para> - - <para> -This means that assignments and conditional expressions are not currently generated. The 'when' construct in CDL (also known as the blocking workunit) is also not currently handled. This may possible be implemented using flow links. - </para> - </section> - </section> - -</chapter> - Copied: tools/eclipse/trunk/docs/userguide/src/main/module/bpel.xml (from rev 91, tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml) =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/bpel.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/bpel.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,87 @@ +<?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="bpel"> + <title>BPEL</title> + + <section> + <title>Overview</title> + <para> +This section will describe generation and conformance checking features related to WS-BPEL. + </para> + + <para> +This initial release provides basic support for generating BPEL processes from a choreography +description. Subsequent releases will also provide conformance checking, to ensure that changes +to a BPEL process are validated to ensure the process remains conformant with the choreography. + </para> + </section> + + <section> + <title>Generating a BPEL process</title> + <section> + <title>Overview</title> + <para> +This section explains how to generate a template BPEL process from architectural and design +artifacts. + </para> + </section> + <section> + <title>Generating the BPEL Process from a Choreography Description</title> + <para> +When the choreography description has been completed, and has no errors, the user should select +the "SAVARA->Generate->WS-BPEL" menu item from the popup menu associated with the choreography +description (.cdm) file. + </para> + + <imageobject> + <imagedata fileref="images/genbpel1.png" width="4in" /> + </imageobject> + + <para> +When the dialog window is displayed, it will contain the list of services that can be generated, +along with the project names that will be created. The user can unselect the services they do not +wish to generate (also using the 'Check All' or 'Clear All' buttons). + </para> + + <imageobject> + <imagedata fileref="images/genbpel2.png" /> + </imageobject> + + <para> +The user can also select their preferred build system, which will create the relevant build structure. + </para> + <para> +If there is a problem with the name of the project select, such as invalid characters used in the name, +or the project name already exists, then it will be displayed in red. + </para> + + <para> +Once the BPEL is generated, it can be viewed using the Eclipse BPEL editor, e.g. + </para> + + <imageobject> + <imagedata fileref="images/genbpel3.png" /> + </imageobject> + + </section> + + <section> + <title>Limitations with the current CDL to BPEL mapping</title> + + <para> +This initial version of the BPEL generation is primarily targeted at generating the interactions +and grouping constructs. These are the important components that will be required when doing +conformance checking as part of the next milestone. + </para> + + <para> +This means that assignments and conditional expressions are not currently generated. The 'when' +construct in CDL (also known as the blocking workunit) is also not currently handled. This may possible +be implemented using flow links. + </para> + </section> + </section> + +</chapter> + Deleted: tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml 2009-11-24 23:47:13 UTC (rev 91) +++ tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -1,192 +0,0 @@ -<?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="cdlconformance"> - <title>CDL Conformance</title> - - <para> -There are two examples to demonstrate the conversation aware ESB actions(for both stateful and stateless), and the conformance checking against a choreography. - </para> - <para> -These are <filename>purchasing</filename>, a simple customer/supplier example with two associated Eclipse projects (<filename>purchasing-store-stateful/less</filename> and <filename>purchasing-models</filename>), and <filename>brokerage</filename> which extends the purchasing example through the introduction of a broker that mediates between potentially multiple suppliers to find the best deal, defined within three Eclipse projects (<filename>brokerage-broker-stateful/less</filename>, <filename>brokerage-supplier-stateful/less</filename> and <filename>brokerage-models</filename>). - </para> - <para> -These examples make use of a common <emphasis>Credit Agency</emphasis> service, defined within the <filename>common-creditAgency-stateful/less</filename> Eclipse project, and are executed through the use of client applications defined in the <filename>${OverlordCDL}/samples/client</filename> folder. - </para> - - <warning> - At the moment, the conversation aware ESB runtime doesn't support the hot-deploy. That means if you update the business pojo class, such as <emphasis role="bold">$creditAgency/src/main/com/acme/services/creditAgency/CreditAgencyPurchase.java</emphasis> file, - You need to re-deploy it, and then <emphasis role="bold">restart the server </emphasis> to cause it to take effect. This issue has been tracked under <ulink url="https://jira.jboss.org/jira/browse/SOAG-72">https://jira.jboss.org/jira/browse/SOAG-72</ulink>. Will be fixed in the next release. - </warning> - - <section> - <title>Purchasing Example</title> - <section> - <title>Overview</title> - <para> -The purchasing example describes the interactions between a Buyer, Store and Credit Agency. The flow for this example would be: - </para> - <itemizedlist> - <listitem> -Buyer send a 'buy' request to Store - </listitem> - <listitem> -Store send a 'credit check' request to the Credit Agency. - </listitem> - <listitem> -If the Credit Agency returns a successful message, then the Store will send a 'BuyConfirmed' to user. - </listitem> - <listitem> -If the Credit Agency returns a failed message, then the Store will send a 'BuyFailed' to user. - </listitem> - </itemizedlist> - - <para> -To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>purchasing-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. - </para> - <para> -To provide a simple demonstration of the conformance checking: - </para> - <orderedlist> - <listitem> -Double click on <filename>purchasing-store[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> - </listitem> - <listitem> -Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. - </listitem> - <listitem> -Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. - </listitem> - <listitem> -Then save the file. This should result in an error being generated, complaining about a type mismatch. - </listitem> - </orderedlist> - <para> -The information regarding the expected message type is obtained from the choreography description in the <filename>purchasing-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. - </para> - <para> -Another Quick Fix option associated with this error is <emphasis>Update from Referenced Description</emphasis>. By selecting this option, you will notice that the message type is changed back to the value without the 'X'. - </para> - </section> - - <section> - <title>Running the Example</title> - <para> - This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. - One is the stateful purchasing example (this is the example that we had since M1 release),the other is stateless purchasing example that is introduced in the M2 release. - </para> - <orderedlist> - <listitem> - First step is to install the ESB services. (Presumely the JBoss ESB server started already) - In a command window, Go to the the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/sample/stateless</filename> in the stateless approach), execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. - </listitem> - <listitem> - Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runPurchasingClient</emphasis> (or <emphasis role="bold"> ant runStatelessPurchasingClient</emphasis> in stateless approach.), which will send a 'BuyRequest' message to the Store, which will then perform the credit check before returning a response to the client. - </listitem> - </orderedlist> - - <para> -To see a different response from the client, change the <emphasis>isCreditValid</emphasis> method on the <emphasis>CreditAgencyPurchase</emphasis> class to return <emphasis>false</emphasis>, within the <filename>common/creditAgency</filename> ESB service implementation, and then re-deploy the Credit Agency service. Then when the client is re-run, a 'BuyFailed' message will be returned. - </para> - - <tip> - <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-purchasing</command> in the <filename>$Overlord/samples/stateful</filename> folder or <filename>$Overlord/samples/stateless</filename> folder respectively.</para> - </tip> - - </section> - - </section> - - <section> - <title>Brokerage Example</title> - - <section> - <title>Overview</title> - - <para> -The brokerage example describes the interactions between a Customer, Broker, Supplier and Credit Agency. The flow for this example would be: - </para> - - <itemizedlist> - <listitem> -Customer sends an 'enquiry' request to Broker - </listitem> - <listitem> -Broker sends the request to one or more Suppliers concurrently - </listitem> - <listitem> -When all of the quote responses have been received, or a timeout expires, the available information is returned to the Customer - </listitem> - <listitem> -Customer decides whether to: - <itemizedlist> - <listitem> - Cancel the transaction, or - </listitem> - <listitem> - Send a 'buy' request to the Broker - </listitem> - </itemizedlist> - </listitem> - <listitem> -If a 'buy' request is received by the Broker, it will send a 'credit check' request to the Credit Agency - </listitem> - <listitem> -If the Credit Agency returns a successful message, then the Broker sends a 'buy' request to the Supplier selected by the Customer (in the 'buy' request), followed by a confirmation back to the Customer - </listitem> - <listitem> -If the Credit Agency returns a failed message, then the Broker will inform the Customer - </listitem> - </itemizedlist> - - <para> -To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. -The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. - </para> - <para> -To provide a simple demonstration of the conformance checking: - </para> - <orderedlist> - <listitem> -Double click on <filename>brokerage-broker[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> - </listitem> - <listitem> -Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. - </listitem> - <listitem> -Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. - </listitem> - <listitem> -Then save the file. This should result in an error being generated, complaining about a type mismatch. - </listitem> - </orderedlist> - <para> -The information regarding the expected message type is obtained from the choreography description in the <filename>brokerage-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. - </para> - </section> - - <section> - <title>Running the Example</title> - <para> - This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. - one is the sateful broker example (this is the example that we had since M1 release), the other is stateless broker example that is introduced in the M2 release. - </para> - <orderedlist> - <listitem> - First step is to install the ESB services (Presumely the JBoss ESB server started already) - In a command window, Go to the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/samples/stateless</filename> in the stateless approach), execute <emphasis role="bold">ant deploy-broker</emphasis> - </listitem> - <listitem> - Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runBrokerageClient</emphasis> (or <emphasis role="bold"> ant runStatelessBrokerageClient</emphasis> in stateless approach), which will initially send an 'enquiry' message to the Broker, which will communicate with the set of Suppliers to obtain the best quote. The client will then send a 'buy' request, which will result in the Broker performing a credit check before returning a response to the client. - </listitem> - </orderedlist> - - <tip> - <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-broker</command> in $Overlord/samples/stateful or $Overlord/samples/stateless respectively.</para> - </tip> - </section> - - </section> - -</chapter> Deleted: tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml 2009-11-24 23:47:13 UTC (rev 91) +++ tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -1,301 +0,0 @@ -<?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="conversationvalidationwithcdl"> - <title>Conversation Validation with CDL</title> - <section> - <title>Overview</title> - <para> -Conversation validation is a form of runtime governance concerned with the dynamic behaviour of a system. - </para> - <para> -When coupled with a choreography description model of a system, this means having the ability to ensure that the way a collection of services interact correctly adheres to a description of the business process being enacted. - </para> - <para> -This section introduces the choreography description language (CDL) defined by W3C, and the <emphasis>pi4soa</emphasis> open source project which provides an editor for creating choreography descriptions, as well as utilizing these descriptions for runtime validation and execution purposes. - - </para> - - </section> - - <section> - <title>Configuration of Conversation Validation</title> - - <para> - This section explains how to configure the conversation validation mechanism to validate ESB 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 - 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.soa.overlord.validator.jbossesb.ValidatorFilter"/> - </properties> - ]]></programlisting> - </informalexample> - - <para> -This filter is installed as part of the installation process for the Overlord-CDL distribution. - </para> - </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>overlord-cdl-validator.esb</emphasis> bundle. - </para> - <para> -An example of the contents of this file, that would related to the TrailBlazer example, is: - </para> - <informalexample> - <programlisting role="XML" ><![CDATA[ - <validator mode="monitor" replyToTimeout="10000" > - <service model="TrailBlazer.cdm" - role="LoanBrokerParticipant" > - <output epr="jms:queue/esb-tb-creditAgencyQueue" /> - <input epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> - <output epr="jms:queue/esb-tb-jmsBankRequestQueue" /> - <output epr="jms:queue/esb-tb-fileBankRequestQueue" /> - <input epr="jms:queue/esb-tb-jmsBankResponseQueue" /> - <output epr="jms:queue/esb-tb-customerNotifier" /> - <input epr="jms:queue/esb-tb-fileBankResponseQueue" /> - </service> - <service model="TrailBlazer.cdm" - role="CreditAgencyParticipant" > - <input epr="jms:queue/esb-tb-creditAgencyQueue" /> - <output epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> - </service> - <service model="TrailBlazer.cdm" - role="BankParticipant" > - <input epr="jms:queue/esb-tb-jmsBankRequestQueue" /> - <input epr="jms:queue/esb-tb-fileBankRequestQueue" /> - <output epr="jms:queue/esb-tb-jmsBankResponseQueue" /> - <output epr="jms:queue/esb-tb-fileBankResponseQueue" /> - </service> - <service model="TrailBlazer.cdm" - role="NotifierParticipant" > - <input epr="jms:queue/esb-tb-customerNotifier" /> - </service> - </validator> - ]]></programlisting> - </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. - </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. - </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. - </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>overlord-cdl-validator.esb</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. - </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:'. - </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. - </para> - - </section> - - <section> - <title>Defining the Validator Configuration within a Choreography</title> - - <para> - The first step to configuring the validator is to associate the endpoint references (EPRs) - against the relevant choreography interactions. This is achieved by defining an - annotation for each 'exchange details' component (i.e. each request and response/notification). - </para> - - <imageobject> - <imagedata fileref="images/editvalidatorann.png" width="5in" /> - </imageobject> - - <para> - When the annotation editor is displayed for the relevant 'exchange details' component, - the <emphasis>jbossesb</emphasis> annotation should be added. This is achieved by - selecting the popup menu associated with the background of the lefthand panel, - and selecting the <emphasis>Add Defined Annotation</emphasis> menu item. - </para> - - <imageobject> - <imagedata fileref="images/editvalidatoranndiag.png" width="5in" /> - </imageobject> - - <para> - When the list of defined annotations is displayed, select the - <emphasis>jbossesb</emphasis> annotation. - </para> - - <imageobject> - <imagedata fileref="images/editvalidatorannselect.png" width="3in" /> - </imageobject> - - <para> - After pressing the <emphasis>Ok</emphasis> button, the annotation editor - will configure the righthand panel with the parameters associated with this - annotation. - </para> - - <imageobject> - <imagedata fileref="images/SVJBossESBAnnotation.jpg" width="5in" /> - </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 - 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. - </para> - - <para> - Once the annotation has been defined, then press the <emphasis>Save</emphasis> - button to save the annotation against the interaction's exchange details. - </para> - - <para> - When all of the relevant 'exchange details' components have been configured with - a <emphasis>jbossesb</emphasis> annotation, defining the EPR to be validated, - then the choreography description file can be copied into the - <filename>overlord-cdl-validator.esb/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. - </para> - - </section> - - </section> - - <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> -The destination defined in this file must match the one configured in the <emphasis>pi4soa.sar/pi4soa.xml</emphasis> file within the server. -</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 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. - </para> - - <imageobject> - <imagedata fileref="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. - </para> - <para> -If any <emphasis>out of sequence</emphasis> or other error situations arise, these are displayed in red. - </para> - </section> - - <section> - <title>Configuration for Conversation Recording</title> - - <para> - As well as validating the interactions between a set of - services, against a pre-defined choreography description, - it is also possible to use the <emphasis>Service Validators</emphasis> - in a non-validating record mode. - </para> - - <para> - This will be useful in situations where a choreography - description does not currently exist, and we wish to - use the stream of business events being sent and received - by each identified service (or participant type) to - gain an understanding of the current business process. - </para> - - <para> - An example of this type of configuration, associated - with the TrailBlazer example, is: - </para> - <informalexample> - <programlisting role="XML" ><![CDATA[ - <validator> - <service role="LoanBrokerParticipant" validate="false" > - <output epr="jms:queue/esb-tb-creditAgencyQueue" /> - <input epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> - <output epr="jms:queue/esb-tb-jmsBankRequestQueue" /> - <output epr="jms:queue/esb-tb-fileBankRequestQueue" /> - <input epr="jms:queue/esb-tb-jmsBankResponseQueue" /> - <output epr="jms:queue/esb-tb-customerNotifier" /> - <input epr="jms:queue/esb-tb-fileBankResponseQueue" /> - </service> - <service role="CreditAgencyParticipant" validate="false" > - <input epr="jms:queue/esb-tb-creditAgencyQueue" /> - <output epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> - </service> - <service role="BankParticipant" validate="false" > - <input epr="jms:queue/esb-tb-jmsBankRequestQueue" /> - <input epr="jms:queue/esb-tb-fileBankRequestQueue" /> - <output epr="jms:queue/esb-tb-jmsBankResponseQueue" /> - <output epr="jms:queue/esb-tb-fileBankResponseQueue" /> - </service> - <service role="NotifierParticipant" validate="false" > - <input epr="jms:queue/esb-tb-customerNotifier" /> - </service> - </validator> - ]]></programlisting> - </informalexample> - - <para> - To define a <emphasis>Service Validator</emphasis> in record - only mode, the <emphasis>model</emphasis> attribute - is not specified (because no choreography description exists - to be validated against), and the optional <emphasis>validate</emphasis> - attribute should be set to <emphasis role="bold">false</emphasis> (by default - this attribute is <emphasis role="bold">true</emphasis>). - </para> - </section> - -</chapter> Copied: tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation.xml (from rev 91, tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml) =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,301 @@ +<?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="conversationvalidationwithcdl"> + <title>Conversation Validation with CDL</title> + <section> + <title>Overview</title> + <para> +Conversation validation is a form of runtime governance concerned with the dynamic behaviour of a system. + </para> + <para> +When coupled with a choreography description model of a system, this means having the ability to ensure that the way a collection of services interact correctly adheres to a description of the business process being enacted. + </para> + <para> +This section introduces the choreography description language (CDL) defined by W3C, and the <emphasis>pi4soa</emphasis> open source project which provides an editor for creating choreography descriptions, as well as utilizing these descriptions for runtime validation and execution purposes. + + </para> + + </section> + + <section> + <title>Configuration of Conversation Validation</title> + + <para> + This section explains how to configure the conversation validation mechanism to validate ESB 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 + 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> + + <para> +This filter is installed as part of the installation process for the SAVARA-Validator distribution. + </para> + </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. + </para> + <para> +An example of the contents of this file, that would related to the TrailBlazer example, is: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ + <validator mode="monitor" replyToTimeout="10000" > + <service model="TrailBlazer.cdm" + role="LoanBrokerParticipant" > + <output epr="jms:queue/esb-tb-creditAgencyQueue" /> + <input epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + <output epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <output epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <input epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-customerNotifier" /> + <input epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service model="TrailBlazer.cdm" + role="CreditAgencyParticipant" > + <input epr="jms:queue/esb-tb-creditAgencyQueue" /> + <output epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + </service> + <service model="TrailBlazer.cdm" + role="BankParticipant" > + <input epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <input epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <output epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service model="TrailBlazer.cdm" + role="NotifierParticipant" > + <input epr="jms:queue/esb-tb-customerNotifier" /> + </service> + </validator> + ]]></programlisting> + </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. + </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. + </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. + </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. + </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. + </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:'. + </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. + </para> + + </section> + + <section> + <title>Defining the Validator Configuration within a Choreography</title> + + <para> + The first step to configuring the validator is to associate the endpoint references (EPRs) + against the relevant choreography interactions. This is achieved by defining an + annotation for each 'exchange details' component (i.e. each request and response/notification). + </para> + + <imageobject> + <imagedata fileref="images/editvalidatorann.png" width="5in" /> + </imageobject> + + <para> + When the annotation editor is displayed for the relevant 'exchange details' component, + the <emphasis>jbossesb</emphasis> annotation should be added. This is achieved by + selecting the popup menu associated with the background of the lefthand panel, + and selecting the <emphasis>Add Defined Annotation</emphasis> menu item. + </para> + + <imageobject> + <imagedata fileref="images/editvalidatoranndiag.png" width="5in" /> + </imageobject> + + <para> + When the list of defined annotations is displayed, select the + <emphasis>jbossesb</emphasis> annotation. + </para> + + <imageobject> + <imagedata fileref="images/editvalidatorannselect.png" width="3in" /> + </imageobject> + + <para> + After pressing the <emphasis>Ok</emphasis> button, the annotation editor + will configure the righthand panel with the parameters associated with this + annotation. + </para> + + <imageobject> + <imagedata fileref="images/SVJBossESBAnnotation.jpg" width="5in" /> + </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 + 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. + </para> + + <para> + Once the annotation has been defined, then press the <emphasis>Save</emphasis> + button to save the annotation against the interaction's exchange details. + </para> + + <para> + When all of the relevant 'exchange details' components have been configured with + a <emphasis>jbossesb</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 + the validation mechanism to derive the configuration information from the choreography + description model, and begin validating the defined destinations against that + choreography description model. + </para> + + </section> + + </section> + + <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> +The destination defined in this file must match the one configured in the <emphasis>pi4soa.sar/pi4soa.xml</emphasis> file within the server. +</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 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. + </para> + + <imageobject> + <imagedata fileref="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. + </para> + <para> +If any <emphasis>out of sequence</emphasis> or other error situations arise, these are displayed in red. + </para> + </section> + + <section> + <title>Configuration for Conversation Recording</title> + + <para> + As well as validating the interactions between a set of + services, against a pre-defined choreography description, + it is also possible to use the <emphasis>Service Validators</emphasis> + in a non-validating record mode. + </para> + + <para> + This will be useful in situations where a choreography + description does not currently exist, and we wish to + use the stream of business events being sent and received + by each identified service (or participant type) to + gain an understanding of the current business process. + </para> + + <para> + An example of this type of configuration, associated + with the TrailBlazer example, is: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ + <validator> + <service role="LoanBrokerParticipant" validate="false" > + <output epr="jms:queue/esb-tb-creditAgencyQueue" /> + <input epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + <output epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <output epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <input epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-customerNotifier" /> + <input epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service role="CreditAgencyParticipant" validate="false" > + <input epr="jms:queue/esb-tb-creditAgencyQueue" /> + <output epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + </service> + <service role="BankParticipant" validate="false" > + <input epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <input epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <output epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service role="NotifierParticipant" validate="false" > + <input epr="jms:queue/esb-tb-customerNotifier" /> + </service> + </validator> + ]]></programlisting> + </informalexample> + + <para> + To define a <emphasis>Service Validator</emphasis> in record + only mode, the <emphasis>model</emphasis> attribute + is not specified (because no choreography description exists + to be validated against), and the optional <emphasis>validate</emphasis> + attribute should be set to <emphasis role="bold">false</emphasis> (by default + this attribute is <emphasis role="bold">true</emphasis>). + </para> + </section> + +</chapter> Added: validator/trunk/docs/pom.xml =================================================================== --- validator/trunk/docs/pom.xml (rev 0) +++ validator/trunk/docs/pom.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,22 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + + <modelVersion>4.0.0</modelVersion> + + <groupId>org.jboss.savara.validator</groupId> + <artifactId>docs</artifactId> + <packaging>pom</packaging> + <name>Savara::Validator::Docs</name> + + <parent> + <groupId>org.jboss.savara</groupId> + <artifactId>validator</artifactId> + <version>1.0-SNAPSHOT</version> + </parent> + + <modules> + <module>samplesguide</module> + </modules> + +</project> Added: validator/trunk/docs/samplesguide/pom.xml =================================================================== --- validator/trunk/docs/samplesguide/pom.xml (rev 0) +++ validator/trunk/docs/samplesguide/pom.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,85 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + + <modelVersion>4.0.0</modelVersion> + + <groupId>org.jboss.savara.validator.docs</groupId> + <artifactId>samplesguide</artifactId> + <packaging>jdocbook</packaging> + <name>Savara::Validator::Docs::SamplesGuide</name> + + <parent> + <groupId>org.jboss.savara.validator</groupId> + <artifactId>docs</artifactId> + <version>1.0-SNAPSHOT</version> + </parent> + + + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.1.2</version> + <extensions>true</extensions> + <executions> + <execution> + <id>generate-docbook</id> + <phase>package</phase> + <goals> + <goal>resources</goal> + <goal>generate</goal> + </goals> + </execution> + </executions> + <dependencies> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-docbook-xslt</artifactId> + <version>1.1.0</version> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.0</version> + <type>jdocbook-style</type> + </dependency> + </dependencies> + <configuration> + <sourceDocumentName>master.xml</sourceDocumentName> + <sourceDirectory>${basedir}/src/main</sourceDirectory> + <imageResource> + <directory>${basedir}/src/main</directory> + <includes> + <include>images/**/*</include> + </includes> + </imageResource> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource>file:///${basedir}/src/main/xslt/pdf.xsl</stylesheetResource> + <finalName>SAVARA-Validator-SamplesGuide.pdf</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <xincludeSupported>true</xincludeSupported> + <xmlTransformerType>saxon</xmlTransformerType> + <docbookVersion>1.72.0</docbookVersion> + </options> + </configuration> + </plugin> + </plugins> + </build> + +</project> Added: validator/trunk/docs/samplesguide/src/main/images/ChoreoMonReady.jpg =================================================================== (Binary files differ) Property changes on: validator/trunk/docs/samplesguide/src/main/images/ChoreoMonReady.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/docs/samplesguide/src/main/images/MonitorMenu.jpg =================================================================== (Binary files differ) Property changes on: validator/trunk/docs/samplesguide/src/main/images/MonitorMenu.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/docs/samplesguide/src/main/images/TrailblazerWebPage.jpg =================================================================== (Binary files differ) Property changes on: validator/trunk/docs/samplesguide/src/main/images/TrailblazerWebPage.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/docs/samplesguide/src/main/master.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/master.xml (rev 0) +++ validator/trunk/docs/samplesguide/src/main/master.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,17 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % RH-ENTITIES SYSTEM "Common_Config/rh-entities.ent"> +]> + +<book lang="en"> + <bookinfo> + <title>SAVARA Validator 1.0-SNAPSHOT</title> + <subtitle>Samples Guide</subtitle> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/author_group.xml"/> + </bookinfo> + + <toc/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/cdlvalidator.xml"/> + +</book> Added: validator/trunk/docs/samplesguide/src/main/module/author_group.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/module/author_group.xml (rev 0) +++ validator/trunk/docs/samplesguide/src/main/module/author_group.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,7 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup> + <corpauthor>Gary Brown</corpauthor> + <corpauthor>Jeff Yu</corpauthor> +</authorgroup> Added: validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml (rev 0) +++ validator/trunk/docs/samplesguide/src/main/module/cdlvalidator.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,132 @@ +<?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="cdlvalidator"> + <title>CDL Validator</title> + + <section> + <title>Trailblazer Example</title> + + <para> +This example can be found in the <filename>trailblazer</filename> folder, which contains an enhanced version of the trailblazer example found in the JBossESB distribution. See the TrailBlazer Guide in the JBossESB distribution (<filename>$JBossESB/docs/samples/TBGuide.pdf</filename>) for more information about the example. The main changes are the introduction of a File Based Bank, and modifications to the message structures to enable a consistent conversation id to be carried with the messages. + </para> + +<note> + <para> +The choreography description for the Trailblazer example can be found in the <emphasis>trailblazer-models</emphasis> project in the Eclipse environment. If the project has not yet been imported, then please refer to the instructions in the <emphasis>Getting Started Guide</emphasis>. + </para> + <para> +You can open the choreography for the trailblazer (trailblazer.cdm) and also a scenario representing a valid transaction associated with the choreography (LoanRequest.scn). In the choreography description editor, view the "Choreography Flows" tab to see the structure of the process. + </para> + <para> +To simulate the scenario against the choreography, to ensure that the choreography correctly caters for the valid business scenario, the user should press the green 'play' button in the toolbar, associated with the Scenario Editor. + </para> +</note> + + + <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. If the selected folders do not exist, then please ensure they are created prior to running the example. + </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> + <listitem> +From the <filename>trailblazer</filename> folder, execute the command to start 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> + <listitem> + <para> +In the Eclipse environment, select the popup menu associated with the <filename>trailblazer.cdm</filename> file, and choose the <emphasis>Choreography->Monitor</emphasis> menu item. + </para> + + <imageobject> + <imagedata fileref="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="images/ChoreoMonReady.jpg" align="center" width="4in" /> + </imageobject> + + </listitem> + <listitem> + <para> +Start a browser and enter the URL: <ulink url="http://localhost:8080/trailblazer">localhost:8080/trailblazer</ulink>. + </para> + + <imageobject> + <imagedata fileref="images/TrailblazerWebPage.jpg" align="center" width="4in" /> + </imageobject> + + </listitem> + <listitem> +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. + </listitem> + </orderedlist> + <para> +To demonstrate what occurs when the implementation deviates from the expected behaviour as defined in the choreography description, try the following steps: + </para> + <orderedlist> + <listitem> + Run the ant task <emphasis role="bold">ant deploy-error-client</emphasis> to redeploy the trailblaizer example. + </listitem> + <listitem> + Run the commands from step 6 above. + </listitem> + </orderedlist> + <para> + The above steps show how changing the service implementation without updating a choreography can result in behavioural validation errors being detected. + </para> + <tip> + <title>What is changed when we run ant deploy-error-client</title> + <para> + Compared to command of <emphasis role="bold">ant deploy</emphasis>, basically, we have just updated the following code in + <emphasis role="bold">$Overlord/samples/trailblazer/client/src/org/jboss/soa/esb/samples/trailblazer/loanbroker/LoanBroker.java</emphasis> file. + </para> + <para> + In the following code within the <emphasis role="bold">processLoanRequest</emphasis> method, we've changed the "4" to "7" + +<programlisting> + //step 2 - check if score is acceptable + if (score >= 4) { +</programlisting> + </para> + </tip> + + <para> + Issue further loan requests, remembering to change the quote reference each time, until a Credit Check result of between 4 and 6 inclusive occurs, which will result in an out of sequence message being reported (in red) to the Choreography Monitor + + <note> + <para> + It is currently a requirement that the choreography used within the Choreography Monitor is the same as the description used to locally monitor the services (i.e. within the overlord-cdl-validator.esb/models directory). + </para> + </note> + </para> + + </section> + +</chapter> Added: validator/trunk/docs/samplesguide/src/main/module/overview.xml =================================================================== --- validator/trunk/docs/samplesguide/src/main/module/overview.xml (rev 0) +++ validator/trunk/docs/samplesguide/src/main/module/overview.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,30 @@ +<?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="overview"> + <title>Overview</title> + <para>The Overlord CDL distribution contains two main types of functionality:</para> + <orderedlist> + <listitem> + the ability to validate executing services against a choreography description (an example of runtime governance). + </listitem> + <listitem> + the ability to build an ESB using 'conversation aware' actions which can be checked for conformance against a choreography description (an example of design time governance). + </listitem> + </orderedlist> + + <para> + This document will describe the samples available to demonstrate each aspect of the functionality. + </para> + <para> + Further information about configuring the runtime validation of services against a choreography can be found in the <emphasis role="bold">UserGuide</emphasis>. + Information regarding the conversation aware ESB actions, and how to use them in conjunction with conformance checking against a choreography description, can also be found in the <emphasis role="bold">UserGuide</emphasis>. + </para> + + <note> + <para> + Before attempting to install and run these examples, you must follow the instructions in the <emphasis role="bold">"Installation" Chapter</emphasis> of the <emphasis role="bold">Getting Started Guide</emphasis> regarding installing Overlord CDL into a JBossAS environment, and importing the samples into the Eclipse environment. + </para> + </note> + +</chapter> Added: validator/trunk/docs/samplesguide/src/main/xslt/pdf.xsl =================================================================== --- validator/trunk/docs/samplesguide/src/main/xslt/pdf.xsl (rev 0) +++ validator/trunk/docs/samplesguide/src/main/xslt/pdf.xsl 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,91 @@ +<?xml version="1.0" encoding="UTF-8"?> +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" + xmlns:fo="http://www.w3.org/1999/XSL/Format" + version="1.0"> + + <xsl:import href="http://docbook.sourceforge.net/release/xsl/1.72.0/fo/docbook.xsl" /> + <xsl:import href="classpath:/xslt/org/jboss/pdf.xsl" /> + +  + <xsl:param name="body.font.family" select="'Times New Roman, serif'" /> + <xsl:param name="monospace.font.family" select="'DejaVu Sans Mono, monospace'" /> + <xsl:param name="sans.font.family" select="'Arial, sans-serif'" /> + <xsl:param name="title.font.family" select="$body.font.family" /> + <xsl:param name="programlisting.font" select="$monospace.font.family" /> + <xsl:param name="programlisting.font.size" select="'75%'" /> + +  + <xsl:param name="double.sided" select="0" /> + +  + <xsl:param name="callout.graphics" select="1" /> + <xsl:param name="callout.graphics.extension" select="'.svg'" /> + +  + <xsl:param name="ulink.show" select="0"/> + +  + <xsl:attribute-set name="xref.properties"> + <xsl:attribute name="font-style">normal</xsl:attribute> + </xsl:attribute-set> + +  + <xsl:attribute-set name="monospace.properties"> + <xsl:attribute name="font-size">1em</xsl:attribute> + <xsl:attribute name="font-family"> + <xsl:value-of select="$monospace.font.family"/> + </xsl:attribute> + </xsl:attribute-set> + +  + <xsl:template match="callout"> + <xsl:variable name="id"><xsl:call-template name="object.id"/></xsl:variable> + <fo:list-item id="{$id}" space-before="1em"> + <fo:list-item-label end-indent="label-end()"> + <fo:block> + <xsl:call-template name="callout.arearefs"> + <xsl:with-param name="arearefs" select="@arearefs"/> + </xsl:call-template> + </fo:block> + </fo:list-item-label> + <fo:list-item-body start-indent="body-start()"> + <fo:block padding-top="0.2em"> + <xsl:apply-templates/> + </fo:block> + </fo:list-item-body> + </fo:list-item> + </xsl:template> + +  + <xsl:template name="callout-bug"> + <xsl:param name="conum" select='1'/> + <xsl:choose> + <xsl:when test="$conum <= $callout.graphics.number.limit"> + <xsl:variable name="filename" + select="concat($callout.graphics.path, $conum, + $callout.graphics.extension)"/> + + <fo:external-graphic content-width="{$callout.icon.size}" + width="{$callout.icon.size}" + padding="0.0em" margin="0.0em" + baseline-shift="-0.375em"> + <xsl:attribute name="src"> + <xsl:choose> + <xsl:when test="$passivetex.extensions != 0 + or $fop.extensions != 0 + or $arbortext.extensions != 0"> + <xsl:value-of select="$filename"/> + </xsl:when> + <xsl:otherwise> + <xsl:text>url(</xsl:text> + <xsl:value-of select="$filename"/> + <xsl:text>)</xsl:text> + </xsl:otherwise> + </xsl:choose> + </xsl:attribute> + </fo:external-graphic> + </xsl:when> + </xsl:choose> + </xsl:template> +</xsl:stylesheet> + Added: validator/trunk/pom.xml =================================================================== --- validator/trunk/pom.xml (rev 0) +++ validator/trunk/pom.xml 2009-11-25 22:14:32 UTC (rev 92) @@ -0,0 +1,230 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> + <modelVersion>4.0.0</modelVersion> + <groupId>org.jboss.savara</groupId> + <artifactId>validator</artifactId> + <version>1.0-SNAPSHOT</version> + <packaging>pom</packaging> + <name>Savara::Validator</name> + <url>http://www.jboss.org/savara</url> + <description> + The JBoss SAVARA Validator. + </description> + <scm> + <connection>scm:svn:https://svn.jboss.org/repos/savara/validator</connection> + </scm> + <developers> + <developer> + <name>Jeff Yu</name> + <id>jeff.yuchang</id> + <email>cyu(a)redhat.com</email> + <organization>Red Hat</organization> + <roles> + <role>Developer</role> + </roles> + <timezone>+8</timezone> + </developer> + <developer> + <name>Gary Brown</name> + <id>objectiser</id> + <email>gbrown(a)redhat.com</email> + <organization>Red Hat</organization> + <roles> + <role>Developer</role> + </roles> + <timezone>+1</timezone> + </developer> + </developers> + <modules> + <module>jbossesb</module> +  + <module>docs</module> +  + </modules> + + <profiles> + <profile> +  + <id>docs</id> + <activation> + <property> + <name>generate.docs</name> + </property> + </activation> + <modules> + <module>docs</module> + </modules> + <reporting> + <plugins> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-javadoc-plugin</artifactId> + <configuration> + <aggregate>true</aggregate> + <show>public</show> + <title>JBoss Savara ${project.version}</title> + </configuration> + </plugin> + </plugins> + </reporting> + </profile> + </profiles> + + <build> +  + <pluginManagement> + <plugins> +  + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-javadoc-plugin</artifactId> + <version>2.2</version> + <configuration> + <aggregate>true</aggregate> + </configuration> + </plugin> + </plugins> + </pluginManagement> + <plugins> +  + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-compiler-plugin</artifactId> + <version>2.0.2</version> + <configuration> + <source>1.5</source> + <target>1.5</target> + <showDeprecation>false</showDeprecation> + <showWarnings>false</showWarnings> + </configuration> + </plugin> +  + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-source-plugin</artifactId> + <executions> + <execution> + <id>attach-sources</id> + <phase>verify</phase> + <goals> + <goal>jar</goal> + </goals> + </execution> + </executions> + </plugin> + <plugin> + <artifactId>maven-surefire-plugin</artifactId> + <configuration> + <includes> + <include>**/*TestCase.java</include> + <include>**/*Test.java</include> + </includes> + </configuration> + </plugin> + </plugins> + </build> + + <properties> + <savara-version>1.0-SNAPSHOT</savara-version> + <junit.version>4.4</junit.version> + <rosetta.version>4.5</rosetta.version> + <log4j.version>1.2.14</log4j.version> + <mvel.version>1.3.4-java1.5</mvel.version> + </properties> + + <dependencyManagement> + <dependencies> + <dependency> + <groupId>junit</groupId> + <artifactId>junit</artifactId> + <version>${junit.version}</version> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss.overlord.dependencies.org.jboss.esb</groupId> + <artifactId>jbossesb-rosetta</artifactId> + <version>${rosetta.version}</version> + </dependency> + <dependency> + <groupId>log4j</groupId> + <artifactId>log4j</artifactId> + <version>${log4j.version}</version> + </dependency> + <dependency> + <groupId>org.mvel</groupId> + <artifactId>mvel</artifactId> + <version>${mvel.version}</version> + </dependency> + </dependencies> + </dependencyManagement> + + + <reporting> + <plugins> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-surefire-report-plugin</artifactId> + </plugin> + </plugins> + </reporting> + + <repositories> + <repository> + <id>jboss</id> + <url>http://repository.jboss.com/maven2/</url> + <snapshots> + <enabled>false</enabled> + </snapshots> + </repository> + + <repository> + <id>jboss-snapshot</id> + <url>http://snapshots.jboss.org/maven2</url> + <snapshots> + <enabled>true</enabled> + </snapshots> + </repository> + + <repository> + <id>maven.repo</id> + <name>maven repository</name> + <url>http://repo1.maven.org/maven2</url> + </repository> + + <repository> + <id>ibiblio</id> + <name>ibiblio repository</name> + <url>http://mirrors.ibiblio.org/pub/mirrors/maven2</url> + </repository> + + <repository> + <id>codehaus</id> + <name>codehaus repository</name> + <url>http://repo1.maven.org/maven2</url> + </repository> + + </repositories> + + <distributionManagement> + <repository> + <id>jboss</id> + <name>JBoss Maven Repository</name> + <url>file://${jboss.maven.repository}</url> + </repository> + <snapshotRepository> + <id>jboss-snapshots</id> + <name>JBoss Snapshot Repository</name> + <url>dav:https://snapshots.jboss.org/maven2</url> + </snapshotRepository> + </distributionManagement> + +</project>

14 years, 4 months

1
0
0 / 0

savara SVN: r91 - in tools/eclipse/trunk/docs: gettingstartedguide and 5 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-24 18:47:13 -0500 (Tue, 24 Nov 2009) New Revision: 91 Added: tools/eclipse/trunk/docs/userguide/pom.xml tools/eclipse/trunk/docs/userguide/src/main/images/SVJBossESBAnnotation.jpg tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatorann.png tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatoranndiag.png tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatorannselect.png tools/eclipse/trunk/docs/userguide/src/main/images/genbpel1.png tools/eclipse/trunk/docs/userguide/src/main/images/genbpel2.png tools/eclipse/trunk/docs/userguide/src/main/images/genbpel3.png tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig1.png tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig2.png tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig3.png tools/eclipse/trunk/docs/userguide/src/main/images/genvalidatordialog.png tools/eclipse/trunk/docs/userguide/src/main/images/genvalidatormenu.png tools/eclipse/trunk/docs/userguide/src/main/images/monitorui.png tools/eclipse/trunk/docs/userguide/src/main/images/setconversationtype.png tools/eclipse/trunk/docs/userguide/src/main/master.xml tools/eclipse/trunk/docs/userguide/src/main/module/author_group.xml tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml tools/eclipse/trunk/docs/userguide/src/main/module/conversation-aware-esb.xml tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml tools/eclipse/trunk/docs/userguide/src/main/xslt/pdf.xsl Modified: tools/eclipse/trunk/docs/gettingstartedguide/pom.xml tools/eclipse/trunk/docs/pom.xml Log: Initial version of Eclipse tools user guide. Modified: tools/eclipse/trunk/docs/gettingstartedguide/pom.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/pom.xml 2009-11-24 21:53:27 UTC (rev 90) +++ tools/eclipse/trunk/docs/gettingstartedguide/pom.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -59,7 +59,7 @@ <format> <formatName>pdf</formatName> <stylesheetResource>file:///${basedir}/src/main/xslt/pdf.xsl</stylesheetResource> - <finalName>GettingStartedGuide.pdf</finalName> + <finalName>SAVARA-Eclipse-Tools-GettingStartedGuide.pdf</finalName> </format> <format> <formatName>html</formatName> Modified: tools/eclipse/trunk/docs/pom.xml =================================================================== --- tools/eclipse/trunk/docs/pom.xml 2009-11-24 21:53:27 UTC (rev 90) +++ tools/eclipse/trunk/docs/pom.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -16,7 +16,7 @@ </parent> <modules> -  + <module>userguide</module> <module>gettingstartedguide</module> </modules> Added: tools/eclipse/trunk/docs/userguide/pom.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/pom.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/pom.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,86 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + + <modelVersion>4.0.0</modelVersion> + + <groupId>org.jboss.savara.tools.eclipse.docs</groupId> + <artifactId>userguide</artifactId> + <packaging>jdocbook</packaging> + <name>Savara::Tools::Eclipse::Docs::UserGuide</name> + + <parent> + <groupId>org.jboss.savara.tools.eclipse</groupId> + <artifactId>docs</artifactId> + <version>1.0-SNAPSHOT</version> + </parent> + + + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.1.2</version> + <extensions>true</extensions> + <executions> + <execution> + <id>generate-docbook</id> + <phase>package</phase> + <goals> + <goal>resources</goal> + <goal>generate</goal> + </goals> + </execution> + </executions> + <dependencies> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-docbook-xslt</artifactId> + <version>1.1.0</version> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.0</version> + <type>jdocbook-style</type> + </dependency> + </dependencies> + <configuration> + <sourceDocumentName>master.xml</sourceDocumentName> + <sourceDirectory>${basedir}/src/main</sourceDirectory> + <imageResource> + <directory>${basedir}/src/main</directory> + <includes> + <include>images/**/*</include> + </includes> + </imageResource> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource>file:///${basedir}/src/main/xslt/pdf.xsl</stylesheetResource> + <finalName>SAVARA-Eclipse-Tools-UserGuide.pdf</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <xincludeSupported>true</xincludeSupported> + <xmlTransformerType>saxon</xmlTransformerType> + <docbookVersion>1.72.0</docbookVersion> + </options> + </configuration> + </plugin> + </plugins> + </build> + + +</project> Added: tools/eclipse/trunk/docs/userguide/src/main/images/SVJBossESBAnnotation.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/SVJBossESBAnnotation.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatorann.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatorann.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatoranndiag.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatoranndiag.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatorannselect.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/editvalidatorannselect.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genbpel1.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genbpel1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genbpel2.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genbpel2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genbpel3.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genbpel3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig1.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig2.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig3.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genesbconfig3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genvalidatordialog.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genvalidatordialog.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/genvalidatormenu.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/genvalidatormenu.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/monitorui.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/monitorui.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/images/setconversationtype.png =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/userguide/src/main/images/setconversationtype.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/userguide/src/main/master.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/master.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/master.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % RH-ENTITIES SYSTEM "Common_Config/rh-entities.ent"> +]> + +<book lang="en"> + <bookinfo> + <title>SAVARA Eclipse Tools 1.0-SNAPSHOT</title> + <subtitle>User Guide</subtitle> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/author_group.xml"/> + </bookinfo> + + <toc/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/bpel-governance.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/cdlconformance.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/conversation-aware-esb.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/conversation-validation-with-cdl.xml"/> + +</book> Added: tools/eclipse/trunk/docs/userguide/src/main/module/author_group.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/author_group.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/author_group.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,7 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup> + <corpauthor>Gary Brown</corpauthor> + <corpauthor>Jeff Yu</corpauthor> +</authorgroup> Added: tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/bpel-governance.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,71 @@ +<?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="bpelgovernance"> + <title>BPEL Governance</title> + + <section> + <title>Overview</title> + <para> +This section will describe governance features related to WS-BPEL. This initial release provides basic support for generating BPEL processes from a choreography description. Subsequent releases will also provide conformance checking, to ensure that changes to a BPEL process are validated to ensure the process remains conformant with the choreography. + </para> + </section> + + <section> + <title>Generating a BPEL process from CDL</title> + <section> + <title>Overview</title> + <para> +This section explains how to generate a template BPEL process from a pi4soa choreography description (.cdm) file. + </para> + </section> + <section> + <title>Generating the BPEL Process</title> + <para> +When the choreography description has been completed, and has no errors, the user should select the "Overlord->Generate->WS-BPEL" menu item from the popup menu associated with the choreography description (.cdm) file. + </para> + + <imageobject> + <imagedata fileref="images/genbpel1.png" width="4in" /> + </imageobject> + + <para> +When the dialog window is displayed, it will contain the list of services that can be generated, along with the project names that will be created. The user can unselect the services they do not wish to generate (also using the 'Check All' or 'Clear All' buttons). + </para> + + <imageobject> + <imagedata fileref="images/genbpel2.png" /> + </imageobject> + + <para> +The user can also select their preferred build system, which will create the relevant build structure. + </para> + <para> +If there is a problem with the name of the project select, such as invalid characters used in the name, or the project name already exists, then it will be displayed in red. + </para> + + <para> +Once the BPEL is generated, it can be viewed using the Eclipse BPEL editor, e.g. + </para> + + <imageobject> + <imagedata fileref="images/genbpel3.png" /> + </imageobject> + + </section> + + <section> + <title>Limitations with the current CDL to BPEL mapping</title> + + <para> +This initial version of the BPEL generation is primarily targeted at generating the interactions and grouping constructs. These are the important components that will be required when doing conformance checking as part of the next milestone. + </para> + + <para> +This means that assignments and conditional expressions are not currently generated. The 'when' construct in CDL (also known as the blocking workunit) is also not currently handled. This may possible be implemented using flow links. + </para> + </section> + </section> + +</chapter> + Added: tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/cdlconformance.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,192 @@ +<?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="cdlconformance"> + <title>CDL Conformance</title> + + <para> +There are two examples to demonstrate the conversation aware ESB actions(for both stateful and stateless), and the conformance checking against a choreography. + </para> + <para> +These are <filename>purchasing</filename>, a simple customer/supplier example with two associated Eclipse projects (<filename>purchasing-store-stateful/less</filename> and <filename>purchasing-models</filename>), and <filename>brokerage</filename> which extends the purchasing example through the introduction of a broker that mediates between potentially multiple suppliers to find the best deal, defined within three Eclipse projects (<filename>brokerage-broker-stateful/less</filename>, <filename>brokerage-supplier-stateful/less</filename> and <filename>brokerage-models</filename>). + </para> + <para> +These examples make use of a common <emphasis>Credit Agency</emphasis> service, defined within the <filename>common-creditAgency-stateful/less</filename> Eclipse project, and are executed through the use of client applications defined in the <filename>${OverlordCDL}/samples/client</filename> folder. + </para> + + <warning> + At the moment, the conversation aware ESB runtime doesn't support the hot-deploy. That means if you update the business pojo class, such as <emphasis role="bold">$creditAgency/src/main/com/acme/services/creditAgency/CreditAgencyPurchase.java</emphasis> file, + You need to re-deploy it, and then <emphasis role="bold">restart the server </emphasis> to cause it to take effect. This issue has been tracked under <ulink url="https://jira.jboss.org/jira/browse/SOAG-72">https://jira.jboss.org/jira/browse/SOAG-72</ulink>. Will be fixed in the next release. + </warning> + + <section> + <title>Purchasing Example</title> + <section> + <title>Overview</title> + <para> +The purchasing example describes the interactions between a Buyer, Store and Credit Agency. The flow for this example would be: + </para> + <itemizedlist> + <listitem> +Buyer send a 'buy' request to Store + </listitem> + <listitem> +Store send a 'credit check' request to the Credit Agency. + </listitem> + <listitem> +If the Credit Agency returns a successful message, then the Store will send a 'BuyConfirmed' to user. + </listitem> + <listitem> +If the Credit Agency returns a failed message, then the Store will send a 'BuyFailed' to user. + </listitem> + </itemizedlist> + + <para> +To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. +The <filename>purchasing-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. + </para> + <para> +To provide a simple demonstration of the conformance checking: + </para> + <orderedlist> + <listitem> +Double click on <filename>purchasing-store[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> + </listitem> + <listitem> +Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. + </listitem> + <listitem> +Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. + </listitem> + <listitem> +Then save the file. This should result in an error being generated, complaining about a type mismatch. + </listitem> + </orderedlist> + <para> +The information regarding the expected message type is obtained from the choreography description in the <filename>purchasing-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. + </para> + <para> +Another Quick Fix option associated with this error is <emphasis>Update from Referenced Description</emphasis>. By selecting this option, you will notice that the message type is changed back to the value without the 'X'. + </para> + </section> + + <section> + <title>Running the Example</title> + <para> + This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. + One is the stateful purchasing example (this is the example that we had since M1 release),the other is stateless purchasing example that is introduced in the M2 release. + </para> + <orderedlist> + <listitem> + First step is to install the ESB services. (Presumely the JBoss ESB server started already) + In a command window, Go to the the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/sample/stateless</filename> in the stateless approach), execute the <emphasis role="bold">ant deploy-purchasing</emphasis>. + </listitem> + <listitem> + Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runPurchasingClient</emphasis> (or <emphasis role="bold"> ant runStatelessPurchasingClient</emphasis> in stateless approach.), which will send a 'BuyRequest' message to the Store, which will then perform the credit check before returning a response to the client. + </listitem> + </orderedlist> + + <para> +To see a different response from the client, change the <emphasis>isCreditValid</emphasis> method on the <emphasis>CreditAgencyPurchase</emphasis> class to return <emphasis>false</emphasis>, within the <filename>common/creditAgency</filename> ESB service implementation, and then re-deploy the Credit Agency service. Then when the client is re-run, a 'BuyFailed' message will be returned. + </para> + + <tip> + <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-purchasing</command> in the <filename>$Overlord/samples/stateful</filename> folder or <filename>$Overlord/samples/stateless</filename> folder respectively.</para> + </tip> + + </section> + + </section> + + <section> + <title>Brokerage Example</title> + + <section> + <title>Overview</title> + + <para> +The brokerage example describes the interactions between a Customer, Broker, Supplier and Credit Agency. The flow for this example would be: + </para> + + <itemizedlist> + <listitem> +Customer sends an 'enquiry' request to Broker + </listitem> + <listitem> +Broker sends the request to one or more Suppliers concurrently + </listitem> + <listitem> +When all of the quote responses have been received, or a timeout expires, the available information is returned to the Customer + </listitem> + <listitem> +Customer decides whether to: + <itemizedlist> + <listitem> + Cancel the transaction, or + </listitem> + <listitem> + Send a 'buy' request to the Broker + </listitem> + </itemizedlist> + </listitem> + <listitem> +If a 'buy' request is received by the Broker, it will send a 'credit check' request to the Credit Agency + </listitem> + <listitem> +If the Credit Agency returns a successful message, then the Broker sends a 'buy' request to the Supplier selected by the Customer (in the 'buy' request), followed by a confirmation back to the Customer + </listitem> + <listitem> +If the Credit Agency returns a failed message, then the Broker will inform the Customer + </listitem> + </itemizedlist> + + <para> +To check conformance, we need to refer to the model and service implementation projects in the Eclipse environment. +The <filename>brokerage-models</filename> project contains the CDL used to perform conformance checking on the <filename>src/main/resources/META-INF/jboss-esb.xml</filename> files within the other brokerage projects. A full explanation of the conversation aware ESB actions can be found in the <emphasis>Conversational Aware ESB</emphasis> section of the <emphasis>User Guide</emphasis> in the <filename>docs</filename> folder. + </para> + <para> +To provide a simple demonstration of the conformance checking: + </para> + <orderedlist> + <listitem> +Double click on <filename>brokerage-broker[-stateful/less]/src/main/resources/META-INF/jboss-esb.xml</filename> + </listitem> + <listitem> +Scroll down to the second action, within the first service. This represents a <emphasis>ReceiveMessageAction</emphasis> and has a property defining the message type to be received. + </listitem> + <listitem> +Edit the 'messageType' property value, e.g. by adding an 'X' to the end of the value. + </listitem> + <listitem> +Then save the file. This should result in an error being generated, complaining about a type mismatch. + </listitem> + </orderedlist> + <para> +The information regarding the expected message type is obtained from the choreography description in the <filename>brokerage-models</filename> project. To identify the precise interaction within the choreography that this error relates to, select the context menu associated with the error and choose the Quick Fix menu item. This will display a dialog with a list of fixes, select the <emphasis>Show referenced description</emphasis> option and press OK. This will cause the relevant interaction within the choreography description to be displayed. + </para> + </section> + + <section> + <title>Running the Example</title> + <para> + This example has two versions, stateful and stateless. in the sample folder, you will find the samples were grouped in stateful and stateless folder. + one is the sateful broker example (this is the example that we had since M1 release), the other is stateless broker example that is introduced in the M2 release. + </para> + <orderedlist> + <listitem> + First step is to install the ESB services (Presumely the JBoss ESB server started already) + In a command window, Go to the <filename>$Overlord/samples/stateful</filename> folder (or <filename>$Overlord/samples/stateless</filename> in the stateless approach), execute <emphasis role="bold">ant deploy-broker</emphasis> + </listitem> + <listitem> + Go to the <filename>$Overlord/samples/client</filename> folder and execute <emphasis role="bold">ant runBrokerageClient</emphasis> (or <emphasis role="bold"> ant runStatelessBrokerageClient</emphasis> in stateless approach), which will initially send an 'enquiry' message to the Broker, which will communicate with the set of Suppliers to obtain the best quote. The client will then send a 'buy' request, which will result in the Broker performing a credit check before returning a response to the client. + </listitem> + </orderedlist> + + <tip> + <para>You can undeploy the corresponding esb artifact by through command <command>ant undeploy-broker</command> in $Overlord/samples/stateful or $Overlord/samples/stateless respectively.</para> + </tip> + </section> + + </section> + +</chapter> Added: tools/eclipse/trunk/docs/userguide/src/main/module/conversation-aware-esb.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/conversation-aware-esb.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/conversation-aware-esb.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,483 @@ +<?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="conversationawareesb"> + <title>Conversation Aware ESB</title> + <section> + + <warning> + <para> +The <emphasis>conversation aware ESB actions</emphasis> mechanism should be considered an alpha version only, +and subject to change in future releases. Its inclusion within this release is intended to enable the community +to experiment with the approach and hopefully provide feedback that can be used to guide the direction of this capability. + </para> + </warning> + + <title>Conversation based Conformance</title> + <section> + <title>Overview</title> + <para> +The term "conversation" represents a structured set of interactions (or message exchanges) between +one or more peer to peer services, to conduct a business transaction. The "conversation" is defined +from a service neutral (i.e. global) perspective. + </para> + <para> +This document explains how such a "conversation" description can be used to ensure conformance of +one or more service implementations, within an ESB, during the design and implementation phase of +the system. + </para> + <para> +This section introduces the choreography description language (CDL) defined by W3C, which is a +standard notation for defining conversations from a global perspective, and the +<emphasis>pi4soa</emphasis> open source project which provides an editor for creating choreography +descriptions, as well as utilizing these descriptions for conformance checking, monitoring and +execution purposes. + </para> + <para> +Finally the section will provide a brief discussion of how CDL can be used to provide conformance +checking of an ESB, through the use of 'conversation aware' ESB actions. + </para> + </section> + <section> + <title>CDL Conformance Checking</title> + <para> +In general, conformance checking is the procedure for ensuring that a component has been correctly +built according to some specification or standard. In terms of CDL, it more specifically ensures +that one or more services perform their responsibilities correctly in accordance with the +choreography description. + </para> + <para> +The <emphasis>pi4soa</emphasis> tools suite provide the mechanism for producing service endpoint +descriptions for each service within a choreography description. The relevant service descriptions +can then be compared (for conformance) against their ESB service implementations. + </para> + <para> +However, to make this possible, it is necessary to be able to derive the communication 'type' +structure from the ESB implementation, i.e. where messages (of particular types) are sent and +received, where decision points are, where actions are performed concurrently, etc. + </para> + <para> +This is why a specific set of 'conversation aware' ESB actions have been defined (discussed in a +later section), to make it possible to derive the communication 'type' structure from an ESB +service implementation. + </para> + <para> +Once the communication 'type' structure has been obtained from the ESB implementation, it can be +compared against the relevant service endpoint description projected from the choreography description, +to determine if there are any differences. These can then be reported to the ESB service developer, +so that they can fix the problems, before the service is deployed to the runtime environment. + </para> + <para> +This ensures that all of the services will interact correctly, as they will all have been validated +against the choreography, and therefore work together by design. + </para> + <para> +In the following section, we will describe how ESB services can be described using +"conversation aware" ESB actions. + </para> + </section> + </section> + + <section> + <title>"Conversation Aware" ESB Actions</title> + <section> + <title>Overview</title> + + <para> +The "conversation aware" ESB action mechanism provides a set of ESB actions that can be used +to instrument an ESB service with constructs that enable the communication structure to be +inferred. This is useful, as it enables the communication structure to be compared against the +expected behaviour defined in a choreography (global) model, or service design. + </para> + + <para> +Usually the stateful behaviour of a service is required to enable it to be compared against +the stateful behaviour defined in a choreography. However this would result in a stateful +service implementation being required for each ESB service, adding state management etc. +which would result in more complex service implementations. + </para> + + <para> +To void adding this complexity to the ESB service implementation, an approach called +<emphasis>stateful fragments</emphasis> has been used. This enables the causality to +be inferred based on dealing with each inbound event - however the causality between +received events is not modelled. The benefit of this approach is its simplicity, and +therefore it has less impact on the +way that users create ESB service descriptors. The disadvantage with this approach is that only +fragments of stateful behaviour can be derived from the ESB jboss-esb.xml. However, +this is useful enough to perform static conformance checking of the service implementation +against a choreography description, and when used in conjunction with the dynamic +conversation validation mechanism, it is still possible to determine out of sequence messages. + </para> + </section> + + <section> + <title>Interaction</title> + <para> +Firstly, let's see the two basic actions for interaction. +Services interact by sending and receiving messages, whether synchronously or asynchronously. + </para> + <para> +JBossESB is designed to anonymously handle inbound messages (possibly requests), without explicitly defining restrictions on message type, and then optionally returning responses (again without explicitly defining the response message type). + </para> + <para> +Although this is sufficient for a runtime mechanism, where issues related to unexpected message types can be handled with suitable exceptions/faults, it does not enable the communication type structure to be understood by examination of the JBossESB configuration. + </para> + + <section> + <title>Sending a message</title> + <para> +When sending a message, the first thing to consider is the type of the message. This can be declared as a property on the <emphasis>SendMessageAction</emphasis>. +If dealing with RPC style interactions, then we may also want to optionally specify an operation name. + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ + <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" + process="process" name="..."> + <property name="operation" value="getQuote" /> + <property name="messageType" value="requestForQuote" /> + .... + </action> + ]]></programlisting> + </informalexample> + + <itemizedlist> + <listitem> +Sending a request + <para> +When sending a request, we need to identify the destination service category/name. This is done by either specifying the category and name explicitly, using the <emphasis>serviceCategory</emphasis> and <emphasis>serviceName</emphasis> properties: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ + + <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" + process="process" name="..."> + .... + <property name="serviceName" value="RequestForQuote.main" /> + <property name="serviceCategory" value="ESBBroker.SupplierParticipant" /> + .... + </action> + ]]></programlisting> + </informalexample> + + </listitem> + + <listitem> +Sending a response + <informalexample> + <programlisting role="XML" ><![CDATA[ + + <action class="org.jboss.savara.jbossesb.actions.SendMessageAction" + process="process" name="..."> + .... + <property name="clientRole" value="buyer" /> + <property name="eprStore" value="orgization.your.impl.EPRStorageImpl" /> + .... + </action> + ]]></programlisting> + </informalexample> + <para> +When sending a response, the destination will not be directly available. The destination would have been received as a 'reply to' EPR (Endpoint Reference) in a previously received request (see <emphasis>ReceiveMessageAction</emphasis> for details of how to store the 'reply to' EPR). +Therefore, to indicate which EPR to respond to, a property called 'clientEPR' is specified with the name of the stored EPR. This must match up to a previously stored EPR name within a <emphasis>ReceiveMessageAction</emphasis>. + </para> + <para> +The value of <emphasis>storageClass</emphasis> should be a class that implements the <emphasis>org.jboss.soa.savara.jbossesb.EPRStorage</emphasis> interface, basically this class is responsible for registering, getting EPR from roleName. + </para> + </listitem> + </itemizedlist> + + </section> + + <section> + <title>Receiving a message</title> + + <informalexample> + <programlisting role="XML" ><![CDATA[ + <action class="org.jboss.savara.jbossesb.actions.ReceiveMessageAction" + process="process" name="s1-2"> + <property name="operation" value="makeEnquiry" /> + <property name="messageType" value="enquiry" /> + <property name="clientRole" value="buyer" /> + <property name="eprStore" value="com.acme.services.creditAgency.MemoryEPRStorage" /> + </action> + ]]></programlisting> + </informalexample> + + <para> +The <emphasis>ReceiveMessageAction</emphasis> is used to explicitly define the message type that should be received. +If an RPC style has been used, then the optional operation name can also be defined. + </para> + <para> +Unlike the <emphasis>SendMessageAction</emphasis>, which will actually send a message to the specified service category/name, +the <emphasis>ReceiveMessageAction</emphasis> primarily serves to provide explicit details about the expected message and to perform any relevant validation of the message content. If an incorrect message type is received, then an error will be logged. + </para> + <para> +The optional 'clientRole' and 'storageClass' properties are used to store any specific "reply to" EPR (associated with the message) against the specified name. This makes the EPR accessible to any subsequent <emphasis>SendMessageAction</emphasis> activities that need to return a response or send a notification. + </para> + </section> + </section> + + <section> + <title>Controlling Flow</title> + <para> +This section describes the two control flow mechanisms that are supported by the stateless ESB actions. + </para> + <para> +The default control flow, supported natively by the ESB action pipeline design, is a sequence. As the name implies, the actions are performed one at a time in the order they defined in the action pipeline, i.e. in a sequence. + </para> + + <section> + <title>Selecting paths based on a decision</title> + <para> +The action associated with the 'selection of a path based on a decision' is the <emphasis>IfAction</emphasis>. An example of this construct is: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ +<action class="org.jboss.savara.jbossesb.actions.IfAction" name="..." + process="process"> + <property name="paths"> + <if service-category="PurchaseGoods.CreditAgency" + service-name="CreditAgency.decision1" + decision-class="org.jboss.soa.savara.jbossesb.TestDecision"/> + <elseif service-category="PurchaseGoods.CreditAgency" + service-name="CreditAgency.decision2" + decision-class="org.jboss.soa.savara.jbossesb.Test2ndDecision"/> + <else service-category="PurchaseGoods.CreditAgency" + service-name="CreditAgency.decision3"/> + </property> +</action> + ]]></programlisting> + </informalexample> + <para> +This construct defines a 'path' property with one or more elements, representing the <emphasis>if</emphasis>, <emphasis>elseif</emphasis> and <emphasis>else</emphasis> aspects of the traditional if/else construct. Only the <emphasis>if</emphasis> element is mandatory, and can be followed by zero or more <emphasis>elseif</emphasis> elements before ending with the optional <emphasis>else</emphasis> element. + </para> + <para> +The <emphasis>if</emphasis> and <emphasis>elseif</emphasis> elements can define an 'decision-class' attribute to be evaluated at runtime, to determine if the associated 'service-category' and 'service-name' should be invoked. +the value of decision-class must implement the interface of <emphasis>org.jboss.soa.savara.jbossesb.Decision</emphasis>. + </para> + </section> + + <section> + <title>Message router action</title> + <para> +The action used to select paths based on a received message type is <emphasis>SwitchAction</emphasis>. +In the stateless esb actions approach, we are using this as the <emphasis>Message Router</emphasis>. +The configuration of <emphasis>SwithAction</emphasis> is like: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ +<action class="org.jboss.savara.jbossesb.actions.SwitchAction" + name="..." process="process"> + <property name="serviceDescriptionName" + value="{org.pi4soa.esbbroker.esbbroker}ESBBrokerProcess-Broker"/> + <property name="conversationType" value="savara.samples.LoanBroker@Broker"/> + <property name="paths"> + <case service-category="org.pi4soa.esbbroker.esbbroker" + service-name="ESBBrokerProcess_Broker__1"> + <message type="enquiry"/> + </case> + <case service-category="org.pi4soa.esbbroker.esbbroker" + service-name="ESBBrokerProcess_Broker__7"> + <event description="Event trigger to send quoteList message type(s)"/> + </case> + <case service-category="org.pi4soa.esbbroker.esbbroker" + service-name="ESBBrokerProcess_Broker__8"> + <message type="buy"/> + </case> + </property> +</action> + ]]></programlisting> + </informalexample> + <para> +In this approach, the <emphasis>SwitchAction</emphasis> typically is the point of contact for other services. Also true for the internal services. In the same manner as the <emphasis>Stateful</emphasis> ESB actions, it is necessary to specify the 'conversation type' that the service represents, to enable conformance checking to be performed against a choreography description that provides the associated conversation type. In the <emphasis>Stateless</emphasis> ESB actions, this initial <emphasis>SwitchAction</emphasis> defines this information in the <emphasis>conversationType</emphasis> property. + </para> + <para> +The 'paths' property defines one or more 'case' elements. These elements identify a service category and name that should be invoked upon receipt of one or more message types, as specified by 'message' elements contained within the 'case' elements. + </para> + <para> +The 'type' attribute on the 'message' element defines the type of message that can be routed to the specified service category/name. In the example above, the message types have no namespace. +However if they have a namespace, this can be defined in curly braces, e.g. "{http://www.jboss.org/samples}buy". + </para> + <para> +The 'event' element is defined for paths with no associated message type. These paths are expected to be triggered by a different sort of event, for example an internal timeout managed by the service implementation. However these internal events are triggered, and directed to the appropriate service descriptor is a implementation issue for the service. The inclusion of this path in the <emphasis>SwitchAction</emphasis> symbolises the exist of this asynchronously triggered path in the behaviour of the service. + </para> + <para> +Once a path has been selected, the associated service category/name will be invoked immediately. +If none of the paths specified within this action are relevant to the received message, then a runtime exception will be thrown. + </para> + </section> + + </section> + + <tip> + In this M2 release, we've just had these four actions in the stateless esb action approach. + we might add other actions in the subsequent release. If you have any comments and feedback, you can go to the forum or issue track to raise your request. + </tip> + + </section> + + <section> + <title>Generating a JBossESB Configuration from CDL</title> + <section> + <title>Overview</title> + <para> +This section explains how to generate a template JBossESB configuration file from a pi4soa choreography +description (.cdm) file. + </para> + </section> + <section> + <title>Generating the JBossESB Configuration</title> + <para> +When the choreography description has been completed, and has no errors, the user should select the +"SAVARA->Generate->JBossESB Services" menu item from the popup menu associated with the choreography +description (.cdm) file. + </para> + + <imageobject> + <imagedata fileref="images/genesbconfig1.png" width="4in" /> + </imageobject> + + <para> +When the dialog window is displayed, it will contain the list of services that can be generated, along with the project names that will be created. The user can unselect the services they do not wish to generate (also using the 'Check All' or 'Clear All' buttons). There is also a checkbox to determine whether a stateful or stateless (the default) implementation should be generated. + </para> + + <imageobject> + <imagedata fileref="images/genesbconfig2.png" /> + </imageobject> + + <para> +The user can also select their preferred build system, which will create the relevant build structure + and script in the generated Java project to enable the JBossESB service to be deployed, as well as + the appropiate messaging system to use. + </para> + <para> +If there is a problem with the name of the project select, such as invalid characters used in the name, +or the project name already exists, then it will be displayed in red. + </para> + + <imageobject> + <imagedata fileref="images/genesbconfig3.png" /> + </imageobject> + + <para> +In the above image, on the left it shows the generated project structure for the Broker service role. +On the right it shows a portion of a generated session class, with the accessor and modifier for one +of the variables associated with that session. + </para> + <para> +Although an initial build script will be created, depending on the build system selected, the user +may need to edit the script to set certain properties, or change the way the build occurs. For +example, with the Ant build, the deploy target (which is the default) will attempt to place the +deployed .esb file into a location defined by the <filename>${org.jboss.esb.server.deploy.dir}</filename>. +If this variable has not been defined, then a folder called +<filename>${org.jboss.esb.server.deploy.dir}</filename> will be created in the root folder of the +project, containing the .esb file. + </para> + </section> + </section> + + <section> + <title>Dealing with Conformance Issues</title> + <section> + <title>Overview</title> + <para> +Conformance checking can be used to determine whether an ESB configuration, containing +"conversation aware" ESB actions, matches the expected behaviour as defined within a choreography +description (.cdm file). The Eclipse environment will report any conformance issues as errors in +the <emphasis>Problems</emphasis> view. + </para> + <para> +This section will explain the types of conformance errors that may be reported and how to +deal with them. Not all errors, associated with an ESB configuration, will be discussed in this +section. Many errors may be detected that will indicate problems associated with the way that +behaviour has been specified in the configuration file (e.g. conversation type has not been defined). +These are not directly related to conformance. + </para> + </section> + + <section> + <title>Show referenced description</title> + <para> +When an error occurs, related to conformance between the ESB configuration file and a choreography +description, it will have an associated <emphasis>quick fix</emphasis> resolution that can be used +to display the relevant activity being referred to within the choreography description. + </para> + </section> + + <section> + <title>Error: Expecting additional activities as defined in referenced description</title> + <para> +This error message indicates that the reference description contains activities that were not found +in the ESB configuration. + </para> + <para> +This error has an associated <emphasis>quick fix</emphasis> to enable the missing activities to be +inserted in the appropriate location within the ESB configuration. + </para> + +<note><para> +When this resolution is selected, if it displays an error <quote>Could not insert activities found +in referenced description</quote>, this means that it was not possible to insert the additional +activities automatically. +</para></note> + </section> + + <section> + <title>Error: Type mismatch with referenced description, was expecting '...'</title> + <para> +This error occurs when an activity contains a type that does not match with the equivalent activity +in the choreography description. A common example would be an interaction, where the message types +are not compatible. + </para> + + <para> +This error has an associated <emphasis>quick fix</emphasis> to enable the type to be updated in the +relevant activity within the ESB configuration. + </para> + +<note><para> +When this resolution is selected, if it displays an error <quote>Could not update activity with +information from referenced description</quote>, this means that it was not possible to update +the information automatically. +</para></note> + </section> + + <section> + <title>Error: Behaviour not present in referenced description</title> + <para> +This error occurs when there are extra activities within the ESB configuration that do not appear +within the choreography description. + </para> + <para> +This error has an associated <emphasis>quick fix</emphasis> to enable the unwanted activities to be +removed from the ESB configuration. + </para> + +<note><para> +When this resolution is selected, if it displays an error <quote>Could not delete activities from +the model</quote>, this means that it was not possible to delete the activities automatically. +</para></note> + </section> + + <section> + <title>Error: Additional unmatched paths in model</title> + <para> +This error indicates that a grouping contruct (e.g. <emphasis>IfAction</emphasis> or +<emphasis>SwitchAction</emphasis>) in the ESB configuration has +additional paths that do not match the equivalent grouping construct in the choreography description. + </para> + </section> + + <section> + <title>Error: Additional unmatched paths in referenced description</title> + <para> +This error indicates that a grouping contruct (e.g. <emphasis>IfAction</emphasis> or +<emphasis>SwitchAction</emphasis>) in the choreography description has additional paths that do not +match the equivalent grouping construct in the ESB configuration. + </para> + </section> + + </section> + +</chapter> + Added: tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/conversation-validation-with-cdl.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,301 @@ +<?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="conversationvalidationwithcdl"> + <title>Conversation Validation with CDL</title> + <section> + <title>Overview</title> + <para> +Conversation validation is a form of runtime governance concerned with the dynamic behaviour of a system. + </para> + <para> +When coupled with a choreography description model of a system, this means having the ability to ensure that the way a collection of services interact correctly adheres to a description of the business process being enacted. + </para> + <para> +This section introduces the choreography description language (CDL) defined by W3C, and the <emphasis>pi4soa</emphasis> open source project which provides an editor for creating choreography descriptions, as well as utilizing these descriptions for runtime validation and execution purposes. + + </para> + + </section> + + <section> + <title>Configuration of Conversation Validation</title> + + <para> + This section explains how to configure the conversation validation mechanism to validate ESB 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 + 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.soa.overlord.validator.jbossesb.ValidatorFilter"/> + </properties> + ]]></programlisting> + </informalexample> + + <para> +This filter is installed as part of the installation process for the Overlord-CDL distribution. + </para> + </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>overlord-cdl-validator.esb</emphasis> bundle. + </para> + <para> +An example of the contents of this file, that would related to the TrailBlazer example, is: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ + <validator mode="monitor" replyToTimeout="10000" > + <service model="TrailBlazer.cdm" + role="LoanBrokerParticipant" > + <output epr="jms:queue/esb-tb-creditAgencyQueue" /> + <input epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + <output epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <output epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <input epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-customerNotifier" /> + <input epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service model="TrailBlazer.cdm" + role="CreditAgencyParticipant" > + <input epr="jms:queue/esb-tb-creditAgencyQueue" /> + <output epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + </service> + <service model="TrailBlazer.cdm" + role="BankParticipant" > + <input epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <input epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <output epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service model="TrailBlazer.cdm" + role="NotifierParticipant" > + <input epr="jms:queue/esb-tb-customerNotifier" /> + </service> + </validator> + ]]></programlisting> + </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. + </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. + </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. + </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>overlord-cdl-validator.esb</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. + </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:'. + </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. + </para> + + </section> + + <section> + <title>Defining the Validator Configuration within a Choreography</title> + + <para> + The first step to configuring the validator is to associate the endpoint references (EPRs) + against the relevant choreography interactions. This is achieved by defining an + annotation for each 'exchange details' component (i.e. each request and response/notification). + </para> + + <imageobject> + <imagedata fileref="images/editvalidatorann.png" width="5in" /> + </imageobject> + + <para> + When the annotation editor is displayed for the relevant 'exchange details' component, + the <emphasis>jbossesb</emphasis> annotation should be added. This is achieved by + selecting the popup menu associated with the background of the lefthand panel, + and selecting the <emphasis>Add Defined Annotation</emphasis> menu item. + </para> + + <imageobject> + <imagedata fileref="images/editvalidatoranndiag.png" width="5in" /> + </imageobject> + + <para> + When the list of defined annotations is displayed, select the + <emphasis>jbossesb</emphasis> annotation. + </para> + + <imageobject> + <imagedata fileref="images/editvalidatorannselect.png" width="3in" /> + </imageobject> + + <para> + After pressing the <emphasis>Ok</emphasis> button, the annotation editor + will configure the righthand panel with the parameters associated with this + annotation. + </para> + + <imageobject> + <imagedata fileref="images/SVJBossESBAnnotation.jpg" width="5in" /> + </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 + 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. + </para> + + <para> + Once the annotation has been defined, then press the <emphasis>Save</emphasis> + button to save the annotation against the interaction's exchange details. + </para> + + <para> + When all of the relevant 'exchange details' components have been configured with + a <emphasis>jbossesb</emphasis> annotation, defining the EPR to be validated, + then the choreography description file can be copied into the + <filename>overlord-cdl-validator.esb/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. + </para> + + </section> + + </section> + + <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> +The destination defined in this file must match the one configured in the <emphasis>pi4soa.sar/pi4soa.xml</emphasis> file within the server. +</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 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. + </para> + + <imageobject> + <imagedata fileref="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. + </para> + <para> +If any <emphasis>out of sequence</emphasis> or other error situations arise, these are displayed in red. + </para> + </section> + + <section> + <title>Configuration for Conversation Recording</title> + + <para> + As well as validating the interactions between a set of + services, against a pre-defined choreography description, + it is also possible to use the <emphasis>Service Validators</emphasis> + in a non-validating record mode. + </para> + + <para> + This will be useful in situations where a choreography + description does not currently exist, and we wish to + use the stream of business events being sent and received + by each identified service (or participant type) to + gain an understanding of the current business process. + </para> + + <para> + An example of this type of configuration, associated + with the TrailBlazer example, is: + </para> + <informalexample> + <programlisting role="XML" ><![CDATA[ + <validator> + <service role="LoanBrokerParticipant" validate="false" > + <output epr="jms:queue/esb-tb-creditAgencyQueue" /> + <input epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + <output epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <output epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <input epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-customerNotifier" /> + <input epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service role="CreditAgencyParticipant" validate="false" > + <input epr="jms:queue/esb-tb-creditAgencyQueue" /> + <output epr="jms:queue/esb-tb-creditAgencyQueue_reply" /> + </service> + <service role="BankParticipant" validate="false" > + <input epr="jms:queue/esb-tb-jmsBankRequestQueue" /> + <input epr="jms:queue/esb-tb-fileBankRequestQueue" /> + <output epr="jms:queue/esb-tb-jmsBankResponseQueue" /> + <output epr="jms:queue/esb-tb-fileBankResponseQueue" /> + </service> + <service role="NotifierParticipant" validate="false" > + <input epr="jms:queue/esb-tb-customerNotifier" /> + </service> + </validator> + ]]></programlisting> + </informalexample> + + <para> + To define a <emphasis>Service Validator</emphasis> in record + only mode, the <emphasis>model</emphasis> attribute + is not specified (because no choreography description exists + to be validated against), and the optional <emphasis>validate</emphasis> + attribute should be set to <emphasis role="bold">false</emphasis> (by default + this attribute is <emphasis role="bold">true</emphasis>). + </para> + </section> + +</chapter> Added: tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,207 @@ +<?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="overview"> + <title>Overview</title> + + <para> + The CDL component of the Overlord SOA governance project aims to leverage the concept of a choreography (or conversation) + description to provide design-time and run-time governance of an SOA. + </para> + <para> + A Choreography provides the means to describe the service interactions between multiple parties from a global (or service neutral) perspective. + This means that it is possible for an organisation to define how an end-to-end business process should function, regardless of whether orchestrated + or peer-to-peer service collaboration will be used. + </para> + <para> + Although in simple situations, a BPEL process description can provide a description of the interactions between multiple services, this only works where a + single orchestrating process is in control. The benefit of the choreography description is that it can be used to provide a global view of a process across multiple + orchestrated service domains. + </para> + <para> + This document will outline how the Choreography Description is being used as part of Project Overlord to provide SOA governance capabilities + for each phase of the SOA lifecycle. + </para> + <para> + When a validated design has been approved by the users, it can be used to generate an initial skeleton of the implementation for each service. + The current version of Overlord enables a skeleton implementation to be generated as a JBossESB service configuration file, + using 'conversation aware' ESB actions. For more information on these, please see the “Conversational ESB User Guide”. + </para> + + <section> + <title>WS-CDL</title> + + <para> +WS-CDL, or Web Service Choreography Description Language, is a candidate recommendation from W3C. Although associated with W3C and Web Services, it is important to begin by stating that the Choreography Description Language (CDL) is <emphasis role="bold">not</emphasis> web service specific. + </para> + <para> +The purpose of CDL is to enable the interactions between a collection of peer to peer services to be described from a neutral (or global) perspective. This is different to other standards, such as WS-BPEL, that describe interactions from a service specific viewpoint. + </para> + <para> +In essence a choreography description declares roles which will pass messages between each other, called interactions. The interactions are ordered based on a number of structuring mechanism which enables loops, conditional, choices and parallelism to be described. In CDL variables used for messages and for conditionals are all situated at roles. There is no shared state rather there is a precise description of the state at each role and a precise description of how these roles interact in order to reach some notion of common state in which information is exchanged and processed between them. + </para> + <para> +In CDL we use interactions and these structuring mechanisms to describe the observable behaviour, the messages exchanges and the rules for those exchanges and any supporting observable state on which they depend, of a system. + </para> + </section> + + <section> + <title>pi4soa</title> + <para> +<emphasis>pi4soa</emphasis> is an open source project established to demonstrate the potential benefits that a global model (as described using CDL) can provide when building an SOA. The open source project is managed by the Pi4 Technologies Foundation, which is a collaboration between industry and academia. + </para> + <para> +Building complex distributed systems, without introducing unintended consequences, is a real challenge. Although the Choreography Description Language provides a means of describing complex systems at a higher level, and therefore help to reduce such complexity, it does not necessarily guarantee that erronous situations cannot occur due to inappropriately specified interactions. The research, being carried out by members of the Pi4 Technologies Foundation, into the global model and endpoint projection is targeted at identifying potential unintended consequences, to ensure that a global description of a system can be reliably executed and can be free from unintended consequences. + </para> + <para> +The tool suite currently offers the ability to: + </para> + <para> + <itemizedlist> + <listitem> + Define a choreography description + </listitem> + <listitem> + Export the description to a range of other formats, such as BPMN, UML activity/state/sequence models, and HTML + </listitem> + <listitem> + Define scenarios (equivalent to sequence diagrams), with example messages, which can then be simulated against an associated choreography + </listitem> + <listitem> + Generate template endpoint implementations: + <para> + <itemizedlist> + <listitem> + WS-BPEL for deployment in ActiveBPEL + </listitem> + <listitem> + Java stubs for execution with the pi4soa state machine, with deployment options for Apache Axis, J2EE (JBoss, Glassfish) and JBoss ESB + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + </para> + </section> + + <section> + <title> SOA Lifecycle Governance </title> + + <section> + <title>Design Time Governance</title> + <para> + Design-time governance is concerned with ensuring that the resulting system correctly implements requirements (whether functional or non-functional). + A choreography description can be used to ensure that the implemented system meets the behavioural requirements. + </para> + <para> + The behavioural requirements can be captured as a collection of scenarios (e.g. sequence diagrams) with associated example messages. + This enables an unambiguous representation of the business requirements to be stored in a machine processable form, which can subsequently + be used to validate other phases of the SOA lifecycle. + </para> + <para> + Once the choreography description for the SOA has been defined, it can be validated against the scenarios, + to ensure that the choreography correctly handles all of the business requirements. + </para> + <para> + Once the service enters the implementation phase, it is important to ensure that it continues to adhere to the design + and therefore meets the business requirements. Currently this is achieved through the use of techniques such as continuous testing. + However this is only as reliable as the quality of the unit tests that have been written. + </para> + <para> + When a 'structured' implementation language has been used, such as WS-BPEL, jPDL or the new 'conversation aware' ESB actions, + it will be possible to infer the behaviour of the service being implemented, to compare it against the choreography description. + Currently this has been implemented for the “conversation aware” ESB actions, and is demonstrated using the samples in this Overlord-CDL distribution. + </para> + <para> + Detecting incorrectly implemented behaviour at the earliest possible time saves on downstream costs associated with finding and fixing errors. + By using static validation against the original design, it ensures that the implemented service will deliver its expected behaviour first time. + This is important in building large scale SOAs where different services may be implemented in different locations. + </para> + <para> + There are two other areas where a choreography description can be used as part of design-time governance, + that are not currently implemented in Overlord: + </para> + <itemizedlist> + <listitem> + Service lookup – the choreography description can be used to determine if a service already exists in the Service Repository that meets the appropriate behavioural requirements. + </listitem> + <listitem> + Service unit testing - this can be achieved using the scenarios originally specified to document the behavioural requirements. + Rather than develop an independent source of test data, the scenarios can be used to validate the sequence of messages sent to, + and received from, a service, as well as validating the contents of the messages returned from the service under test. + </listitem> + </itemizedlist> + </section> + + <section> + <title>Runtime Governance</title> + <para> + Runtime governance ensures that the SOA executes as expected according to predefined policies. In this context, a choreography description can be used in two ways. + </para> + + <section> + <title> Service validator</title> + <para> + The choreography description represents the interactions between multiple services to deliver a business goal. + To validate the behaviour of each individual service, within the choreography description, the behaviour of each service can be derived from the choreography. + </para> + <para> + The derived behaviour (or “endpoint projection”) of a service can be used within a 'service validator' to monitor the inbound and outbound messages for the service, + to ensure they conform to the expected behaviour. + If an invalid message is detected, it would be possible to block it, to prevent it from causing subsequent problems in downstream systems. + The error can also be reported to a central management capability. + </para> + <para> + The CDL component of Overlord provides the ability to configure service validators to monitor the behaviour of individual services. + An enhanced version of the JBossESB trailblazer example has been included, with the appropriate validator configuration, to demonstrate this mechanism. + </para> + </section> + + <section> + <title>Process correlation</title> + <para> + Validating each service locally can enable errors to be detected quickly, + and the effects of the error prevented from contaminating other systems by blocking the erroneous messages. + </para> + <para> + However local service specific validation may not be adequate to identify errors that would affect the end-to-end business process. + Therefore the message activity at each service validator can be reported to a central 'process correlation engine' which can reconstitute a global view of the business transaction, + and determine if it matches the expected behaviour as defined in the choreography description. + </para> + <para> + The benefit of a correlated global view of the distributed business transaction is that it can be further analysed to ensure other governance polices have been followed – e.g. SLAs. + </para> + <para> + The pi4soa tool suite includes a simple GUI based monitoring tool to display the information obtained from correlating message events associated with individual services. + The trailblazer example has been written to cause out of sequence messages under certain circumstances. See the “Samples Guide” for more information on how to run this example. + </para> + </section> + </section> + </section> + + <section> + <title> First Steps </title> + <para>The first step will be to follow the instructions in the Getting Started Guide to install Overlord. </para> + <para> Once installed, the next step should be to try out the examples in the samples folder. The examples consistent of:</para> + <itemizedlist> + <listitem> + Service Validation related examples + <para> + The samples folder contains an enhanced version of the trailblazer example from the JBossESB, with the addition of a File Based Bank, and message content including a conversation id to enable the messages to be correlated with a specific session. + </para> + </listitem> + <listitem> + Conversation aware ESB actions, with conformance checking against Choreography + <para> + Two examples have been included, one simple example (purchasing) and the other more advanced (brokerage). Both relate to the business process of purchasing items. The second example introduces the concept of a broker to act on behalf of the customer, interacting with multiple potential suppliers. + </para> + <para> + These examples show how a service implementation (built using “conversation aware ESB actions” in this case), can be continuously checked for conformance against a choreography description. + </para> + <para> + The final step should be to review all of the documents in the docs folder to understand more about each capability, and then try using the techniques on your own project. + </para> + </listitem> + </itemizedlist> + </section> +</chapter> Added: tools/eclipse/trunk/docs/userguide/src/main/xslt/pdf.xsl =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/xslt/pdf.xsl (rev 0) +++ tools/eclipse/trunk/docs/userguide/src/main/xslt/pdf.xsl 2009-11-24 23:47:13 UTC (rev 91) @@ -0,0 +1,91 @@ +<?xml version="1.0" encoding="UTF-8"?> +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" + xmlns:fo="http://www.w3.org/1999/XSL/Format" + version="1.0"> + + <xsl:import href="http://docbook.sourceforge.net/release/xsl/1.72.0/fo/docbook.xsl" /> + <xsl:import href="classpath:/xslt/org/jboss/pdf.xsl" /> + +  + <xsl:param name="body.font.family" select="'Times New Roman, serif'" /> + <xsl:param name="monospace.font.family" select="'DejaVu Sans Mono, monospace'" /> + <xsl:param name="sans.font.family" select="'Arial, sans-serif'" /> + <xsl:param name="title.font.family" select="$body.font.family" /> + <xsl:param name="programlisting.font" select="$monospace.font.family" /> + <xsl:param name="programlisting.font.size" select="'75%'" /> + +  + <xsl:param name="double.sided" select="0" /> + +  + <xsl:param name="callout.graphics" select="1" /> + <xsl:param name="callout.graphics.extension" select="'.svg'" /> + +  + <xsl:param name="ulink.show" select="0"/> + +  + <xsl:attribute-set name="xref.properties"> + <xsl:attribute name="font-style">normal</xsl:attribute> + </xsl:attribute-set> + +  + <xsl:attribute-set name="monospace.properties"> + <xsl:attribute name="font-size">1em</xsl:attribute> + <xsl:attribute name="font-family"> + <xsl:value-of select="$monospace.font.family"/> + </xsl:attribute> + </xsl:attribute-set> + +  + <xsl:template match="callout"> + <xsl:variable name="id"><xsl:call-template name="object.id"/></xsl:variable> + <fo:list-item id="{$id}" space-before="1em"> + <fo:list-item-label end-indent="label-end()"> + <fo:block> + <xsl:call-template name="callout.arearefs"> + <xsl:with-param name="arearefs" select="@arearefs"/> + </xsl:call-template> + </fo:block> + </fo:list-item-label> + <fo:list-item-body start-indent="body-start()"> + <fo:block padding-top="0.2em"> + <xsl:apply-templates/> + </fo:block> + </fo:list-item-body> + </fo:list-item> + </xsl:template> + +  + <xsl:template name="callout-bug"> + <xsl:param name="conum" select='1'/> + <xsl:choose> + <xsl:when test="$conum <= $callout.graphics.number.limit"> + <xsl:variable name="filename" + select="concat($callout.graphics.path, $conum, + $callout.graphics.extension)"/> + + <fo:external-graphic content-width="{$callout.icon.size}" + width="{$callout.icon.size}" + padding="0.0em" margin="0.0em" + baseline-shift="-0.375em"> + <xsl:attribute name="src"> + <xsl:choose> + <xsl:when test="$passivetex.extensions != 0 + or $fop.extensions != 0 + or $arbortext.extensions != 0"> + <xsl:value-of select="$filename"/> + </xsl:when> + <xsl:otherwise> + <xsl:text>url(</xsl:text> + <xsl:value-of select="$filename"/> + <xsl:text>)</xsl:text> + </xsl:otherwise> + </xsl:choose> + </xsl:attribute> + </fo:external-graphic> + </xsl:when> + </xsl:choose> + </xsl:template> +</xsl:stylesheet> +

14 years, 4 months

1
0
0 / 0

savara SVN: r90 - in methodology/trunk: gettingstartedguide/src/main/module and 1 other directory.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-24 16:53:27 -0500 (Tue, 24 Nov 2009) New Revision: 90 Removed: methodology/trunk/tooling/ Modified: methodology/trunk/ methodology/trunk/gettingstartedguide/src/main/module/installation.xml methodology/trunk/gettingstartedguide/src/main/module/soagwithcdl.xml Log: Remove service modeler - this needs to remain in overlord. Property changes on: methodology/trunk ___________________________________________________________________ Name: svn:ignore + .project Modified: methodology/trunk/gettingstartedguide/src/main/module/installation.xml =================================================================== --- methodology/trunk/gettingstartedguide/src/main/module/installation.xml 2009-11-24 21:41:13 UTC (rev 89) +++ methodology/trunk/gettingstartedguide/src/main/module/installation.xml 2009-11-24 21:53:27 UTC (rev 90) @@ -18,22 +18,18 @@ <section> <title>Prerequisites</title> <orderedlist> - <listitem>JBossAS (version 4.2.3.GA or higher), available from <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbossas</ulink></listitem> - <listitem>JBossESB (version 4.5.GA or higher), should download the <emphasis role="bold">jbossesb-4.5.GA.zip</emphasis>, available from <ulink url="http://www.jboss.org/jbossesb">http://www.jboss.org/jbossesb</ulink></listitem> - <listitem>Overlord CDL (version 1.0-M1 or higher), available from <ulink url="http://www.jboss.org/overlord">http://www.jboss.org/overlord</ulink></listitem> - <listitem> - pi4soa (version 2.0.0 or higher), available from <ulink url="http://pi4soa.wiki.sourceforge.net/download">http://pi4soa.wiki.sourceforge.net/download</ulink> - <note> - <para> - It is recommended that a pre-packaged version is used, which includes all of the necessary Eclipse related plugins. - However the plugins can be installed separately into an existing Eclipse environment by following the instructions on the <ulink url="http://www.pi4soa.org">http://www.pi4soa.org</ulink> download wiki. - </para> - </note> - </listitem> - <listitem> - Ant, available from <ulink url="http://ant.apache.org/">http://ant.apache.org</ulink> - </listitem> - </orderedlist> + <listitem>JBossAS (version 5.1.0.GA or higher), available from <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbossas</ulink></listitem> + <listitem>JBossESB (version 4.6.GA or higher), should download the <emphasis role="bold">jbossesb-4.5.GA.zip</emphasis>, available from <ulink url="http://www.jboss.org/jbossesb">http://www.jboss.org/jbossesb</ulink></listitem> + <listitem>SAVARA (version 1.0-M1 or higher), available from <ulink url="http://www.jboss.org/savara">http://www.jboss.org/savara</ulink></listitem> + <listitem>pi4soa (version 3.0.0 or higher), available as part of JBoss Tools from + <ulink url="http://www.jboss.org/tools">http://www.jboss.org/tools</ulink> + <note> + <para> + pi4soa is bundled as part of JBossTools 3.1.CR1 or greater. + </para> + </note></listitem> + <listitem>Ant, available from <ulink url="http://ant.apache.org/">http://ant.apache.org</ulink></listitem> + </orderedlist> </section> <section> Modified: methodology/trunk/gettingstartedguide/src/main/module/soagwithcdl.xml =================================================================== --- methodology/trunk/gettingstartedguide/src/main/module/soagwithcdl.xml 2009-11-24 21:41:13 UTC (rev 89) +++ methodology/trunk/gettingstartedguide/src/main/module/soagwithcdl.xml 2009-11-24 21:53:27 UTC (rev 90) @@ -84,14 +84,392 @@ <title>Design Time Governance With WS-BPEL</title> <para> -This milestone release includes a basic capability to generate a service implementation, for a participant in a choreography, using WS-BPEL. +This tools include a capability to generate a service implementation, for a participant in a choreography, +using WS-BPEL. A completed version of the <emphasis>PurchasingGoods</emphasis> example can be +found in the samples directory (which can be imported into Eclipse). </para> <para> -Subsequent milestone releases will include more capabilities as part of the service generation, including the generation of WSDL, as well as supporting conformance checking back against the choreography description. - </para> - <para> +However if you wish to generate the example from scratch, the follow the instructions in this section. More information about how to use this feature can be found in the User Guide. </para> + + <section> + <title>Generating WS-BPEL based Services</title> + + <para> +When a choreography description has been created, it is possible to generate a BPEL Process (and associated +WSDL files and deployment descriptor) for each of the participants defined within the choreography. +To try this out, select the <emphasis>Savara->Generate->WS-BPEL</emphasis> menu item from the popup menu +associated with the <filename>PurchaseGoods.cdm</filename>. + </para> + + <imageobject> + <imagedata fileref="images/GenerateBPELMenu.jpg" align="center" width="3in" /> + </imageobject> + + <para> +This will display a dialog listing the possible services that can be generated from this choreography, +with a proposed Eclipse project name. + </para> + + <imageobject> + <imagedata fileref="images/GenerateBPELDialog.jpg" align="center" width="3in" /> + </imageobject> + + <para> +To test out this feature, uncheck the <emphasis>Buyer</emphasis> participant, leave the build system +as <emphasis>Ant</emphasis>, select the messaging system appropriate for your target environment and +press the 'Ok' button. This will create a single new project for the <emphasis>Store</emphasis> and +<emphasis>CreditAgency</emphasis> participants. + </para> + + <para> +Each project will contain a single <filename>bpel</filename> folder containing the WS-BPEL process +definition for the participant, a list of relevant WSDL files and a deployment descriptor file +for use with RiftSaw. Howeve the WS-BPEL and WSDL files are standard, so can be deployed to any +WS-BPEL 2.0 compliant engine. + </para> + + <imageobject> + <imagedata fileref="images/GenerateBPELNav.jpg" align="center" width="2in" /> + </imageobject> + + </section> + + <section> + <title>Adding implementation details to CreditAgency</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</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:pur="http://www.jboss.org/examples/purchasing" + 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="CreditAgencyPartnerLinkTypes.wsdl" + namespace="http://www.jboss.org/examples/creditAgency"/> + <partnerLinks> + <partnerLink myRole="CreditAgencyService" name="StoreToCreditAgency" + partnerLinkType="ca:StoreToCreditAgencyServiceLT"/> + </partnerLinks> + <variables> + <variable messageType="ca:CreditCheckRequest" name="creditCheckRequestVar"/> + <variable messageType="ca:CreditCheckOk" name="creditCheckOkVar"/> + <variable messageType="ca:CreditCheckInvalid" name="creditCheckInvalidVar"/> + </variables> + <sequence> + <receive createInstance="yes" operation="checkCredit" + partnerLink="StoreToCreditAgency" portType="ca:CreditAgencyInterface" + variable="creditCheckRequestVar"/> + <if> + <sequence> + <reply operation="checkCredit" partnerLink="StoreToCreditAgency" + portType="ca:CreditAgencyInterface" variable="creditCheckOkVar"/> + </sequence> + <else> + <sequence> + <reply faultName="ca:CreditCheckFailed" 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> + <condition> + $creditCheckRequestVar.CreditCheckRequest/pur:amount <= 500 + </condition> + .... + ]]></programlisting> + </informalexample> + + <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"> + <copy> + <from>$creditCheckRequestVar.CreditCheckRequest</from> + <to>$creditCheckOkVar.CreditCheckOk</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"> + <copy> + <from>$creditCheckRequestVar.CreditCheckRequest</from> + <to>$creditCheckInvalidVar.CreditCheckInvalid</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</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:pur="http://www.jboss.org/examples/purchasing" + 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="StorePartnerLinkTypes.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:CreditCheckRequest" name="creditCheckRequestVar"/> + <variable messageType="ca:CreditCheckOk" name="creditCheckOkVar"/> + <variable messageType="sto:BuyConfirmed" name="buyConfirmedVar"/> + <variable messageType="sto:BuyFailed" name="buyFailedVar"/> + </variables> + <sequence> + <receive createInstance="yes" operation="buy" partnerLink="BuyerToStore" + portType="sto:StoreInterface" variable="buyRequestVar"/> + <scope> + <faultHandlers> + <catch faultMessageType="ca:CreditCheckInvalid" + faultName="ca:CreditCheckFailed" faultVariable="creditCheckInvalidVar"> + <sequence> + <reply faultName="sto:BuyFailed" operation="buy" + partnerLink="BuyerToStore" portType="sto:StoreInterface" + variable="buyFailedVar"/> + </sequence> + </catch> + </faultHandlers> + <sequence> + <invoke inputVariable="creditCheckRequestVar" operation="checkCredit" + outputVariable="creditCheckOkVar" partnerLink="StoreToCreditAgency" + portType="ca:CreditAgencyInterface"/> + <reply 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"> + <copy> + <from>$creditCheckInvalidVar.CreditCheckInvalid</from> + <to>$buyFailedVar.BuyFailed</to> + </copy> + </assign> + ]]></programlisting> + </informalexample> + + <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"> + <copy> + <from>$buyRequestVar.BuyRequest</from> + <to>$creditCheckRequestVar.CreditCheckRequest</to> + </copy> + </assign> + <invoke inputVariable="creditCheckRequestVar" operation="checkCredit" + outputVariable="creditCheckOkVar" partnerLink="StoreToCreditAgency" + portType="ca:CreditAgencyInterface"/> + <assign name="CopyPurchaseDetails"> + <copy> + <from>$creditCheckOkVar.CreditCheckOk</from> + <to>$buyConfirmedVar.BuyConfirmed</to> + </copy> + </assign> + ]]></programlisting> + </informalexample> + + </section> + </section> + </section> <section>

14 years, 4 months

1
0
0 / 0

savara SVN: r89 - in tools/eclipse/trunk: docs and 9 other directories.

by do-not-reply＠jboss.org

Author: objectiser Date: 2009-11-24 16:41:13 -0500 (Tue, 24 Nov 2009) New Revision: 89 Added: tools/eclipse/trunk/docs/ tools/eclipse/trunk/docs/gettingstartedguide/ tools/eclipse/trunk/docs/gettingstartedguide/pom.xml tools/eclipse/trunk/docs/gettingstartedguide/src/ tools/eclipse/trunk/docs/gettingstartedguide/src/main/ tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ChoreoMonReady.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckError.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckErrorMessage.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckErrorMessageMenu.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesDialog.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesMenu.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesNav.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportDialog.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportFileDialog.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportMenu.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportProjectsDialog.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportedProjects.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/InvalidPurchasePostTest.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/JavaCompiler1-5Compliant.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/MonitorMenu.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/PurchaseGoods.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/QuickFixDialog.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBAnnotation.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBAnnotationToolTip.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBEditAnnotation.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ShowReferencedDescription.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SuccessfulPurchasePostTest.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SuccessfulPurchasePreTest.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/TrailBlazerMonitorError.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/TrailblazerWebPage.jpg tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/author_group.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/installation.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/overview.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/runtimevalidation.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/serviceanalysisdesign.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/servicedev.xml tools/eclipse/trunk/docs/gettingstartedguide/src/main/xslt/ tools/eclipse/trunk/docs/gettingstartedguide/src/main/xslt/pdf.xsl tools/eclipse/trunk/docs/pom.xml tools/eclipse/trunk/docs/userguide/ tools/eclipse/trunk/docs/userguide/src/ tools/eclipse/trunk/docs/userguide/src/main/ tools/eclipse/trunk/docs/userguide/src/main/images/ tools/eclipse/trunk/docs/userguide/src/main/module/ tools/eclipse/trunk/docs/userguide/src/main/xslt/ tools/eclipse/trunk/pom.xml Log: Added tool getting started guide, and template structure for user guide. Added: tools/eclipse/trunk/docs/gettingstartedguide/pom.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/pom.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/pom.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,86 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + + <modelVersion>4.0.0</modelVersion> + + <groupId>org.jboss.savara.tools.eclipse.docs</groupId> + <artifactId>gettingstartedguide</artifactId> + <packaging>jdocbook</packaging> + <name>Savara::Tools::Eclipse::Docs::GettingStartedGuide</name> + + <parent> + <groupId>org.jboss.savara.tools.eclipse</groupId> + <artifactId>docs</artifactId> + <version>1.0-SNAPSHOT</version> + </parent> + + + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.1.2</version> + <extensions>true</extensions> + <executions> + <execution> + <id>generate-docbook</id> + <phase>package</phase> + <goals> + <goal>resources</goal> + <goal>generate</goal> + </goals> + </execution> + </executions> + <dependencies> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-docbook-xslt</artifactId> + <version>1.1.0</version> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.0</version> + <type>jdocbook-style</type> + </dependency> + </dependencies> + <configuration> + <sourceDocumentName>master.xml</sourceDocumentName> + <sourceDirectory>${basedir}/src/main</sourceDirectory> + <imageResource> + <directory>${basedir}/src/main</directory> + <includes> + <include>images/**/*</include> + </includes> + </imageResource> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource>file:///${basedir}/src/main/xslt/pdf.xsl</stylesheetResource> + <finalName>GettingStartedGuide.pdf</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <xincludeSupported>true</xincludeSupported> + <xmlTransformerType>saxon</xmlTransformerType> + <docbookVersion>1.72.0</docbookVersion> + </options> + </configuration> + </plugin> + </plugins> + </build> + + +</project> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ChoreoMonReady.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ChoreoMonReady.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckError.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckError.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckErrorMessage.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckErrorMessage.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckErrorMessageMenu.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ConformanceCheckErrorMessageMenu.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesDialog.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesDialog.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesMenu.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesMenu.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesNav.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/GenerateESBServicesNav.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportDialog.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportDialog.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportFileDialog.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportFileDialog.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportMenu.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportMenu.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportProjectsDialog.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportProjectsDialog.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportedProjects.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ImportedProjects.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/InvalidPurchasePostTest.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/InvalidPurchasePostTest.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/JavaCompiler1-5Compliant.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/JavaCompiler1-5Compliant.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/MonitorMenu.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/MonitorMenu.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/PurchaseGoods.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/PurchaseGoods.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/QuickFixDialog.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/QuickFixDialog.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBAnnotation.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBAnnotation.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBAnnotationToolTip.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBAnnotationToolTip.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBEditAnnotation.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SVJBossESBEditAnnotation.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ShowReferencedDescription.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/ShowReferencedDescription.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SuccessfulPurchasePostTest.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SuccessfulPurchasePostTest.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SuccessfulPurchasePreTest.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/SuccessfulPurchasePreTest.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/TrailBlazerMonitorError.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/TrailBlazerMonitorError.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/TrailblazerWebPage.jpg =================================================================== (Binary files differ) Property changes on: tools/eclipse/trunk/docs/gettingstartedguide/src/main/images/TrailblazerWebPage.jpg ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/master.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % RH-ENTITIES SYSTEM "Common_Config/rh-entities.ent"> +]> + +<book lang="en"> + <bookinfo> + <title>SAVARA Eclipse Tools 1.0-SNAPSHOT</title> + <subtitle>Getting Started Guide</subtitle> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/author_group.xml"/> + </bookinfo> + + <toc/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/overview.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/installation.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/businessanalysis.xml"/> +  + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/servicedev.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/runtimevalidation.xml"/> +</book> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/author_group.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/author_group.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/author_group.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,7 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup> + <corpauthor>Gary Brown</corpauthor> + <corpauthor>Jeff Yu</corpauthor> +</authorgroup> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/businessanalysis.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,121 @@ +<?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="businessanalysis"> + <title>Business Analysis</title> + + <para> + </para> + + <section> + <title>Defining Requirements</title> + + <para> +When designing a system, it is necessary to capture requirements. Various approaches can be +used for this, but currently there are no mechanisms that enable the requirements to be +documented in such a way to enable an implementation to be validated back against the requirements. + </para> + + <para> +The pi4soa tools provide a means of describing requirements, representing specific use cases +for the interactions between a set of cooperating services, using scenarios - which can be +considered similar to UML sequence diagrams that have been enhanced to include example messages. + </para> + + <para> +In the <filename>purchasing-models</filename> Eclipse project, the +<filename>SuccessfulPurchase.scn</filename> scenario looks like this: + </para> + + <imageobject> + <imagedata fileref="images/SuccessfulPurchasePreTest.jpg" align="center" width="5in" /> + </imageobject> + + <para> + The business requirements can therefore defined as a set of scenarios, each demonstrating + a specific use-case, or path through the business process being enacted. + </para> + + </section> + + <section> + <title>Creating a Global Model</title> + + <para> +The next step in the development process is to specific a Global Model to implement +the requirements described within the set of scenarios. + </para> + + <para> +The current representation used to define Global Models within SAVARA is the W3C Web Service +Choreography Description Language (WS-CDL). The pi4soa tools provide a WS-CDL (or choreography +description) editor. Although this standard is associated with web services, it does not mean +that a system specified using this standard needs to be implemented using web services. The +actual WS-CDL language is used for defining the interactions between any distributed system. + </para> + + <para> +The choreography description for the Purchasing example can be found in +<filename>purchasing-models/PurchaseGoods.cdm</filename>. When the +choreography editor has been launched, by double-clicking on this file within the Eclipse +environment, then navigate to the <emphasis>Choreography Flows</emphasis> tab to see the +definition of the purchasing process: + </para> + + <imageobject> + <imagedata fileref="images/PurchaseGoods.jpg" align="center" width="5in" /> + </imageobject> + + </section> + + <section> + <title>Validating Requirements against Global Model</title> + + <para> +The pi4soa tools can be used to test the scenarios against the choreography description, to +ensure that the choreography correctly implements the requirements. To test the +<filename>SuccessfulPurchase.scn</filename> scenario against the choreography, launch +the scenario editor by double-clicking on the scenario file, and then pressing the +green <emphasis>play</emphasis> button in the toolbar. When complete, the scenario +should look like the following image, indicating that the scenario completed successfully. + </para> + + <imageobject> + <imagedata fileref="images/SuccessfulPurchasePostTest.jpg" align="center" width="5in" /> + </imageobject> + + <para> +To view a scenario that demonstrates a test failure, open the +<filename>InvalidPurchase.scn</filename> scenario by double-clicking on the file, and +then initiate the test using the green <emphasis>play</emphasis> button in the toolbar. +When complete, the scenario should look like the following image. + </para> + + <imageobject> + <imagedata fileref="images/InvalidPurchasePostTest.jpg" align="center" width="5in" /> + </imageobject> + + <para> +You will notice that the <emphasis>Store</emphasis> participant has a red 'send' node, +indicating that this action was not expected behaviour when compared with the choreography +description. The reason this is considered an error, is that the <emphasis>Store</emphasis> +participant should only send a <emphasis>BuyFailed</emphasis> message following an invalid +credit check. + </para> + + <para> +When an error is detected in a scenario, the choreography designer can then determine whether +the scenario is wrong (i.e. it does not correctly describe a business requirement), or whether +the choreography is wrong and needs to be updated to accomodate the scenario. + </para> + + <para> +Once the choreography description has been successfully tested against the scenarios, the +next step may be to obtain approval to proceed to the analysis/design phase. To help support +this effort, the pi4soa tools provide the means to export the choreography description to +a range of representations (e.g. BPMN, UML or HTML documentation +<emphasis>TO BE CONFIRMED</emphasis>). + </para> + </section> + +</chapter> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/installation.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/installation.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/installation.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,121 @@ +<?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="installation"> + <title>Installation</title> + + <para> + This section describes the installation procedure for the SAVARA Eclipse Tools. + </para> + + <section> + <title>Prerequisites</title> + <para> + 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 Eclipse Tools (version 1.0-M1 or higher), available from <ulink url="http://www.jboss.org/savara">http://www.jboss.org/savara</ulink></listitem> + <listitem>JBoss Tools (3.1 or higher) <ulink url="http://www.jboss.org/tools">http://www.jboss.org/tools</ulink> + available from an update site</listitem> + </orderedlist> + </section> + + <section> + <title>Installation Instructions</title> + <para> + The installation instructions for the SAVARA Eclipse Tools are: + </para> + <orderedlist> + <listitem> + Eclipse + <para> + Download the latest version of Eclipse JEE, and install in your environment. + </para> + </listitem> + + <listitem> + JBoss Tools + <para> + Start up your Eclipse environment, and go to the <emphasis>Help->Install New Software..</emphasis> + menu item. Select the appropriate update site URL from the JBoss Tools download + page, and enter it into the top text field in the dialog window, and press the + <emphasis>Add</emphasis> button. Once the contents of the update site is available, + then select the appropriate components and follow the instructions to install + them within your Eclipse environment. + </para> + </listitem> + + <listitem> + Install SAVARA Eclipse plugins + <para> + Start up your Eclipse environment, and go to the + <emphasis>Help->Install New Software..</emphasis>. Instead of entering a URL, + just press the <emphasis>Add</emphasis> button and then when the dialog + window is displayed, select the <emphasis>Local</emphasis> button. Select + the location of the local update site within the SAVARA Eclipse Tools + distribution. Again, as with the previous step, follow the instructions provided + by the Eclipse update manager to complete the installation. + </para> + </listitem> + + </orderedlist> + </section> + + <section> + <title>Importing Samples into Eclipse</title> + + <para> + Once the SAVARA Eclipse Tool distribution has been correctly installed, if you wish to try out + any of the examples then the following steps should be followed to import the relevant + projects into the previously configured Eclipse environment. + </para> + + <orderedlist> + <listitem> + <para> +Select the 'Import...' menu item, associated with the popup menu on the background of the left +panal (Navigator or Package depending on perspective being viewed). + </para> + <imageobject> + <imagedata fileref="images/ImportMenu.jpg" align="center" width="2in" /> + </imageobject> + </listitem> + <listitem> + <para> +When the import dialog appears, select the <emphasis>General->ExistingProject from Workspace</emphasis> +option and press the 'Next' button. + </para> + <imageobject> + <imagedata fileref="images/ImportDialog.jpg" align="center" width="4in" /> + </imageobject> + </listitem> + <listitem> + <para> +Ensuring that the 'Select root directory' radio button is selected, press the 'Browse' button and +navigate to the <filename>${SAVARA-Tools}/samples</filename> folder, then press 'Ok'. + </para> + <imageobject> + <imagedata fileref="images/ImportFileDialog.jpg" align="center" width="3in" /> + </imageobject> + </listitem> + <listitem> + <para> +All of the Eclipse projects contained within the <filename>samples</filename> directory structure +will be listed. Press the 'Finish' button to import them all. + </para> + <imageobject> + <imagedata fileref="images/ImportProjectsDialog.jpg" align="center" width="4in" /> + </imageobject> + <para> + Once imported, the Eclipse navigator will list the sample projects: + </para> + <imageobject> + <imagedata fileref="images/ImportedProjects.jpg" align="center" width="2in" /> + </imageobject> + </listitem> + </orderedlist> + + </section> + +</chapter> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/overview.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/overview.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/overview.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,38 @@ +<?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="overview"> + <title>Overview</title> + + <para> + This is the Getting Started Guide for the SAVARA Eclipse Tools. + </para> + + <para> + This guide starts with the installation instructions for the SAVARA Eclipse Tools. + </para> + + <para> + The remainder of the document is organised to reflect phases within the SAVARA + Methodology, and how the current tools can be used in support of that methodology. + The tools are still in development, and therefore not all phases will have tools, + and the tools in some phases will not necessarily be complete. + </para> + + <para> + As an overview, the tools currently include capabilities for: + </para> + + <itemizedlist> + <listitem>Definition of business requirements as scenarios</listitem> + <listitem>Creation of a choreography (global model) to represent the architecture for a system + that delivers the requirements</listitem> + <listitem>Generation of documentation based on the choreography</listitem> + <listitem>Generation of service implementation using WS-BPEL</listitem> + <listitem>Conformance checking a WS-BPEL service implementation against a choreography</listitem> + <listitem>Generation of service implementation using "conversation aware" ESB actions</listitem> + <listitem>Conformance checking a "conversation aware" ESB service implementation against a choreography</listitem> + <listitem>Runtime validation of an ESB service against a choreography description</listitem> + </itemizedlist> + +</chapter> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/runtimevalidation.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/runtimevalidation.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/runtimevalidation.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,225 @@ +<?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="runtimevalidation"> + <title>Runtime Validation</title> + + <note> + <para> + Before you can deploy and run the runtime validation example, you will + need to install the SAVARA Validator module for JBossESB. + </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-Validator 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-Validator}/samples/trailblazer</filename> folder and the <filename>trailblazer-models</filename> Eclipse project. + </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. + </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). + </para> + + <imageobject> + <imagedata fileref="images/SVJBossESBEditAnnotation.jpg" align="center" width="3in" /> + </imageobject> + + <para> +This will display the annotation editor, with the single configured annotation called 'jbossesb'. 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). + </para> + + <imageobject> + <imagedata fileref="images/SVJBossESBAnnotation.jpg" 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: + </para> + + <imageobject> + <imagedata fileref="images/SVJBossESBAnnotationTooltip.jpg" align="center" width="3in" /> + </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. + </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. + </para> + </note> + + </section> + + <section> + <title>Deploy the TrailBlazer 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/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: + </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. + </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. + </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. + </para> + + <imageobject> + <imagedata fileref="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="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="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-Validator}/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="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> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/serviceanalysisdesign.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/serviceanalysisdesign.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/serviceanalysisdesign.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,20 @@ +<?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="serviceanalysisdesign"> + <title>Service Oriented Analysis and Design</title> + + <para> + </para> + + <section> + <title>Service Oriented Analysis</title> + + </section> + + <section> + <title>Service Oriented Design</title> + + </section> + +</chapter> Added: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/servicedev.xml =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/servicedev.xml (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/servicedev.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,627 @@ +<?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="servicedev"> + <title>Service Development</title> + + <para> +Services can be developed by generating initial development artifacts, based on artifacts +created in preceding phases (e.g. global model or service contracts/designs). + </para> + + <para> +To ensure that the services continue to conform to the artifacts defined in the previous +phases, the tools perform conformance checking between the service implementation and +the existing architecture/design artifacts. This is not possible with all implementation +languages - they must provide the means to extract the communication structure for +comparison. + </para> + + <para> +The following sections explain how the generation and conformance checking can be achieved +for two implementation languages, WS-BPEL and a "conversation aware" ESB actions (a custom +extension to the JBossESB action language). + </para> + + <section> + <title>WS-BPEL</title> + + <para> +This tools include a capability to generate a service implementation, for a participant in a choreography, +using WS-BPEL. A completed version of the <emphasis>PurchasingGoods</emphasis> example can be +found in the samples directory (which can be imported into Eclipse). + </para> + + <para> +However if you wish to generate the example from scratch, the follow the instructions in this section. +More information about how to use this feature can be found in the User Guide. + </para> + + <section> + <title>Generating WS-BPEL based Services</title> + + <para> +When a choreography description has been created, it is possible to generate a BPEL Process (and associated +WSDL files and deployment descriptor) for each of the participants defined within the choreography. +To try this out, select the <emphasis>Savara->Generate->WS-BPEL</emphasis> menu item from the popup menu +associated with the <filename>PurchaseGoods.cdm</filename>. + </para> + + <imageobject> + <imagedata fileref="images/GenerateBPELMenu.jpg" align="center" width="3in" /> + </imageobject> + + <para> +This will display a dialog listing the possible services that can be generated from this choreography, +with a proposed Eclipse project name. + </para> + + <imageobject> + <imagedata fileref="images/GenerateBPELDialog.jpg" align="center" width="3in" /> + </imageobject> + + <para> +To test out this feature, uncheck the <emphasis>Buyer</emphasis> participant, leave the build system +as <emphasis>Ant</emphasis>, select the messaging system appropriate for your target environment and +press the 'Ok' button. This will create a single new project for the <emphasis>Store</emphasis> and +<emphasis>CreditAgency</emphasis> participants. + </para> + + <para> +Each project will contain a single <filename>bpel</filename> folder containing the WS-BPEL process +definition for the participant, a list of relevant WSDL files and a deployment descriptor file +for use with RiftSaw. Howeve the WS-BPEL and WSDL files are standard, so can be deployed to any +WS-BPEL 2.0 compliant engine. + </para> + + <imageobject> + <imagedata fileref="images/GenerateBPELNav.jpg" align="center" width="2in" /> + </imageobject> + + </section> + + <section> + <title>Adding implementation details to CreditAgency</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:pur="http://www.jboss.org/examples/purchasing" + 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="CreditAgencyPartnerLinkTypes.wsdl" + namespace="http://www.jboss.org/examples/creditAgency"/> + <partnerLinks> + <partnerLink myRole="CreditAgencyService" name="StoreToCreditAgency" + partnerLinkType="ca:StoreToCreditAgencyServiceLT"/> + </partnerLinks> + <variables> + <variable messageType="ca:CreditCheckRequest" name="creditCheckRequestVar"/> + <variable messageType="ca:CreditCheckOk" name="creditCheckOkVar"/> + <variable messageType="ca:CreditCheckInvalid" name="creditCheckInvalidVar"/> + </variables> + <sequence> + <receive createInstance="yes" operation="checkCredit" + partnerLink="StoreToCreditAgency" portType="ca:CreditAgencyInterface" + variable="creditCheckRequestVar"/> + <if> + <sequence> + <reply operation="checkCredit" partnerLink="StoreToCreditAgency" + portType="ca:CreditAgencyInterface" variable="creditCheckOkVar"/> + </sequence> + <else> + <sequence> + <reply faultName="ca:CreditCheckFailed" 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> + <condition> + $creditCheckRequestVar.CreditCheckRequest/pur:amount <= 500 + </condition> + .... + ]]></programlisting> + </informalexample> + + <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"> + <copy> + <from>$creditCheckRequestVar.CreditCheckRequest</from> + <to>$creditCheckOkVar.CreditCheckOk</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"> + <copy> + <from>$creditCheckRequestVar.CreditCheckRequest</from> + <to>$creditCheckInvalidVar.CreditCheckInvalid</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:pur="http://www.jboss.org/examples/purchasing" + 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="StorePartnerLinkTypes.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:CreditCheckRequest" name="creditCheckRequestVar"/> + <variable messageType="ca:CreditCheckOk" name="creditCheckOkVar"/> + <variable messageType="sto:BuyConfirmed" name="buyConfirmedVar"/> + <variable messageType="sto:BuyFailed" name="buyFailedVar"/> + </variables> + <sequence> + <receive createInstance="yes" operation="buy" partnerLink="BuyerToStore" + portType="sto:StoreInterface" variable="buyRequestVar"/> + <scope> + <faultHandlers> + <catch faultMessageType="ca:CreditCheckInvalid" + faultName="ca:CreditCheckFailed" faultVariable="creditCheckInvalidVar"> + <sequence> + <reply faultName="sto:BuyFailed" operation="buy" + partnerLink="BuyerToStore" portType="sto:StoreInterface" + variable="buyFailedVar"/> + </sequence> + </catch> + </faultHandlers> + <sequence> + <invoke inputVariable="creditCheckRequestVar" operation="checkCredit" + outputVariable="creditCheckOkVar" partnerLink="StoreToCreditAgency" + portType="ca:CreditAgencyInterface"/> + <reply 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"> + <copy> + <from>$creditCheckInvalidVar.CreditCheckInvalid</from> + <to>$buyFailedVar.BuyFailed</to> + </copy> + </assign> + ]]></programlisting> + </informalexample> + + <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"> + <copy> + <from>$buyRequestVar.BuyRequest</from> + <to>$creditCheckRequestVar.CreditCheckRequest</to> + </copy> + </assign> + <invoke inputVariable="creditCheckRequestVar" operation="checkCredit" + outputVariable="creditCheckOkVar" partnerLink="StoreToCreditAgency" + portType="ca:CreditAgencyInterface"/> + <assign name="CopyPurchaseDetails"> + <copy> + <from>$creditCheckOkVar.CreditCheckOk</from> + <to>$buyConfirmedVar.BuyConfirmed</to> + </copy> + </assign> + ]]></programlisting> + </informalexample> + + </section> + </section> + + </section> + + <section> + <title>"Conversation Aware" ESB Actions</title> + + <section> + <title>What are "Conversation Aware" ESB Actions?</title> + + <para> +<emphasis>Conversation aware</emphasis> ESB actions refer to a set of pre-defined ESB actions +that enable the structure (or behaviour) of a service to be inferred. + </para> + + <para> +For example, there are actions that explicitly define the sending and receiving of messages. +These actions define a property that declares the type of the message being sent or received. +Other actions describe grouping constructs such as if/else and switch. + </para> + + <para> +The benefit of making these concepts explicit within the ESB service configuration, is that +it makes it possible to check the implementation correctly matches the expected behaviour as +defined within the preceding artifacts (e.g. service design or choreography description). +This will be demonstrated in the following sub-section discussing conformance checking. + </para> + + </section> + + <section> + <title>Generating an ESB Service using "Conversation Aware" ESB Actions</title> + + <para> +Once we have a choreography description, it is possible to generate an ESB Service (with <emphasis>conversation aware</emphasis> ESB actions), for each of the participants defined within the choreography. To try this out, select the <emphasis>SAVARA->Generate->JBossESB Services</emphasis> menu item from the popup menu associated with the <filename>PurchaseGoods.cdm</filename>. + </para> + + <imageobject> + <imagedata fileref="images/GenerateESBServicesMenu.jpg" align="center" width="3in" /> + </imageobject> + + <para> +This will display a dialog listing the possible services that can be generated from this choreography, with a proposed Eclipse project name. + </para> + + <imageobject> + <imagedata fileref="images/GenerateESBServicesDialog.jpg" align="center" width="3in" /> + </imageobject> + + <para> +To test out this feature, uncheck the <emphasis>Buyer</emphasis> and <emphasis>CreditAgency</emphasis> participants, leave the build system as <emphasis>Ant</emphasis>, select the messaging system appropriate for your target environment and press the 'Ok' button. This will create a single new project for the <emphasis>Store</emphasis> participant. + </para> + + <imageobject> + <imagedata fileref="images/GenerateESBServicesNav.jpg" align="center" width="2in" /> + </imageobject> + + <para> +The generated project includes the ESB configuration file (in the <filename>src/conf</filename> folder) and the relevant Java classes in the <filename>src/java</filename> folder. The contents of this project represents a template of the service. Before it can be executed, the ESB configuration file will need to be enhanced to include internal implementation details for the service. The contents of this generated project should be compared to the completed version in the <filename>purchasing-store</filename> project. + </para> + + <note> + <para> +When the project is generated, if errors are reported against the <filename>jboss-esb.xml</filename>, then simply double-click on the error to launch the ESB configuration file. Then make a minor change, such as adding a new line and then removing it, and save the file again (to force re-validation). This should cause the errors to be cleared. This occurs because the Eclipse tasks that validate the <filename>jboss-esb.xml</filename> file and compiling the new Java classes in the project sometimes gets confused, causing the classes not to be present when the validation rules attempt to access them. This issue is being investigated. + </para> + </note> + </section> + + <section> + <title>Conformance Checking "Conversation Aware" ESB Services</title> + + <para> +To demonstrate the conformance checking mechanism, where the behaviour of the ESB service is verifed against its responsiblities as defined within the choreography description, open the <filename>src/conf/jboss-esb.xml</filename> in the <filename>PurchaseGoodsProcess-Store</filename> generated in the previous sub-section. + </para> + + <para> +When the ESB configuration has been loaded into an editor, locate the first <emphasis>ReceiveMessageAction</emphasis> ESB action, which should have a property called <emphasis>messageType</emphasis> with a value of <emphasis>BuyRequest</emphasis>. To cause a conformance checking error, simply append an 'X' to the end of the message type value, as shown in the following screenshot: + </para> + + <imageobject> + <imagedata fileref="images/ConformanceCheckError.jpg" align="center" width="4in" /> + </imageobject> + + <para> +This results in an error message being reported: + </para> + + <imageobject> + <imagedata fileref="images/ConformanceCheckErrorMessage.jpg" align="center" width="4in" /> + </imageobject> + + <para> +To fix conformance issues, some of the error messages will provide <emphasis>Quick Fix</emphasis> solutions. These can be access using the popup menu associated with the error message: + </para> + + <imageobject> + <imagedata fileref="images/ConformanceCheckErrorMessageMenu.jpg" align="center" width="4in" /> + </imageobject> + + <para> +This will display the <emphasis>Quick Fix</emphasis> dialog listing the available resolutions. + </para> + + <imageobject> + <imagedata fileref="images/QuickFixDialog.jpg" align="center" width="4in" /> + </imageobject> + + <para> +If the <emphasis>Show Referenced Description</emphasis> resolution is selected, then it will cause the choreography description to be launched and the specific interaction to be focused. + </para> + + <imageobject> + <imagedata fileref="images/ShowReferencedDescription.jpg" align="center" width="4in" /> + </imageobject> + + <para> +If the <emphasis>Update from Referenced Description</emphasis> is selected, then the <filename>jboss-esb.xml</filename> will be automatically updated to remove the appended 'X' from the message type. + </para> + + </section> + + <section> + <title>Running "Conversation Aware" ESB Services</title> + + <note> + <para> + Before you can deploy and run the "conversation aware" ESB example, you will + need to install the SAVARA Runtime module for JBossESB. + </para> + </note> + + <para> +The purchasing example describes the interactions between a Buyer, Store and Credit Agency. +The flow for this example would be: + </para> + + <itemizedlist> + <listitem> +Buyer send a 'buy' request to Store + </listitem> + <listitem> +Store send a 'credit check' request to the Credit Agency. + </listitem> + <listitem> +If the Credit Agency returns a successful message, then the Store will send a 'BuyConfirmed' to user. + </listitem> + <listitem> +If the Credit Agency returns a failed message, then the Store will send a 'BuyFailed' to user. + </listitem> + </itemizedlist> + + <para> +To run the <emphasis>purchasing</emphasis> example, firstly ensure that the SAVARA Runtime for +JBossESB has been deployed and configured within the JBoss Application +Server/ESB environment: + </para> + + <orderedlist> + <listitem> +In a command window, go to the <filename>${SAVARA-Runtime}/samples</filename> folder and +execute <emphasis role="bold">ant deploy-purchasing</emphasis> + </listitem> + <listitem> +In a command window, go to the <filename>${SAVARA-Runtime}/samples/client</filename> folder +and execute <emphasis role="bold">ant runPurchasingClient</emphasis>, which will send a +'BuyRequest' message to the <emphasis>Store</emphasis>, +which will then perform the credit check before returning a response to the client. + </listitem> + </orderedlist> + + <para> +In this example, the conversation ESB actions will do the validation in the runtime. +As we've said, the client send the 'buyRequest' message to the store, +firstly the store service will check the received message based on its messageType attribute. +and then send another message to the <emphasis>CreditAgency</emphasis> service it goes +through its validation. +If the messageType that <emphasis>Store</emphasis> service received is not as same +as the one defined in the "conversation aware" ESB actions, it will throw out the +exception and ends its flow. + </para> + + </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, defined +using <emphasis>conversation aware</emphasis> ESB actions or BPEL, 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: tools/eclipse/trunk/docs/gettingstartedguide/src/main/xslt/pdf.xsl =================================================================== --- tools/eclipse/trunk/docs/gettingstartedguide/src/main/xslt/pdf.xsl (rev 0) +++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/xslt/pdf.xsl 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,91 @@ +<?xml version="1.0" encoding="UTF-8"?> +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" + xmlns:fo="http://www.w3.org/1999/XSL/Format" + version="1.0"> + + <xsl:import href="http://docbook.sourceforge.net/release/xsl/1.72.0/fo/docbook.xsl" /> + <xsl:import href="classpath:/xslt/org/jboss/pdf.xsl" /> + +  + <xsl:param name="body.font.family" select="'Times New Roman, serif'" /> + <xsl:param name="monospace.font.family" select="'DejaVu Sans Mono, monospace'" /> + <xsl:param name="sans.font.family" select="'Arial, sans-serif'" /> + <xsl:param name="title.font.family" select="$body.font.family" /> + <xsl:param name="programlisting.font" select="$monospace.font.family" /> + <xsl:param name="programlisting.font.size" select="'75%'" /> + +  + <xsl:param name="double.sided" select="0" /> + +  + <xsl:param name="callout.graphics" select="1" /> + <xsl:param name="callout.graphics.extension" select="'.svg'" /> + +  + <xsl:param name="ulink.show" select="0"/> + +  + <xsl:attribute-set name="xref.properties"> + <xsl:attribute name="font-style">normal</xsl:attribute> + </xsl:attribute-set> + +  + <xsl:attribute-set name="monospace.properties"> + <xsl:attribute name="font-size">1em</xsl:attribute> + <xsl:attribute name="font-family"> + <xsl:value-of select="$monospace.font.family"/> + </xsl:attribute> + </xsl:attribute-set> + +  + <xsl:template match="callout"> + <xsl:variable name="id"><xsl:call-template name="object.id"/></xsl:variable> + <fo:list-item id="{$id}" space-before="1em"> + <fo:list-item-label end-indent="label-end()"> + <fo:block> + <xsl:call-template name="callout.arearefs"> + <xsl:with-param name="arearefs" select="@arearefs"/> + </xsl:call-template> + </fo:block> + </fo:list-item-label> + <fo:list-item-body start-indent="body-start()"> + <fo:block padding-top="0.2em"> + <xsl:apply-templates/> + </fo:block> + </fo:list-item-body> + </fo:list-item> + </xsl:template> + +  + <xsl:template name="callout-bug"> + <xsl:param name="conum" select='1'/> + <xsl:choose> + <xsl:when test="$conum <= $callout.graphics.number.limit"> + <xsl:variable name="filename" + select="concat($callout.graphics.path, $conum, + $callout.graphics.extension)"/> + + <fo:external-graphic content-width="{$callout.icon.size}" + width="{$callout.icon.size}" + padding="0.0em" margin="0.0em" + baseline-shift="-0.375em"> + <xsl:attribute name="src"> + <xsl:choose> + <xsl:when test="$passivetex.extensions != 0 + or $fop.extensions != 0 + or $arbortext.extensions != 0"> + <xsl:value-of select="$filename"/> + </xsl:when> + <xsl:otherwise> + <xsl:text>url(</xsl:text> + <xsl:value-of select="$filename"/> + <xsl:text>)</xsl:text> + </xsl:otherwise> + </xsl:choose> + </xsl:attribute> + </fo:external-graphic> + </xsl:when> + </xsl:choose> + </xsl:template> +</xsl:stylesheet> + Added: tools/eclipse/trunk/docs/pom.xml =================================================================== --- tools/eclipse/trunk/docs/pom.xml (rev 0) +++ tools/eclipse/trunk/docs/pom.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,23 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + + <modelVersion>4.0.0</modelVersion> + + <groupId>org.jboss.savara.tools.eclipse</groupId> + <artifactId>docs</artifactId> + <packaging>pom</packaging> + <name>Savara::Tools::Eclipse::Docs</name> + + <parent> + <groupId>org.jboss.savara.tools</groupId> + <artifactId>eclipse</artifactId> + <version>1.0-SNAPSHOT</version> + </parent> + + <modules> +  + <module>gettingstartedguide</module> + </modules> + +</project> Added: tools/eclipse/trunk/pom.xml =================================================================== --- tools/eclipse/trunk/pom.xml (rev 0) +++ tools/eclipse/trunk/pom.xml 2009-11-24 21:41:13 UTC (rev 89) @@ -0,0 +1,196 @@ +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> + <modelVersion>4.0.0</modelVersion> + <groupId>org.jboss.savara.tools</groupId> + <artifactId>eclipse</artifactId> + <version>1.0-SNAPSHOT</version> + <packaging>pom</packaging> + <name>Savara::Tools::Eclipse</name> + <url>http://www.jboss.org/savara</url> + <description> + The JBoss SAVARA Eclipse Tools. + </description> + <scm> + <connection>scm:svn:https://svn.jboss.org/repos/savara/tools/eclipse</connection> + </scm> + <developers> + <developer> + <name>Jeff Yu</name> + <id>jeff.yuchang</id> + <email>cyu(a)redhat.com</email> + <organization>Red Hat</organization> + <roles> + <role>Developer</role> + </roles> + <timezone>+8</timezone> + </developer> + <developer> + <name>Gary Brown</name> + <id>objectiser</id> + <email>gbrown(a)redhat.com</email> + <organization>Red Hat</organization> + <roles> + <role>Developer</role> + </roles> + <timezone>+1</timezone> + </developer> + </developers> + <modules> + <module>docs</module> + </modules> + + <build> +  + <pluginManagement> + <plugins> +  + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-javadoc-plugin</artifactId> + <version>2.2</version> + <configuration> + <aggregate>true</aggregate> + </configuration> + </plugin> + </plugins> + </pluginManagement> + <plugins> +  + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-compiler-plugin</artifactId> + <version>2.0.2</version> + <configuration> + <source>1.5</source> + <target>1.5</target> + <showDeprecation>false</showDeprecation> + <showWarnings>false</showWarnings> + </configuration> + </plugin> +  + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-source-plugin</artifactId> + <executions> + <execution> + <id>attach-sources</id> + <phase>verify</phase> + <goals> + <goal>jar</goal> + </goals> + </execution> + </executions> + </plugin> + <plugin> + <artifactId>maven-surefire-plugin</artifactId> + <configuration> + <includes> + <include>**/*TestCase.java</include> + <include>**/*Test.java</include> + </includes> + </configuration> + </plugin> + </plugins> + </build> + + <properties> + <savara-version>1.0-SNAPSHOT</savara-version> + <junit.version>4.4</junit.version> + <rosetta.version>4.5</rosetta.version> + <log4j.version>1.2.14</log4j.version> + <mvel.version>1.3.4-java1.5</mvel.version> + </properties> + + <dependencyManagement> + <dependencies> + <dependency> + <groupId>junit</groupId> + <artifactId>junit</artifactId> + <version>${junit.version}</version> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss.overlord.dependencies.org.jboss.esb</groupId> + <artifactId>jbossesb-rosetta</artifactId> + <version>${rosetta.version}</version> + </dependency> + <dependency> + <groupId>log4j</groupId> + <artifactId>log4j</artifactId> + <version>${log4j.version}</version> + </dependency> + <dependency> + <groupId>org.mvel</groupId> + <artifactId>mvel</artifactId> + <version>${mvel.version}</version> + </dependency> + </dependencies> + </dependencyManagement> + + + <reporting> + <plugins> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-surefire-report-plugin</artifactId> + </plugin> + </plugins> + </reporting> + + <repositories> + <repository> + <id>jboss</id> + <url>http://repository.jboss.com/maven2/</url> + <snapshots> + <enabled>false</enabled> + </snapshots> + </repository> + + <repository> + <id>jboss-snapshot</id> + <url>http://snapshots.jboss.org/maven2</url> + <snapshots> + <enabled>true</enabled> + </snapshots> + </repository> + + <repository> + <id>maven.repo</id> + <name>maven repository</name> + <url>http://repo1.maven.org/maven2</url> + </repository> + + <repository> + <id>ibiblio</id> + <name>ibiblio repository</name> + <url>http://mirrors.ibiblio.org/pub/mirrors/maven2</url> + </repository> + + <repository> + <id>codehaus</id> + <name>codehaus repository</name> + <url>http://repo1.maven.org/maven2</url> + </repository> + + </repositories> + + <distributionManagement> + <repository> + <id>jboss</id> + <name>JBoss Maven Repository</name> + <url>file://${jboss.maven.repository}</url> + </repository> + <snapshotRepository> + <id>jboss-snapshots</id> + <name>JBoss Snapshot Repository</name> + <url>dav:https://snapshots.jboss.org/maven2</url> + </snapshotRepository> + </distributionManagement> + +</project>

14 years, 4 months

1
0
0 / 0

savara SVN: r88 - in validator/trunk: distribution/src and 18 other directories.

by do-not-reply＠jboss.org

Author: jeff.yuchang Date: 2009-11-15 11:02:50 -0500 (Sun, 15 Nov 2009) New Revision: 88 Added: validator/trunk/distribution/src/ validator/trunk/distribution/src/files/ validator/trunk/distribution/src/files/jbossesb/ validator/trunk/distribution/src/files/jbossesb/build.xml validator/trunk/distribution/src/files/jbossesb/conf/ validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties-validator.xml validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties.xml validator/trunk/distribution/src/files/jbossesb/models/ validator/trunk/distribution/src/files/jbossesb/models/trailblazer.zip validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/META-INF/ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/META-INF/jboss-service.xml validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbm-queue-service.xml validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbmq-queue-service.xml validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.common_2.3.0.v200709252135.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.ecore.xmi_2.3.1.v200709252135.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.ecore_2.3.1.v200709252135.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.cdl_2.0.0.200904101438.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.common_2.0.0.200904101438.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.j2ee_2.0.0.200904101438.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.jboss_2.0.0.200904101438.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.jbossesb_2.0.0.200904101438.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.service_2.0.0.200904101438.jar validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/pi4soa.xml validator/trunk/distribution/src/files/jbossesb/readme.txt validator/trunk/distribution/src/main/ validator/trunk/distribution/src/main/assembly/ validator/trunk/distribution/src/main/assembly/bin.xml validator/trunk/distribution/src/main/release/ validator/trunk/distribution/src/main/release/samples/ validator/trunk/distribution/src/main/release/samples/jbossesb/ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.classpath validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.project validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.settings/ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.settings/org.eclipse.core.resources.prefs validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/src/ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/src/pi4soa.xml Modified: validator/trunk/jbossesb/pom.xml validator/trunk/jbossesb/src/main/configs/esb-assembly.xml Log: * add assembly script for validator sub-project. Added: validator/trunk/distribution/src/files/jbossesb/build.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/build.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/build.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,75 @@ +<project name="validator" default="deploy" basedir="."> + + <property name="target-server" value="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}" /> + + + + + + <target name="messaging-config" > + <property name="org.jboss.esb.server.deploy.dir" + value="${target-server}/deploy"/> + + <condition property="messaging.present"> + <available file="${org.jboss.esb.server.deploy.dir}/jboss-messaging"/> + </condition> + <condition property="messaging.present"> + <available file="${org.jboss.esb.server.deploy.dir}/jboss-messaging.sar"/> + </condition> + + <condition property="jbossmq.present"> + <not> + <isset property="messaging.present"/> + </not> + </condition> + </target> + +  + <target name="messaging-dependencies" if="messaging.present" depends="messaging-config"> + <property name="jms.service.file" value="jbm-queue-service.xml"/> + <property name="jms.description" value="JBoss Messaging"/> + </target> + +  + <target name="jbossmq-dependencies" if="jbossmq.present" depends="messaging-config"> + <property name="jms.service.file" value="jbmq-queue-service.xml"/> + <property name="jms.description" value="JBoss MQ"/> + </target> + + + + + + <target name="deploy" depends="register-validator-filter,messaging-dependencies,jbossmq-dependencies"> + <echo message="Deploy pi4soa.sar, savara-validator-jbossesb.esb files to the target server '${target-server}'." /> + <copy todir="${target-server}/deploy/pi4soa.sar"> + <fileset dir="${basedir}/pi4soa.sar"> + <exclude name="jms/**" /> + </fileset> + </copy> + <copy todir="${target-server}/deploy/pi4soa.sar" + file="${basedir}/pi4soa.sar/jms/${jms.service.file}" /> + <copy todir="${target-server}/deploy/savara-validator-jbossesb.esb"> + <fileset dir="${basedir}/savara-validator-jbossesb.esb" /> + </copy> + </target> + + <target name="undeploy" depends="unregister-validator-filter"> + <echo message="Undeploy pi4soa.sar, savara-validator-jbossesb.esb files from the target sever '${target-server}'."/> + <delete dir="${target-server}/deploy/pi4soa.sar" /> + <delete dir="${target-server}/deploy/savara-validator-jbossesb.esb" /> + </target> + + <target name="register-validator-filter"> + <echo message="register the validator filter in the jbossesb-properties file" /> + <delete file="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" /> + <copy file="${basedir}/conf/jbossesb-properties-validator.xml" tofile="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" /> + </target> + + <target name="unregister-validator-filter"> + <echo message="unregister the validator filter from the jbossesb-properties file" /> + <delete file="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" /> + <copy file="${basedir}/conf/jbossesb-properties.xml" tofile="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" /> + </target> + +</project> Property changes on: validator/trunk/distribution/src/files/jbossesb/build.xml ___________________________________________________________________ Name: svn:executable + * Added: validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties-validator.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties-validator.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties-validator.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,95 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> + + + +<esb + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:noNamespaceSchemaLocation="jbossesb-1_0.xsd"> + <properties name="core"> + <property name="org.jboss.soa.esb.jndi.server.context.factory" value="org.jnp.interfaces.NamingContextFactory"/> + <property name="org.jboss.soa.esb.jndi.server.url" value="${jboss.bind.address}:1099"/> + <property name="org.jboss.soa.esb.persistence.connection.factory" value="org.jboss.internal.soa.esb.persistence.format.MessageStoreFactoryImpl"/> + <property name="org.jboss.soa.esb.loadbalancer.policy" value="org.jboss.soa.esb.listeners.ha.RoundRobin"/> + <property name="jboss.esb.invm.scope.default" value="NONE"/> + </properties> + <properties name="registry"> + <property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.registry.local.InquiryService#inquire"/> + <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="org.apache.juddi.registry.local.PublishService#publish"/> + <property name="org.jboss.soa.esb.registry.implementationClass" value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/> + <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/> + <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/> + <property name="org.jboss.soa.esb.registry.password" value="password"/> +  + <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.LocalTransport"/> + </properties> + <properties name="transports" depends="core"> + <property name="org.jboss.soa.esb.mail.smtp.host" value="localhost"/> + <property name="org.jboss.soa.esb.mail.smtp.user" value="jbossesb"/> + <property name="org.jboss.soa.esb.mail.smtp.password" value=""/> + <property name="org.jboss.soa.esb.mail.smtp.port" value="25"/> + <property name="org.jboss.soa.esb.mail.smtp.auth" value="true"/> + <property name="org.jboss.soa.esb.ftp.localdir" value="/tmp"/> + <property name="org.jboss.soa.esb.ftp.remotedir" value="/tmp"/> + <property name="org.jboss.soa.esb.jms.connectionPool" value="20"/> + <property name="org.jboss.soa.esb.jms.sessionSleep" value="30"/> + </properties> + <properties name="connection"> + <property name="min-pool-size" value="5"/> + <property name="max-pool=size" value="10"/> + <property name="blocking-timeout-millis" value="5000"/> + <property name="abandoned-connection-timeout" value="10000"/> + <property name="abandoned-connection-time-interval" value="30000"/> + </properties> + <properties name="dbstore"> + +  +  + <property name="org.jboss.soa.esb.persistence.db.conn.manager" value="org.jboss.internal.soa.esb.persistence.manager.J2eeConnectionManager"/> + +  + <property name="org.jboss.soa.esb.persistence.db.datasource.name" value="java:/JBossESBDS"/> + +  + <property name="org.jboss.soa.esb.persistence.db.connection.url" value="jdbc:hsqldb:hsql://localhost:9001/"/> + <property name="org.jboss.soa.esb.persistence.db.jdbc.driver" value="org.hsqldb.jdbcDriver"/> + <property name="org.jboss.soa.esb.persistence.db.user" value="sa"/> + <property name="org.jboss.soa.esb.persistence.db.pwd" value=""/> + <property name="org.jboss.soa.esb.persistence.db.pool.initial.size" value="2"/> + <property name="org.jboss.soa.esb.persistence.db.pool.min.size" value="2"/> + <property name="org.jboss.soa.esb.persistence.db.pool.max.size" value="5"/> +  + <property name="org.jboss.soa.esb.persistence.db.pool.test.table" value="pooltest"/> + <property name="org.jboss.soa.esb.persistence.db.pool.timeout.millis" value="5000"/> + + </properties> + <properties name="filters"> + <property name="org.jboss.soa.esb.filter.1" value="org.jboss.internal.soa.esb.message.filter.MetaDataFilter"/> + <property name="org.jboss.soa.esb.filter.2" value="org.jboss.internal.soa.esb.message.filter.GatewayFilter"/> + <property name="org.jboss.soa.esb.filter.10" value="org.jboss.soa.overlord.validator.jbossesb.ValidatorFilter" /> + </properties> +</esb> Added: validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/conf/jbossesb-properties.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,94 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> + + + +<esb + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:noNamespaceSchemaLocation="jbossesb-1_0.xsd"> + <properties name="core"> + <property name="org.jboss.soa.esb.jndi.server.context.factory" value="org.jnp.interfaces.NamingContextFactory"/> + <property name="org.jboss.soa.esb.jndi.server.url" value="${jboss.bind.address}:1099"/> + <property name="org.jboss.soa.esb.persistence.connection.factory" value="org.jboss.internal.soa.esb.persistence.format.MessageStoreFactoryImpl"/> + <property name="org.jboss.soa.esb.loadbalancer.policy" value="org.jboss.soa.esb.listeners.ha.RoundRobin"/> + <property name="jboss.esb.invm.scope.default" value="NONE"/> + </properties> + <properties name="registry"> + <property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.registry.local.InquiryService#inquire"/> + <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="org.apache.juddi.registry.local.PublishService#publish"/> + <property name="org.jboss.soa.esb.registry.implementationClass" value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/> + <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/> + <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/> + <property name="org.jboss.soa.esb.registry.password" value="password"/> +  + <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.LocalTransport"/> + </properties> + <properties name="transports" depends="core"> + <property name="org.jboss.soa.esb.mail.smtp.host" value="localhost"/> + <property name="org.jboss.soa.esb.mail.smtp.user" value="jbossesb"/> + <property name="org.jboss.soa.esb.mail.smtp.password" value=""/> + <property name="org.jboss.soa.esb.mail.smtp.port" value="25"/> + <property name="org.jboss.soa.esb.mail.smtp.auth" value="true"/> + <property name="org.jboss.soa.esb.ftp.localdir" value="/tmp"/> + <property name="org.jboss.soa.esb.ftp.remotedir" value="/tmp"/> + <property name="org.jboss.soa.esb.jms.connectionPool" value="20"/> + <property name="org.jboss.soa.esb.jms.sessionSleep" value="30"/> + </properties> + <properties name="connection"> + <property name="min-pool-size" value="5"/> + <property name="max-pool=size" value="10"/> + <property name="blocking-timeout-millis" value="5000"/> + <property name="abandoned-connection-timeout" value="10000"/> + <property name="abandoned-connection-time-interval" value="30000"/> + </properties> + <properties name="dbstore"> + +  +  + <property name="org.jboss.soa.esb.persistence.db.conn.manager" value="org.jboss.internal.soa.esb.persistence.manager.J2eeConnectionManager"/> + +  + <property name="org.jboss.soa.esb.persistence.db.datasource.name" value="java:/JBossESBDS"/> + +  + <property name="org.jboss.soa.esb.persistence.db.connection.url" value="jdbc:hsqldb:hsql://localhost:9001/"/> + <property name="org.jboss.soa.esb.persistence.db.jdbc.driver" value="org.hsqldb.jdbcDriver"/> + <property name="org.jboss.soa.esb.persistence.db.user" value="sa"/> + <property name="org.jboss.soa.esb.persistence.db.pwd" value=""/> + <property name="org.jboss.soa.esb.persistence.db.pool.initial.size" value="2"/> + <property name="org.jboss.soa.esb.persistence.db.pool.min.size" value="2"/> + <property name="org.jboss.soa.esb.persistence.db.pool.max.size" value="5"/> +  + <property name="org.jboss.soa.esb.persistence.db.pool.test.table" value="pooltest"/> + <property name="org.jboss.soa.esb.persistence.db.pool.timeout.millis" value="5000"/> + + </properties> + <properties name="filters"> + <property name="org.jboss.soa.esb.filter.1" value="org.jboss.internal.soa.esb.message.filter.MetaDataFilter"/> + <property name="org.jboss.soa.esb.filter.2" value="org.jboss.internal.soa.esb.message.filter.GatewayFilter"/> + </properties> +</esb> Added: validator/trunk/distribution/src/files/jbossesb/models/trailblazer.zip =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/models/trailblazer.zip ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/META-INF/jboss-service.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/META-INF/jboss-service.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/META-INF/jboss-service.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,6 @@ +<?xml version="1.0" encoding="UTF-8"?> +<service> + <mbean code="org.pi4soa.jboss.service.Pi4SOAService" + name="pi4soa:service=pi4soa"> + </mbean> +</service> Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbm-queue-service.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbm-queue-service.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbm-queue-service.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,11 @@ +<?xml version="1.0" encoding="UTF-8"?> +<server> + + <mbean code="org.jboss.jms.server.destination.TopicService" + name="jboss.messaging.destination:service=Topic,name=tracker" + xmbean-dd="xmdesc/Topic-xmbean.xml"> + <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> + <depends>jboss.messaging:service=PostOffice</depends> + </mbean> + +</server> Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbmq-queue-service.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbmq-queue-service.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/jms/jbmq-queue-service.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,7 @@ +<?xml version="1.0" encoding="UTF-8"?> +<server> + <mbean code="org.jboss.mq.server.jmx.Topic" + name="jboss.mq.destination:service=Topic,name=tracker"> + <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends> + </mbean> +</server> Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.common_2.3.0.v200709252135.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.common_2.3.0.v200709252135.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.ecore.xmi_2.3.1.v200709252135.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.ecore.xmi_2.3.1.v200709252135.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.ecore_2.3.1.v200709252135.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.eclipse.emf.ecore_2.3.1.v200709252135.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.cdl_2.0.0.200904101438.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.cdl_2.0.0.200904101438.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.common_2.0.0.200904101438.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.common_2.0.0.200904101438.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.j2ee_2.0.0.200904101438.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.j2ee_2.0.0.200904101438.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.jboss_2.0.0.200904101438.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.jboss_2.0.0.200904101438.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.jbossesb_2.0.0.200904101438.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.jbossesb_2.0.0.200904101438.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.service_2.0.0.200904101438.jar =================================================================== (Binary files differ) Property changes on: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/org.pi4soa.service_2.0.0.200904101438.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/pi4soa.xml =================================================================== --- validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/pi4soa.xml (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/pi4soa.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,38 @@ + + +<pi4soa> + <container> + <serviceTracker class="org.pi4soa.service.tracker.jms.JMSServiceTracker" > + <jmsConnectionFactory>ConnectionFactory</jmsConnectionFactory> + <jmsDestination>topic/tracker</jmsDestination> + <recordMessagePayload>true</recordMessagePayload> + </serviceTracker> + </container> + <monitor> + <serviceTracker class="org.pi4soa.service.tracker.jms.JMSServiceTracker" > + <jmsConnectionFactory>ConnectionFactory</jmsConnectionFactory> + <jmsDestination>topic/tracker</jmsDestination> + <recordMessagePayload>true</recordMessagePayload> + </serviceTracker> + </monitor> +</pi4soa> \ No newline at end of file Added: validator/trunk/distribution/src/files/jbossesb/readme.txt =================================================================== --- validator/trunk/distribution/src/files/jbossesb/readme.txt (rev 0) +++ validator/trunk/distribution/src/files/jbossesb/readme.txt 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,37 @@ +Required to deploy the validator libraries. +- ANT + +Folder structures +----------------------- +1 - pi4soa.sar + +2 - savara-validator-jbossesb.esb It contains the monitor config file (WS-CDL file) that will be used by the Filter. + +3 - conf/ It contains the proper configuration for governance deployment. + +4 - models It contains the WS-CDL models archive. + + + +Instructions for deploying/undeploying by using ANT (recommended) +------------------------------------------------------------------ +1 - Go to $savara/install directory. + +2 - Run "ant deploy-savara-validator" to deploy the validator libraries. + +3 - Run "ant undeploy-savara-validator" to undeploy the validator libraries. + + + +Deploying validator libraries manually +----------------------------------------------------------- + +1 - Copy the "pi4soa.sar", "monitor.esb" two libraries to the $JBossESB/server/config (e.g. default)/deploy folder. + +2 - Open up the "jbossesb-properties.xml", which is loated in the $JBossESB/server/$domain/deploy/jbossesb.sar folder. + + Add following "monitor filter" in the file, at the bottom of the '<properties name="filter">' xml block. + + ' <property name="org.jboss.soa.esb.filter.10" value="org.pi4soa.jbossesb.monitor.MonitorFilter" /> ' + + Added: validator/trunk/distribution/src/main/assembly/bin.xml =================================================================== --- validator/trunk/distribution/src/main/assembly/bin.xml (rev 0) +++ validator/trunk/distribution/src/main/assembly/bin.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,152 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<assembly> +  + <id>bin</id> + <includeBaseDirectory>true</includeBaseDirectory> + <formats> + <format>zip</format> + </formats> + + <fileSets> + +  + <fileSet> + <directory>src/main/release</directory> + <outputDirectory>/</outputDirectory> + <includes> + <include>*.txt</include> + <include>*.properties</include> + </includes> + </fileSet> + + <fileSet> + <directory>src/main/release/install</directory> + <outputDirectory>/install</outputDirectory> + </fileSet> + +  + + <fileSet> + <directory>src/main/release/samples/jbossesb</directory> + <outputDirectory>samples</outputDirectory> + </fileSet> + +  + <fileSet> + <directory>../samples/jbossesb/brokerage/models</directory> + <outputDirectory>samples/models/brokerage</outputDirectory> + <excludes> + <exclude>**/.project</exclude> + </excludes> + </fileSet> + <fileSet> + <directory>../samples/jbossesb/purchasing/models</directory> + <outputDirectory>samples/models/purchasing</outputDirectory> + <excludes> + <exclude>**/.project</exclude> + </excludes> + </fileSet> + + <fileSet> + <directory>../samples/jbossesb/brokerage/broker/src</directory> + <outputDirectory>samples/brokerage/broker/src</outputDirectory> + </fileSet> + <fileSet> + <directory>../samples/jbossesb/brokerage/supplier/src</directory> + <outputDirectory>samples/brokerage/supplier/src</outputDirectory> + </fileSet> + <fileSet> + <directory>../samples/jbossesb/purchasing/store/src</directory> + <outputDirectory>samples/purchasing/store/src</outputDirectory> + </fileSet> + <fileSet> + <directory>../samples/jbossesb/common/creditAgency/src</directory> + <outputDirectory>samples/common/creditAgency/src</outputDirectory> + </fileSet> + +  + <fileSet> + <directory>../samples/jbossesb/client</directory> + <outputDirectory>samples/client</outputDirectory> + </fileSet> +  + + </fileSets> + + <dependencySets> + <dependencySet> + <outputDirectory>modules</outputDirectory> + <unpack>true</unpack> + <includes> + <include>org.jboss.savara.runtime:savara-runtime-jbossesb:zip:dist</include> + </includes> + </dependencySet> + +  + <dependencySet> + <outputDirectory>samples/brokerage/broker/lib</outputDirectory> + <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping> + <includes> + <include>org.jboss.savara:savara-runtime-jbossesb:jar</include> + <include>org.jboss.overlord.dependencies.org.jboss.esb:jbossesb-rosetta</include> + <include>log4j:log4j</include> + </includes> + </dependencySet> + <dependencySet> + <outputDirectory>samples/brokerage/supplier/lib</outputDirectory> + <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping> + <includes> + <include>org.jboss.savara:savara-runtime-jbossesb:jar</include> + <include>org.jboss.overlord.dependencies.org.jboss.esb:jbossesb-rosetta</include> + <include>log4j:log4j</include> + </includes> + </dependencySet> + <dependencySet> + <outputDirectory>samples/purchasing/store/lib</outputDirectory> + <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping> + <includes> + <include>org.jboss.savara:savara-runtime-jbossesb:jar</include> + <include>org.jboss.overlord.dependencies.org.jboss.esb:jbossesb-rosetta</include> + <include>log4j:log4j</include> + </includes> + </dependencySet> + <dependencySet> + <outputDirectory>samples/common/creditAgency/lib</outputDirectory> + <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping> + <includes> + <include>org.jboss.savara:savara-runtime-jbossesb:jar</include> + <include>org.jboss.overlord.dependencies.org.jboss.esb:jbossesb-rosetta</include> + <include>log4j:log4j</include> + <include>sun-jaxws:jaxws-api</include> + <include>javax.xml.bind:jaxb-api</include> + <include>sun-jaxws:jsr181-api</include> + </includes> + </dependencySet> + + </dependencySets> + +</assembly> Added: validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.classpath =================================================================== --- validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.classpath (rev 0) +++ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.classpath 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,6 @@ +<?xml version="1.0" encoding="UTF-8"?> +<classpath> + <classpathentry kind="src" path="src"/> + <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> + <classpathentry kind="output" path="bin"/> +</classpath> Added: validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.project =================================================================== --- validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.project (rev 0) +++ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.project 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,17 @@ +<?xml version="1.0" encoding="UTF-8"?> +<projectDescription> + <name>trailblazer-models</name> + <comment></comment> + <projects> + </projects> + <buildSpec> + <buildCommand> + <name>org.eclipse.jdt.core.javabuilder</name> + <arguments> + </arguments> + </buildCommand> + </buildSpec> + <natures> + <nature>org.eclipse.jdt.core.javanature</nature> + </natures> +</projectDescription> Added: validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.settings/org.eclipse.core.resources.prefs =================================================================== --- validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.settings/org.eclipse.core.resources.prefs (rev 0) +++ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/.settings/org.eclipse.core.resources.prefs 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,3 @@ +#Mon Sep 22 11:55:10 BST 2008 +eclipse.preferences.version=1 +encoding/TrailBlazer.cdm=UTF-8 Added: validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/src/pi4soa.xml =================================================================== --- validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/src/pi4soa.xml (rev 0) +++ validator/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/models/src/pi4soa.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -0,0 +1,37 @@ + + +<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> + Modified: validator/trunk/jbossesb/pom.xml =================================================================== --- validator/trunk/jbossesb/pom.xml 2009-11-15 15:48:31 UTC (rev 87) +++ validator/trunk/jbossesb/pom.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -2,15 +2,15 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> - <groupId>org.jboss.savara</groupId> + <groupId>org.jboss.savara.validator</groupId> <artifactId>savara-validator-jbossesb</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <name>Savara::Validator::JBoss ESB</name> <parent> - <groupId>org.jboss</groupId> - <artifactId>savara</artifactId> + <groupId>org.jboss.savara</groupId> + <artifactId>validator</artifactId> <version>1.0-SNAPSHOT</version> </parent> Modified: validator/trunk/jbossesb/src/main/configs/esb-assembly.xml =================================================================== --- validator/trunk/jbossesb/src/main/configs/esb-assembly.xml 2009-11-15 15:48:31 UTC (rev 87) +++ validator/trunk/jbossesb/src/main/configs/esb-assembly.xml 2009-11-15 16:02:50 UTC (rev 88) @@ -19,7 +19,7 @@ <dependencySet> <outputDirectory>/</outputDirectory> <includes> - <include>org.jboss.savara:savara-validator-jbossesb</include> + <include>org.jboss.savara.validator:savara-validator-jbossesb</include> </includes> </dependencySet> </dependencySets>

14 years, 5 months

1
0
0 / 0

savara SVN: r87 - in runtime/trunk: distribution/src and 7 other directories.

by do-not-reply＠jboss.org

Author: jeff.yuchang Date: 2009-11-15 10:48:31 -0500 (Sun, 15 Nov 2009) New Revision: 87 Removed: runtime/trunk/distribution/src/files/ runtime/trunk/distribution/src/main/assembly/docs.xml runtime/trunk/distribution/src/main/assembly/src.xml runtime/trunk/distribution/src/main/release/samples/jbossesb/trailblazer/ Modified: runtime/trunk/distribution/pom.xml runtime/trunk/distribution/src/main/assembly/bin.xml runtime/trunk/distribution/src/main/release/install/build.xml runtime/trunk/docs/pom.xml runtime/trunk/docs/samplesguide/pom.xml runtime/trunk/docs/userguide/pom.xml runtime/trunk/jbossesb/src/main/configs/esb-assembly.xml Log: * move the validator related stuff into validator sub project. Modified: runtime/trunk/distribution/pom.xml =================================================================== --- runtime/trunk/distribution/pom.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/distribution/pom.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -85,66 +85,26 @@ </resource> </resources> <plugins> - <plugin> - <artifactId>maven-assembly-plugin</artifactId> - <version>2.2-beta-2</version> - <executions> - <execution> - <id>docs</id> - <phase>process-resources</phase> - <goals> - <goal>single</goal> - </goals> - <configuration> - <finalName>savara-${project.version}-docs</finalName> - <appendAssemblyId>false</appendAssemblyId> - <descriptors> - <descriptor>src/main/assembly/docs.xml</descriptor> - </descriptors> - </configuration> - </execution> - </executions> - </plugin> - <plugin> - <artifactId>maven-assembly-plugin</artifactId> - <version>2.2-beta-2</version> - <executions> - <execution> - <id>src</id> - <phase>process-resources</phase> - <goals> - <goal>single</goal> - </goals> - <configuration> - <finalName>savara-${project.version}-src</finalName> - <appendAssemblyId>false</appendAssemblyId> - <descriptors> - <descriptor>src/main/assembly/src.xml</descriptor> - </descriptors> - </configuration> - </execution> - </executions> - </plugin> - <plugin> - <artifactId>maven-assembly-plugin</artifactId> - <version>2.2-beta-2</version> - <executions> - <execution> - <id>bin</id> - <phase>process-resources</phase> - <goals> - <goal>single</goal> - </goals> - <configuration> - <finalName>savara-${project.version}</finalName> - <appendAssemblyId>false</appendAssemblyId> - <descriptors> - <descriptor>src/main/assembly/bin.xml</descriptor> - </descriptors> - </configuration> - </execution> - </executions> - </plugin> + <plugin> + <artifactId>maven-assembly-plugin</artifactId> + <version>2.2-beta-2</version> + <executions> + <execution> + <id>bin</id> + <phase>process-resources</phase> + <goals> + <goal>single</goal> + </goals> + <configuration> + <finalName>savara-runtime-${project.version}</finalName> + <appendAssemblyId>false</appendAssemblyId> + <descriptors> + <descriptor>src/main/assembly/bin.xml</descriptor> + </descriptors> + </configuration> + </execution> + </executions> + </plugin> </plugins> </build> Modified: runtime/trunk/distribution/src/main/assembly/bin.xml =================================================================== --- runtime/trunk/distribution/src/main/assembly/bin.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/distribution/src/main/assembly/bin.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -28,16 +28,6 @@ <fileSets> - <fileSet> - <directory>src/files/eclipse</directory> - <outputDirectory>tools</outputDirectory> - </fileSet> - - <fileSet> - <directory>src/files/validator/jbossesb</directory> - <outputDirectory>modules/savara-validator-jbossesb</outputDirectory> - </fileSet> -  <fileSet> <directory>src/main/release</directory> @@ -55,29 +45,20 @@  <fileSet> - <directory>../docs/docbook/userguide/target/docbook/publish/en-US</directory> + <directory>../docs/userguide/target/docbook/publish/en-US</directory> <outputDirectory>docs/userguide</outputDirectory> </fileSet> <fileSet> - <directory>../docs/docbook/samplesguide/target/docbook/publish/en-US</directory> + <directory>../docs/samplesguide/target/docbook/publish/en-US</directory> <outputDirectory>docs/samplesguide</outputDirectory> </fileSet> - <fileSet> - <directory>../docs/docbook/gettingstartedguide/target/docbook/publish/en-US</directory> - <outputDirectory>docs/gettingstartedguide</outputDirectory> - </fileSet> - <fileSet> - <directory>../runtime/jbossesb/target/javadoc</directory> + <directory>../jbossesb/target/javadoc</directory> <outputDirectory>docs/savara-runtime-jbossesb-javadoc</outputDirectory> </fileSet> - - <fileSet> - <directory>../validator/jbossesb/target/javadoc</directory> - <outputDirectory>docs/savara-validator-jbossesb-javadoc</outputDirectory> - </fileSet> +   @@ -125,10 +106,6 @@ <directory>../samples/jbossesb/client</directory> <outputDirectory>samples/client</outputDirectory> </fileSet> - <fileSet> - <directory>../samples/jbossesb/trailblazer</directory> - <outputDirectory>samples/trailblazer</outputDirectory> - </fileSet>  </fileSets> @@ -138,16 +115,9 @@ <outputDirectory>modules</outputDirectory> <unpack>true</unpack> <includes> - <include>org.jboss.savara:savara-runtime-jbossesb:zip:dist</include> + <include>org.jboss.savara.runtime:savara-runtime-jbossesb:zip:dist</include> </includes> </dependencySet> - <dependencySet> - <outputDirectory>modules/savara-validator-jbossesb</outputDirectory> - <unpack>true</unpack> - <includes> - <include>org.jboss.savara:savara-validator-jbossesb:zip:dist</include> - </includes> - </dependencySet>  -<assembly> -  - <id>docs</id> - <includeBaseDirectory>true</includeBaseDirectory> - <formats> - <format>zip</format> - </formats> - - <fileSets> - <fileSet> - <directory>../docs/docbook/userguide/target/docbook/publish/en-US</directory> - <outputDirectory>docs/userguide</outputDirectory> - </fileSet> - - <fileSet> - <directory>../docs/docbook/samplesguide/target/docbook/publish/en-US</directory> - <outputDirectory>docs/samplesguide</outputDirectory> - </fileSet> - - <fileSet> - <directory>../docs/docbook/gettingstartedguide/target/docbook/publish/en-US</directory> - <outputDirectory>docs/gettingstartedguide</outputDirectory> - </fileSet> - - <fileSet> - <directory>../runtime/jbossesb/target/javadoc</directory> - <outputDirectory>docs/savara-runtime-jbossesb-javadoc</outputDirectory> - </fileSet> - - <fileSet> - <directory>../validator/jbossesb/target/javadoc</directory> - <outputDirectory>docs/savara-validator-jbossesb-javadoc</outputDirectory> - </fileSet> - - </fileSets> - -</assembly> Deleted: runtime/trunk/distribution/src/main/assembly/src.xml =================================================================== --- runtime/trunk/distribution/src/main/assembly/src.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/distribution/src/main/assembly/src.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<assembly> -  - <id>src</id> - <includeBaseDirectory>true</includeBaseDirectory> - <formats> - <format>zip</format> - </formats> - - <fileSets> - - <fileSet> - <directory>..</directory> - <outputDirectory>src</outputDirectory> - <excludes> - <exclude>**/.project</exclude> - <exclude>**/.classpath</exclude> - <exclude>**/.settings</exclude> - <exclude>**/.settings/**/*</exclude> - <exclude>**/target</exclude> - <exclude>**/target/**/*</exclude> - </excludes> - </fileSet> - </fileSets> - -</assembly> Modified: runtime/trunk/distribution/src/main/release/install/build.xml =================================================================== --- runtime/trunk/distribution/src/main/release/install/build.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/distribution/src/main/release/install/build.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -1,4 +1,4 @@ -<project name="Overlord_CDL_Installer" default="deploy-savara-runtime" basedir="."> +<project name="SAVARA_Runtime_Installer" default="deploy" basedir=".">  <property name="org.jboss.esb.deployment.properties" location="deployment.properties"/> @@ -24,36 +24,17 @@ <fail unless="esb.server.configured" message="Cannot determine target deployment, please check deployment.properties"/> </target> - <target name="deploy-savara-runtime" description="Deploys Savara Runtime to the server"> + <target name="deploy" description="Deploys Savara Runtime to the server"> <echo message="Deploy savara runtime to JBoss ESB server" /> <copy todir="${deploy.dir}/savara-runtime-jbossesb.esb"> <fileset dir="${modules}/savara-runtime-jbossesb.esb"/> </copy> </target> - <target name="undeploy-savara-runtime" description="Undeploys Savara Runtime"> + <target name="undeploy" description="Undeploys Savara Runtime"> <echo message="Undeploy the savara runtime jbossesb from JBoss ESB server" /> <delete dir="${deploy.dir}/savara-runtime-jbossesb.esb" /> </target> - <target name="deploy-savara-validator" depends="check.deploy.props" description="Deploys Savara validator to the server"> - <echo message="Deploy Savara validator" /> - <ant dir="${modules}/savara-validator-jbossesb" target="deploy"> - <property name="org.jboss.esb.server.home" value="${org.jboss.esb.server.home}"/> - <property name="org.jboss.esb.server.config" value="${org.jboss.esb.server.config}"/> - </ant> - </target> - - <target name="undeploy-savara-validator" depends="check.deploy.props" description="Undeploys Overlord CDL validator to the server"> - <echo message="Undeploy Savara validator" /> - <ant dir="${modules}/savara-validator-jbossesb" target="undeploy"> - <property name="org.jboss.esb.server.home" value="${org.jboss.esb.server.home}"/> - <property name="org.jboss.esb.server.config" value="${org.jboss.esb.server.config}"/> - </ant> - </target> - - <target name="deploy" depends="deploy-savara-runtime, deploy-savara-validator" description="Deploy Savara components."/> - - <target name="undeploy" depends="undeploy-savara-runtime, undeploy-savara-validator" description="Undeploy Savara components."/> </project> Modified: runtime/trunk/docs/pom.xml =================================================================== --- runtime/trunk/docs/pom.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/docs/pom.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -18,7 +18,6 @@ <modules> <module>userguide</module> <module>samplesguide</module> - <module>gettingstartedguide</module> </modules> </project> Modified: runtime/trunk/docs/samplesguide/pom.xml =================================================================== --- runtime/trunk/docs/samplesguide/pom.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/docs/samplesguide/pom.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -7,10 +7,10 @@ <groupId>org.jboss.savara.docs</groupId> <artifactId>samplesguide</artifactId> <packaging>jdocbook</packaging> - <name>Savara::docs::samplesguide</name> + <name>Savara::Runtime::docs::samplesguide</name> <parent> - <groupId>org.jboss.savara</groupId> + <groupId>org.jboss.savara.runtime</groupId> <artifactId>docs</artifactId> <version>1.0-SNAPSHOT</version> </parent> @@ -82,5 +82,4 @@ </plugins> </build> - </project> Modified: runtime/trunk/docs/userguide/pom.xml =================================================================== --- runtime/trunk/docs/userguide/pom.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/docs/userguide/pom.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -7,10 +7,10 @@ <groupId>org.jboss.savara.docs</groupId> <artifactId>userguide</artifactId> <packaging>jdocbook</packaging> - <name>Savara::docs::userguide</name> + <name>Savara::Runtime::docs::userguide</name> <parent> - <groupId>org.jboss.savara</groupId> + <groupId>org.jboss.savara.runtime</groupId> <artifactId>docs</artifactId> <version>1.0-SNAPSHOT</version> </parent> @@ -82,5 +82,4 @@ </plugins> </build> - </project> Modified: runtime/trunk/jbossesb/src/main/configs/esb-assembly.xml =================================================================== --- runtime/trunk/jbossesb/src/main/configs/esb-assembly.xml 2009-11-15 13:05:24 UTC (rev 86) +++ runtime/trunk/jbossesb/src/main/configs/esb-assembly.xml 2009-11-15 15:48:31 UTC (rev 87) @@ -20,7 +20,7 @@ <dependencySet> <outputDirectory>/</outputDirectory> <includes> - <include>org.jboss.savara:savara-runtime-jbossesb</include> + <include>org.jboss.savara.runtime:savara-runtime-jbossesb</include> </includes> </dependencySet> </dependencySets>

14 years, 5 months

1
0
0 / 0

← Newer
1
2
3
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

savara-commits November 2009