"kukeltje" wrote : 1: it is not ignored by hibernate, hibernate can not look into the process classloader afaik | 2: Correct, access is the problem. | | A (not specifically the best) solution is to use the war for this if versioninig of this UrlLock class is not needed. Ouch! a classloader issue. That kind of problems stole a lot of my time in my recent eclipse plugin project :-( I could imagine that this is especially hard to solve if I configure jBPM to access hibernate via a datasource. Otherwise jBPM might have the chance to adjust the SessionFactory (found http://opensource.atlassian.com/projects/hibernate/browse/HHH-3603 and http://forum.hibernate.org/viewtopic.php?p=2403881 dealing with related problems). Not to version the entities might be possible (have to check this) although this would be the only "hole" in the process versioning. Either way it might be worth mentioning this issue in the userguide. Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219407#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...