Paul,
I couldn't find any JVM parameters that dealt with the behavior you
described, and writing a class loader is way more effort than I'm willing to
expend for this small annoyance. I took your advice to use the directory
where the class files were, rather than the jar file, and that worked like a
charm. Thanks,
-Matt
PS I guess I was thinking there would be some sort of exposed API (whether
in bsh or jdee) that would allow you to, in effect, call close() on the
stream attached to the file. Does anyone know of such a thing? (Feel free
to point me to documentation.)
PPS I don't believe I put that link in my first email; I think gmail thought
that was an ip address, and linked automatically. Thanks for making me look
like a prat, google!
On Thu, Aug 28, 2008 at 5:33 PM, Paul Landes <[EMAIL PROTECTED]> wrote:
> I don't have the answer, but I think I might be able to narrow it
> down, which is the JVM. Look to see if there are some JVM parameters
> you can pass so that once the classloader loads what it needs from the
> jar, it closes the file.
>
> As you probably know, windows uses pessimistic locking so the kernel
> doesn't let you do much with the file (depending on how it is opened).
>
> You might want to build classes in a directory structure instead and
> use that directory as a classpath element. You might get better
> results.
>
> You could of course write or extend a class loader and then put it in
> the prebootclasspath, but I'd try building classes in a directory
> first (i.e. javac -d <DIR_A> ..., then java -classpath DIR_A;path...)
>
>
>
> Matthew Wyatt writes:
> > All,
> > I've noticed that if I use JDEE to complete a method name, I can no
> > longer delete the jar file that the BeanShell uses to look up the method
> > names and signatures until I kill the process in the *JDEE bsh* buffer,
> > because the BeanShell is holding onto the file handle. Is there a way
> to
> > force it to let go of the file after completing?
> > I'm running on Win XP, SP 2, Emacs 22.2, JDE 2.3.5.1.
> > If this is a known BeanShell issue, then I'm sorry to bring it up in
> this
> > mailing list. I couldn't find anything on this issue on google.
> > Thanks for your time,
> > -Matt
> > <div dir="ltr">All,<br> I've noticed that if I use JDEE
> to complete a method name, I can no longer delete the jar file that the
> BeanShell uses to look up the method names and signatures until I kill the
> process in the *JDEE bsh* buffer, because the BeanShell is holding onto the
> file handle. Is there a way to force it to let go of the file after
> completing?<br>
> > I'm running on Win XP, SP 2, Emacs 22.2, JDE <a href="
> http://2.3.5.1";>2.3.5.1</a>.<br> If this is a known BeanShell
> issue, then I'm sorry to bring it up in this mailing list. I
> couldn't find anything on this issue on google.<br>
> > Thanks for your time,<br>-Matt<br></div>
> >
> -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the
> world
> >
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> > jdee-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/jdee-users
>
>
> --
> Paul Landes
> [EMAIL PROTECTED]
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
jdee-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jdee-users
