[JBoss JIRA] Created: (SOAG-77) Trailblazer example documentation improvments
by Jeff Yu (JIRA)
Trailblazer example documentation improvments
---------------------------------------------
Key: SOAG-77
URL: https://jira.jboss.org/jira/browse/SOAG-77
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 1.0 MR1
Reporter: Jeff Yu
Assignee: Mark Little
Fix For: 1.0 MR2
Thanks Jeff Delong for following suggestions and feedback.
------------------------
A few suggestions on how to improve the documentation:
1) Have the readme refer to the docs/samplesguide/SamplesGuide. While much of the information is redundant, the SamplesGuides has the information on the ChoreographyMonitor and the error-client.
2) In the SamplesGuide.pdf, the code snippet from LoanBroker.java is unreadable.
3) Under 10 2 It says to run the commands from step 6 on. Is that really necessary?
4) Add more information on the role of the LoanBroker.java class, and how it's choice of
if (score >= 4) {
//step 3a - send to Bank - async
System.out.println("sending to first Bank...");
sendToBank(bank1Invoker, customer, "b1");
Implements the Choreography conditional expression: cdl:getVariable('creditCheckResult','','//@score') >= 4
5) It would be nice to have an architectural discussion here about how this choreography is being monitored. (perhaps this is described in another document I have yet to read).
--------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (SOAG-68) Async Perform
by Gary Brown (JIRA)
Async Perform
-------------
Key: SOAG-68
URL: https://jira.jboss.org/jira/browse/SOAG-68
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Jeff Yu
Currently the Brokerage example iterates through a list of suppliers to find the best quote, before proceeding to perform a credit check and complete the transaction.
However the list of suppliers is processed using a loop containing a synchronous perform, so each supplier is dealt with in turn.
The next step is to cater for an asynchronous perform, where the suppliers can be dealt with concurrently (i.e. so multiple sub-sessions active at the same time). This would require the 'WhenAction' to block, awaiting all of the sub-sessions to complete, before making its decision regarding the best quote.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (SOAG-65) Blocking/waiting behaviour for WhenAction
by Gary Brown (JIRA)
Blocking/waiting behaviour for WhenAction
-----------------------------------------
Key: SOAG-65
URL: https://jira.jboss.org/jira/browse/SOAG-65
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Conversation Runtime
Reporter: Gary Brown
Assignee: Jeff Yu
Currently the WhenAction does immediate evaluation of an expression. This construct needs to enable blocking/waiting behaviour if the expression evaluates to false - using the services of an external mechanism that can monitor an expression, and re-evaluate it whenever a change occurs to the state for the session, and then trigger the appropriate service descriptor once the expression does evaluate to true.
The expression could also represent a timeout, and therefore this mechanism could be combined with the issue related to the WhenAction handling timeouts (SOAG-33).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (SOAG-97) Have CDL validation deployment lookup Service EPR
by Jeff DeLong (JIRA)
Have CDL validation deployment lookup Service EPR
-------------------------------------------------
Key: SOAG-97
URL: https://jira.jboss.org/jira/browse/SOAG-97
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WS-CDL
Affects Versions: CONTINUING
Reporter: Jeff DeLong
Assignee: Mark Little
Instead of using annotations in the CDL model to add the ESB EPR to the service/participant for runtime validation purposes, perhaps as part of deployment into the server the deployer could use the service name to lookup the EPR, and then add this information to the validation configuration.
This would save the developer from having to copy runtime deployment information into the CDL files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years