Carsten Ziegeler wrote: > > Sylvain Wallez wrote > > That's an interesting approach also, as all work happends > from Eclipse. > > However, lauching "cocoon servlet-debug" allows to start the > > application independently of Eclipse and attach the > debugger only if needed. > > > > So both approaches have their pros and cons depending on > the kind of > > roundtrip that's needed. > Sure. But you can also launch cocoon from within eclipse in > "run" mode. > > > > > Is there some special setup required to launch Jetty from Eclipse? > > > No. Just set Jetty as the main class, add the configuration > to startup Jetty (like port etc.) - you can simply copy/paste > this from the cocoon.sh/bat file and that's it. >
I use this setup: - make sure ./tools/loader is on your eclipse classpath (it isn't by default) - create an eclipse run configuration for Jetty Cocoon: 1. On configurations 'Main' tab use 'Loader' as the main class. 2. On the Arguments tab set: Program arguments: "tools\jetty\conf\main.xml" VM arguments: "-Djava.endorsed.dirs=./lib/endorsed" "-Dwebapp=./build/webapp" -Dorg.xml.sax.parser=org.apache.xerces.parsers.SAXParser -Djetty.port=8888 -Djetty.admin.port=8889 "-Dhome=." "-Dloader.jar.repositories=./tools/jetty/lib,./lib/endorsed" -Dloader.main.class=org.mortbay.jetty.Server Unico
