Re: which settings are for jde-db-jdb-1-4 ?

poppyer <[email protected]> Tue, 27 Nov 2007 16:31:06 +0000
Newsgroups gmane.emacs.jdee
Message-ID <[email protected]>
Carlos Konstanski <[email protected]> writes:

> At Tue, 27 Nov 2007 12:00:29 +0000,
> poppyer  wrote:
>> 
>> Hi all,
>> 
>> Every time I switch to a jde buffer, it says:
>> Project file reload error: Invalid slot type: jde-db-jdb-1-4, :path, string, nil
>> 
>> Which settings am I missing?
>> 
>> Thanks,
>> poppyer
>
> Just glancing at jde-jdb.el, it looks like `jde-db-jdb-1-4' is a class
> which is a subclass of `jde-db-jdb'.  `jde-db-jdb' has a slot called
> `path', which is of type string.  It is supposed to contain the path
> to the jdb executable.  It is initialized with the value "jdb" (in
> JDEE 2.3.5.1 - which version are you running?)  I'd check two things:
>
> - Are you using JDEE 2.3.5.1?
>
> - In a bash shell, can you verify that jdb is on your PATH?
>
> If you cannot launch jdb from a bash shell, you have little hope of
> getting it to work in JDEE.
>
> In the same file, there is a function called `jde-jdb-get-jdb'.  This
> is where an instance of the appropriate subclass of `jde-db-jdb' is
> obtained.  Had you provided a stack trace, I'm sure a call to this
> function would appear near the top.  You can see that you'll get an
> instance of `jde-db-jdb-1-4' if you have any version of java which is
> 1.4 or higher.  Which version are you running?
>
> At the end of this function, there is this bit of code:
>
>     (oset jdb :path (jde-get-jdk-prog (oref jdb :exec-name)))
>
> Perhaps this is where your problem occurs?  (Please provide a debugger
> stack trace.)  If the call to `jde-get-jdk-prog' returned `nil', that
> could account for your error.  The purpose of this function call is to
> get the full path to your jdb executable.  Again, it indicates that
> jdb is not on your PATH.
>
> Carlos Konstanski


Thanks Carlos, you are pointing me the right direction.
Yes, I don't have the jdb installed. 
Now I use (setq jde-debugger '("JDEbug")) to avoid calling the jdb,
since I never use the debugger.

Thanks,
poppyer
--