Hmm... and that means? :-)
Maybe it's me, but I still didn't get/understand an answer to my question:
* is BCELWrapperGenerator supposed to be thread safe or is the synchronization done elsewhere (the code that calls the generator)?
Now I looked deeper into the code that calls BCELWrapperGenerator and I can see, that there is no synchronization anywhere... So I'll just go ahead and patch BCELWrapperGenerator.
Rgds, Neeme
Berin Loritsch wrote:
Neeme Praks wrote:
Question: is BCELWrapperGenerator supposed to be thread safe? Especially .createWrapper(Class) method invocations?
I'm getting some weird errors from BCEL, from time to time, not always... So I was wondering... looking at the source, it is quite clear that it is not thread safe (usage of m_classGenerator and m_codeGenerator outside of synchronized block). But is it supposed to be?
If it is, then I'll just move the relevant sections inside the synchronized block, if nobody objects...
Most code generators are not supposed to be threadsafe, but our access to it should be. Since Fortress is supposed to be used in multithreaded environments, I suggest we take care of it the best way how.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
