Hi Jürgen, I'm not sure if your suggested patch is sufficient in all cases. If I understood Xerces' DOM model correctly, then it appears to be not thread-safe, not even for read-only access. In this case just forcing a pre-initialization of the lazy model is probably not enough.
I'm currently thinking about cloning the element for those parts that may concurrently access the node. How does that sound? Is it possible to easily reproduce the problem in a test case? Or do you have some kind of testbed where you could test a patch? Cheers, Tammo juergen.schumac...@empolis.com wrote: > Hi Tammo, > >> Is the workaround the proposed fix mentioned in ODE-503? > > Basically yes, but I cannot do it immediately in SerializableElement, > because I do not want to change the code released by ODE, but need to iterate > separately over the process definitions after the deployment has finished. > And it's a bit nasty to access them from outside the BpelServerImpl (: > > Cheers, > Juergen. > > > -- Tammo van Lessen - http://www.taval.de
