[JBoss jBPM] - Jboss jBPM serialization problem
by Arutha
Hey,
I've got a question on sending Serializable objects over the bus. I know how this can be done, as I built an application creating a Pojo, sending it onto the bus, modifying it with JbossRules and spitting it out to another service off the bus.
My problem is this: I tied in the jBPM orchestration with this very same application, and as soon as I send the Serializable over the bus through the process definition now, it comes out the other end in the message.getBody().getContents(), but the get() method, returning an object, is empty this time.
I believe the cause is that I'm not converting the byte array the message holds in the get() to a jBPM format, as is done with the body contents :
<variable esb-name="eVar1" jbpm-name="counter" value="45" />
<variable esb-name="BODY_CONTENT" jbpm-name="theBody" />
I'm not doing that, since I have no idea how to.
Is this the cause, and if so, any way I can move the Serializable object in the message to the jBPM orchestration process and back to the ESB ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079138#4079138
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079138
19Â years
[JBoss jBPM] - Re: ClassCast Problem
by Arutha
Hey,
I had the same problem last week, I'd like to call "Cannot cast smtptoesb.server.smtpmail to smtptoesb.server.smtpmail". The cause of this was rather simple, but I still took many hours not relaxing in front of the TV to figure it out.
The problem for me was that Jboss worked with an older version of the class than the application itself, trying to cast will throw this problem. Try shutting down Jboss, removing all tmp related to this work, cleaning the build folder, redeploying it and running it again.
I realise it's not ideal, rebooting Jboss, I tried doing this @runtime, but Jboss locks the tmp-files that need to be deleted, and for some reason, even after redeploying in this situation, Jboss kept using the old Pojo class.
With 'older' version, I mean that even though the class may be exactly the same, it was compiled at an earlier time.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079132#4079132
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079132
19Â years