-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
"Paul Murphy" <[EMAIL PROTECTED]> wrote:
> Hello all,
> Has anybody succesfully used one the most widely used Java IDE
>tools like
>Visual Cafe, Jbuilder, Visual Age to debug a servlet IN JServ? I've seen
>suggestions about using jikes and emacs but I have to develop on NT(then
>deploy on Solaris) and I've gotten used to stepping through code in a nice
>GUI IDE.
>
>If this can be done, I think a lot more people would buy into developing
>with/for JServe.
I used Metrowerks CodeWarrior. It can also be done with Visual Cafe. I
should do a proper write up of the procedure. For now, I'm most familiar
with CodeWarrior so I'll give a brief synopsis of how to get this working.
You can follow a similar procedure for Visual Cafe (of course, with
appropriate differences). You can also use New Atlanta's servlet debugger,
currently a free beta download. Using New Atlanta's product is essentially
the same as using jserv to debug, except you use their stub class as the
main class.
- using CodeWarrior Pro 5 (www.metrowerks.com), NT4SP3, 128MB (note, one
nice thing about codewarrior is that it works well with 128MB, whereas you
need 196 or more to work with visual cafe)
- use Sun JDK1.2 -- codewarrior debugger is unstable with JDK1.1.8
- use Sun's JDWP (or is it JDPA?) anyway, it's their new per-release
interface for linking the debugger with the runtime. You don't really need
this, but it's supposed to make the debugger be able to do more things, so
you might as well try to get it; to install, you need to copy the dll's and
jar's into the corresponding folders in the JDK--I know, this sucks, and
there is a way to point to them using settings rather than overwriting, but
this is how I did it.
- see the codewarrior release notes, there's a registry setting that tells
codewarrior which jdk to use, though this is only relevant if you have more
than one sun jdk on your system
- turn manual mode on for apache jserv, then stop and restart apache to
make sure that any automatic-mode apache jserv is killed
- define a stub class, something like
public class ApacheJServ {
public static void main(String[] args)
{
org.apache.jserv.JServ(args);
}
}
- add the stub and the ApacheJServ.jar file to your project
- set your prefs for the project to generate an application and set the
application's main class to be the above stub class
- enable and run the debugger -- it should work...
P.S. before debugging servlets you should learn how to setup and run the
debugger for regular Java apps. There are a whole bunch of stupid little
things that can be confusing, and if you're also trying to do servlets then
you may not know if it's something to with the servlet engine or just some
odd thing in the IDE.
-- Ari Halberstadt mailto:[EMAIL PROTECTED] <http://www.magiccookie.com/>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
