beanshell 'locks' jars, bsh-exit not working
[EMAIL PROTECTED] writes: Hi, I have two problems: 1. When I do a get latest from our source repository (Visual SourceSafe) and it tries to replace a jar in my project with bsh running I get the message file xx is already open. According to VSS help this means: Either another user or VSS has the file locked. If you don't have VSS, try overwiting a jar in Windows Explorer with bsh running - it won't let you do it, although the error is less obvious. I appreciate that if a jar changes, then the classes loaded in the bsh JVM are effectively out of date, but it would be nice if I bsh didn't lock files and I could just C-c C-v C-q to re-load the classes. I'll look into this. 2. I used to get around #1 by doing bsh-exit then redoing the get latest, but it seems like that hasn't worked for a few betas. bsh-exit now gives the message: eieio-generic-call: No method definition: bsh-running-p, (unbound). Currently I have to quit and restart Emacs. That's a result of the decision to remove the dependency of the Beanshell interface on the JDEE. The JDEE has new commands for starting and ending the Beanshell: jde-bsh-run and jde-bsh-exit, respectively. The menu items JDE-Interpreter-Start and JDE-Interprester-Exit invoke these commands. Paul
unusual symbol lookup feature
Hi,
I find C-c C-v C-y excellent and find myself using it more and more, but
occasionally have this odd behavoir:
Point is in class A like so:
public class A {
...
new X().--|--someMethod()
...
}
and I hit C-c C-v C-y. I get the dialog:
===
Which class?
(*) java.lang.Object
( ) org.omg.CORBA.Object
( ) com.inprise.vbroker.CORBA.Object
( ) org.omg.CORBA.Object
[Ok] [Cancel]
===
At the same time JDE loads class X in the other window. If I select Ok
or Cancel we stop there and the cursor rests at:
public class X--|-- extends Y { ...
Actually class Y, which as you can see is the super of X, implements
the method. And if I then go back to the original point and redo C-c C-v
C-y the screen splits and in one I have class X (again!) and in the other
class Y with point correctly placed after the method name.
IMHO class X is a red herring and should not be loaded at all!
Also, I can repeat this double-attempt sequence over and over with the
same result, so JDE apparently does not learn where the method is
defined.
Does anybody else also have this?
Thanks,
Maurice
Maurice Nicholson
Senior Analyst Programmer
SITA Advanced Travel Solutions
Tel: +44 (0) 1483 414411
Fax: +44 (0) 1483 414122
Direct: +44 (0) 1483 521294
Email: [EMAIL PROTECTED]
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient, please notify us
immediately and delete it from your system. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon
this information by persons or entities other than the intended recipient
is prohibited. The views and opinions expressed in this e-mail message
are the author's own and may not reflect the views and opinions of SITA.
Re: unusual symbol lookup feature
I just noticed the same thing yesterday. Also, it imported a class
(the same class, in you instance it would be class A) as well. I
don't know what that was about. I figured I just hit a wrong key
combination, but maybe not..
[EMAIL PROTECTED] writes:
Hi,
I find C-c C-v C-y excellent and find myself using it more and more, but
occasionally have this odd behavoir:
Point is in class A like so:
public class A {
...
new X().--|--someMethod()
...
}
and I hit C-c C-v C-y. I get the dialog:
===
Which class?
(*) java.lang.Object
( ) org.omg.CORBA.Object
( ) com.inprise.vbroker.CORBA.Object
( ) org.omg.CORBA.Object
[Ok] [Cancel]
===
At the same time JDE loads class X in the other window. If I select
Ok
or Cancel we stop there and the cursor rests at:
public class X--|-- extends Y { ...
Actually class Y, which as you can see is the super of X, implements
the method. And if I then go back to the original point and redo C-c C-v
C-y the screen splits and in one I have class X (again!) and in the
other
class Y with point correctly placed after the method name.
IMHO class X is a red herring and should not be loaded at all!
Also, I can repeat this double-attempt sequence over and over with the
same result, so JDE apparently does not learn where the method is
defined.
Does anybody else also have this?
Thanks,
Maurice
Maurice Nicholson
Senior Analyst Programmer
SITA Advanced Travel Solutions
Tel: +44 (0) 1483 414411
Fax: +44 (0) 1483 414122
Direct: +44 (0) 1483 521294
Email: [EMAIL PROTECTED]
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient, please notify us
immediately and delete it from your system. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient
is prohibited. The views and opinions expressed in this e-mail message
are the author's own and may not reflect the views and opinions of SITA.
