sorry, my bad.
now that you mention it, it does ring a bell that we looked at this some time ago.
let's release the hacky fix and see if it stands.
"alex.guizar(a)jboss.com" wrote : Fady fixed it with a hack on VariableInstance, which goes to prove that a hack is faster than discussion ;-)
indeed :-)
but be very carefull with classloader hacks. very often they backfired on me and i spend lots of time afterwards fixing it in different environments.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155223#4155223
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155223
Bernd and other folks' examples in JBPM-1024 are about storing serialized objects in the variables, which is what I think is worth addressing. These objects cannot be deserialized if the class files are only present in the process archive.
Now I understand what you meant by hibernate not knowing of the class, but hibernatable objects are not what JBPM-1024 is about. As Ronald points out, fixing the issue for hibernatable classes is harder. I don't know how to override hibernate's class loader except for overriding the context class loader, which will certainly open a can of worms.
I committed a unit test (CustomSerializableVariableDbTest) which shows that JBPM-1024 affects 3.2.2 but not the current CVS head. Fady fixed it with a hack on VariableInstance, which goes to prove that a hack is faster than discussion ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155215#4155215
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155215
Hi Tom,
Sorry, but we started this thread indeed with just serializing objects into blobs.
My use case was: Get a sample running with the web console. There I added some "business objects" to the process by an action handler. These objects were just deployed together with the process definition. When I arrived in a task form I got the exception, because the class cannot be found for deserializing (and the root cause isn't shown in the console, so it wasn't straight forward to figure out what was the problem). It wasn't a hibernate class and not the any association...
With a hibernate class IT MUST be on the classpath, because it is in the hibernate mapping, no problem here I think...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155214#4155214
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155214
anonymous wrote : still hibernate will not know of the class.
Why does hibernate have to know about the process classes? As I see it, hibernate only needs to provide the byte array. It is SerializableToByteArrayConverter's responsibility to read an object from the bytes. A subclass of ObjectInputStream may be required to bring the ProcessClassLoader into the equation without touching the context class loader.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155166#4155166
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155166