yes, it is wierd, but is definitively happening, and as I've tried to
describe before, only when any of the scripting semantics are used.
My only guess is that it somehow has to do with classloaders and where
classes are being generated/compiled.
I am not sure but there were some indentified
yeah I don't think that bug was related (there was no file locking
involved).
So its happening with groovy as well as jython?
On 3/14/06, Kristofer Eriksson [EMAIL PROTECTED] wrote:
yes, it is wierd, but is definitively happening, and as I've tried to
describe before, only when any of the
I have no clues about that unfortunately, it does sound wierd. What would
cause a jar to be locked? Its almost as if tomcat hasn't finished
classloading or something.
On 3/10/06, Kristofer Eriksson [EMAIL PROTECTED] wrote:
yes, the problem is exactly that. The core drools jar files (and only
yes, the problem is exactly that. The core drools jar files (and only those)
are beeing held by tomcat (locked) when the application restarts which
prevents them from being deleted.
Thx
Kristofer
On 3/10/06, Michael Neale [EMAIL PROTECTED] wrote:
so the problem is with the jar files?
