The problem you describe sounds like the "bind freezes my app" mystery
bug that a few people seem to have run into. There are some detailed
problems reports in the CVS. Check out the tcljava CVS and look at these
files in the tcljava/bugs directory.
eventbug1
eventbug2
eventbug3
jbindbug.txt
The
Mo,
The problem was mine. The collection object that held listeners was null
(never initialized). That was the null pointer problem.
java::bind seems fine. I'm using it to do queries, etc. and it seems
reasonable. I will be working over Jacl in the next couple of days as our
team completes a
Was it a bug in the tcljava code or your code? Could the java::bind
command be improved in some way to avoid this type of problem in
the future?
Mo Dejong
Cygnus Solutions
On Thu, 9 Dec 1999, Randolph S. Kahle wrote:
> Mo,
>
> Problem solved in very short order because of your help.
>
> Thank
Mo,
Problem solved in very short order because of your help.
Thank you *very* much for the prompt reply to my email.
Regards,
Randy Kahle
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe:send ma
Mo,
Thanks for the tip.
the failure seems to be when a registration is invoked. Again, thanks for
the tip. I'll keep researching.
java.lang.NullPointerException:
at com..application.LoginController.addLoginListener(LoginController.java:37)
at java.lnag.reflect.Method.invoke(Native Metho
You might want to try this to get a stack trace. That might really
help track down the problem.
java::try {
java::bind $l processLogin login
} catch {NullPointerException e} {
$e printStactTrace
}
Mo Dejong
Cygnus Solutions
> * set l [Login getObject] works, I get a ref that supports thing
