Rebuild conversation aware sample jboss-esb.xml configurations to be based on generated version
-----------------------------------------------------------------------------------------------
Key: SOAG-78
URL: https://jira.jboss.org/jira/browse/SOAG-78
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: WS-CDL
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0 MR2
Samples for conversation aware actions should be based on generated version, to make it easier for end-user to generate a new skeleton of the behaviour from the choreography, and compare it against the fully implemented version.
--
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
Business pojo class can't be hot-deploy
----------------------------------------
Key: SOAG-72
URL: https://jira.jboss.org/jira/browse/SOAG-72
Project: SOA Governance
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Conversation Runtime
Affects Versions: 1.0 MR1
Reporter: Jeff Yu
Assignee: Jeff Yu
The steps to reproduce:
1. Deploy the overlord cdl to JBoss ESB.
2. Run the purchasing example.
3. Open the common/creditAgency/src/com/acme/services/creditAgency/CreditAgencyPurchase.java
Make the isCreditValid() method return false;
4. Redeploy the creditAgency esb artifact.
5. The update won't take effect by using hot deploy.
--
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
Investigate BPEL deployment against various vendor
--------------------------------------------------
Key: SOAG-74
URL: https://jira.jboss.org/jira/browse/SOAG-74
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 1.0 MR2
Reporter: Jeff Yu
Assignee: Jeff Yu
Need to investigate the various BPEL runtime's deployment, such as ActiveBPEL, Apache ODE and other closed source BPEL runtime.
--
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
Using JPA instead of Hibernate API directly
-------------------------------------------
Key: SOAG-46
URL: https://jira.jboss.org/jira/browse/SOAG-46
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Conversation Runtime
Affects Versions: 1.0 CR1
Reporter: Jeff Yu
Assignee: Jeff Yu
Might be better to use JPA instead of hibernate directly, which means need to use the hibernate-entityManager library.
--
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
Refactor the conversational actions package name.
-------------------------------------------------
Key: SOAG-81
URL: https://jira.jboss.org/jira/browse/SOAG-81
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Conversation Runtime
Affects Versions: 1.0 MR1
Reporter: Jeff Yu
Assignee: Jeff Yu
Fix For: 1.0 MR2
Will update the the conversational actions package name from 'org.jboss.soa.overlord.jbossesb' to 'org.jboss.soa.overlord.jbossesb.stateful'. Also need to update it in the examples configuration file - jboss-esb.xml.
--
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
Generate WS-BPEL from Choreography Description
----------------------------------------------
Key: SOAG-75
URL: https://jira.jboss.org/jira/browse/SOAG-75
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: WS-CDL
Affects Versions: 1.0 MR2
Reporter: Gary Brown
Assignee: Gary Brown
Generate BPEL 2.0 process descriptions from a choreography description.
NOTE: When this task has been completed, and the deployment framework has been built, then we might need to refactor the generation mechanism to identify commonality with the ESB Conversation Action mechanism. For now will keep the code bases separate until more information is known.
--
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
Build stateful fragment approach to JBoss ESB from CDL file.
------------------------------------------------------------
Key: SOAG-80
URL: https://jira.jboss.org/jira/browse/SOAG-80
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WS-CDL
Affects Versions: 1.0 MR1
Reporter: Jeff Yu
Assignee: Jeff Yu
Fix For: 1.0 MR2
In the M2 release, we are going to try another approach with JBossESB. Compared to the conversation runtime actions that we had in M1, we will try to build a stateful fragment (or technically, we called it statless) approach to the JBossESB.
--
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