This looks great.. I tried using the core of it plus hacking through
Eclipse.. However, I get back an error that it can't connect tomcat, and in
my lot I have lots of:
ENTRY org.eclipse.debug.ui 4 120 Jan 27, 2003 18:24:07.798
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[113]: java.io.IOException: Incorrect
handshake reply received: <HEAD><TITLE>M
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.PerformHandshake(Socket
TransportImpl.java:137)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.attach(SocketTransportI
mpl.java:42)
at
org.eclipse.jdi.internal.connect.SocketAttachingConnectorImpl.attach(SocketA
ttachingConnectorImpl.java:96)
at
org.eclipse.jdt.internal.launching.SocketAttachConnector.connect(SocketAttac
hConnector.java:113)
at
org.eclipse.jdt.internal.launching.JavaRemoteApplicationLaunchConfigurationD
elegate.launch(JavaRemoteApplicationLaunchConfigurationDelegate.java:59)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:147)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialo
g$6.run(LaunchConfigurationsDialog.java:1241)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:95)
I set as environment variables the two JDPA_* variables. Any one have a
suggestion? This is tomcat 4.1.16 and Eclipse 2.1.
Eric Pugh
-----Original Message-----
From: Quinton McCombs [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 5:52 PM
To: Turbine Users List
Subject: RE: Anyone using Eclipse with Turbine?
I created a Wiki page for documenting how to configure the various
serlet containers and IDEs for debugging. I only added Tomcat and
IntelliJ because that is what I use :-). If you are using a different
configuration and you know how to setup the debugging to work, please
add to this page. This has been a fairly common topic.
http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaTurbineIDEDebugging
> -----Original Message-----
> From: Lester Ward [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 27, 2003 4:02 PM
> To: 'Turbine Users List'
> Subject: RE: Anyone using Eclipse with Turbine?
>
>
> > I thought the only way to use Turbine was with Tomcat,
> > therefore I am using Tomcat. What are you using?
>
> I'm using JBoss 3.0.4 with Jetty as it's servlet container.
> I've been playing around with debugging in Eclipse. My
> solution is not perfect (because Eclipse does not allow you
> to make your build target somewhere outside of the project
> hierarchy, such as the deploy folder of your application server).
>
> Anyway, there are a few things that you can do.
>
> 1) Run your app server within the debugger! This is easy with
> JBoss, because JBoss is pure java. The easiest way to do this
> is to look at the script (or
> batch) file that you normally use to launch your app server,
> and then use Eclipse to build a debug target that matches.
>
> 2) Configure your application server to launch for remote
> debugging. This usually means changing the file used to
> launch the server, using settings similar to these:
>
> -classic -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
>
> You should be able to find a page that describes more
> specifically how to setup remote debugging with whatever app
> server you are using.
>
> One the server is running, you can attach Eclipse's debugger
> to it using a Remove Java Application launch configuration
> (see debug perspective, run menu, Debug...).
>
> 3) See if an Eclipse plugin provides native support for your
> app server. It might with Tomcat, but I am not sure.
>
> You might also check out an Eclipse plugin called Lomboz
(http://www.mycgiserver.com/~objectlearn/products/lomboz.html), which
claims to provide J2EE component and web application management for
Eclipse. I tried it out and didn't like the way it worked, but you might
find it useful.
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
