I guess the problem was that the type of the variable value was not any of jBPM's built-in persistable types. The solution might have been making the type serializable.
sbhatti, since you ask, this is the easiest but hardly the best approach. Serialization is slow and makes the stored data inaccesible piecewise. The best way to persist a custom type is to create a Hibernate mapping document and reference it from hibernate.cfg.xml. The drawback is, of course, that you have to know how to write mappings (and preferrably write a test case) but learning is a breeze with all the Hibernate tutorials around. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937560#3937560 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3937560 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
