[overlord-issues] [JBoss JIRA] Commented: (SOAG-72) Business pojo class can't be hot-deploy

[Jeff Yu (JIRA)]

    [ https://jira.jboss.org/jira/browse/SOAG-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12438433#action_12438433 ] 

Jeff Yu commented on SOAG-72:
-----------------------------

The problem is that:

>From the debugging.

When we store the updated class into database, it used the new class, thats right. But after that, if we retrieve that serialized object from database, it is becoming an obsolete object.

		ByteArrayInputStream bais = new ByteArrayInputStream(serializedObject);
		try {
			ObjectInputStream in = new ObjectInputStream(bais);
			this.businessObject = in.readObject();
			in.close();
		} catch (Exception e) {
			throw new RuntimeException("Error in reading Object", e);
		}

Not sure which cache is not updated. 

> 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