[
https://jira.jboss.org/jira/browse/SOAG-72?page=com.atlassian.jira.plugin...
]
Jeff Yu commented on SOAG-72:
-----------------------------
The reason for this is caused by that we are storing the business pojo object as
serialized object.
Not sure when it got the serialized object from database, it will still be the old one.
Need to be investigated more.
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