As someone who asked one of those FAQs on here, maybe I can help a little too. Maybe even this time I won't be too redundant. First off, I've been an (X|Lucid|FSF)Emacs user for 10+ years, but never really tried the Lisp stuff. I'm really just a user. It's really difficult to really find what I am looking for when it comes to JDE. One the web site, it appears to want to be a navigation/toc on the left frame, contents on the right. So then why does seemingly every link pop up a new window? It makes navigating the site looking for something more difficult than it has to be, at least for me. Searching the mailing list is extremely frustrating. For a while, every time I hit the ';' key, it would insert a return and indent me on the next line. I really did not want this behavior. I was able to turn it off in C-mode, but it would come back whenever I entered JDE. Just try searching the mailing list archive for that one. There were a couple of variables I figured were involved, searching for them revealed every person who included their .emacs in the message or other helpful debugging content. So I was afraid to post on here again and lived with it for a while until I finally had some time to track it down. As for additional docs on JDEbug, the existing ones were nearly adequate to get me going. Never using JPDA before, I didn't realize that the Classic JIT in 1.2.2 didn't like the debug options and would give an illegal access error in windows. Apparently HotSpot is OK with it, and looking at the Sun JPDA site I found that -Xnoagent and -Djava.compiler=NONE were necessary. Had these two flags been mentioned on the JDEbug page, I would have been up and running in minutes of curiosity. As an aside, JDEBug works much better than the Cafe debugger for debugging EJBs in WebLogic 5.1. As another aside, while on the topic of useful JDEbug tidbits ... Setting a breakpoint before attaching to a process is pointless, it just gets ignored. I have no idea why I can't get the CLI window up, and in some situations would give anything to get that window. Setting a breakpoint on a method signature does not perform a "stop in package.Class.method" like one would expect, it merely sets a breakpoint on a line that will never be hit. And lastly, I am more than willing to help out in any way I can. I *really* like JDE! What can/should I do? > -----Original Message----- > From: Ben Speakmon [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 27, 2000 9:44 AM > To: [EMAIL PROTECTED] > Subject: re: FAQs > > > Since the response to this idea has been positive, here's > what I suggest: > Each time someone asks a FAQ, like "why doesn't jdb work?" or > "how can I > debug servlets/jsp?" whoever answers the question on the list > posts the > answer on the FAQ on the site. It would also be cool to link > to the root > of the discussion on the mailing list archive. When people ask on the > list, we can give them specific URLs that answer their > questions instead > of saying "it's in the mailing list, go find it" after which > they return > and say "I checked and couldn't find this". (This is not an > indictment of > them; who really has time to dig through all that info when there's a > deadline to meet?) > > While I'm going here, maybe some quick-start guides, such as the one > written for Linux, to get up and going with JDEBug, would > also not be out > of place there. > > In any case, I'll try to put up good information when I run > across it, and > I hope that this takes off. > > Thanks for your time, guys. > > > Hi Ben, > > > > Yes, I had intended the FAQ to be a group effort. That's > why it is based on > > FAQ-o-matic. I would really appreciate help in maintaining it. > > > > Regards, > > > > - Paul > > > -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > Benjamin A. Speakmon > Associate Software Engineer, Web Products Division > TeleCommunication Systems, Inc. >
