On 1/4/2007 10:47 AM, Bertrand Delacretaz wrote:
On 1/4/07, Lars Huttar <[EMAIL PROTECTED]> wrote:
...Method (1): using Jetty
The first method, "cocoon.bat servlet-debug" (as recommended in [1]),
appears to start OK. But when you try to browse to
http://localhost:8000/, the browser gives the error:...
FWIW, the following works with the current 2.1.10 release, macosx, JDK
1.5:
-Build from scratch, directly from the release archive
-Run ./cocoon.sh servlet-debug
-Connect to http://localhost:8888 from browser
-Connect to port 8000 from the Eclipse remote debugger
You might want to try that, to compare with what you're seeing. The
Cocoon release shouldn't make a difference.
-Bertrand
Thanks for your reply.
The steps you mentioned for starting jetty used to work for me, but
don't anymore; so I would agree with Grzegorz that something must be
wrong with my configuration. But I'm at a loss to know what's wrong.
Does Jetty output more informative error messages into a log anywhere?
Or where might I find Jetty configuration that I might have messed up
earlier and forgotten about it? The files in tools\jetty\conf seem to be
untouched.
On 1/4/2007 12:03 PM, Grzegorz Kossakowski wrote:
Lars Huttar napisał(a):
... So, I still have the same problem.
When I browse to http://localhost:8888/, Jetty outputs the following
message to the console:
09:44:51.166 EVENT Started HttpContext[/]
So I know Jetty is to some degree "catching" the request.
Also, I neglected to mention that the heading above "No context on
this server matched..." was "Error 404 - Not Found."
It's odd. Which version of java do you have? Do you have something like
this as output on jetty console:
18:48:40.007 EVENT Started SocketListener on 0.0.0.0:8888
18:48:40.007 EVENT Started [EMAIL PROTECTED]
?
I have the first but not the second:
09:42:46.355 EVENT Started SocketListener on 0.0.0.0:8888
09:42:46.355 WARN!!
org.mortbay.util.MultiException[org.xml.sax.SAXParseException: Document
root element "web-app", must match DOCTYPE root "null".]
at org.mortbay.http.HttpServer.start(HttpServer.java:640)
at org.mortbay.jetty.Server.main(Server.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
09:44:51.166 EVENT Started HttpContext[/]
The WARN is nothing new, I think, so I've been ignoring it... maybe I
shouldn't be??
Any idea what document is failing to parse? Is the document root element
really supposed to be <null>?
I've checked out (on linux, but I do remember I have debugged C2.1.7 on
WinXP long time ago) and it just works so it must be something with your
configuration.
If I don't find a solution for debugging with Jetty, I may try Eclipse
as you suggest. The headache there is that if I really do have to
maintain a SVN working copy of Cocoon for debugging, I will have to
keep manually updating it with changes from my development copy of
Cocoon, in which I have cocoon.xconf and some other Cocoon config
files tracked by our internal SVN repository. Is it possible to use
Eclipse to debug Cocoon without involving Subclipse?
I'm not sure if I understand you correctly but:
1. Use Eclipse as debugger in any case (if you use jetty or tomcat)
I was going to try raw jdb as a simplest case, to see if it worked; if
so then I could work up to getting Eclipse configured to work with
Cocoon. Or am I mistaken in thinking that you can debug Cocoon without
Eclipse?
2. Eclipse must only know about sources of your application and Cocoon
to debug happy your applications. It does not care about your configs
etc. You just have to import Cocoon as project into Eclipse's workspace
and create project for your java classes and set-up necessary
dependencies on jars. That's all.
That's good to know. I figured you could probably debug Cocoon in
Eclipse without having a SVN working copy of Cocoon, but the
instructions at http://wiki.apache.org/cocoon/LoadInEclipse assume you
check Cocoon out of SVN. I'm not familiar with Eclipse so was reluctant
to spend time figuring out how to do it independent of the instructions.
E.g. it seems non-trivial to learn how to specify where all the jar
files are, and all the source code, etc. Are there instructions anywhere
on how to do this? I guess I will have to bite the bullet and learn
Eclipse if I want to use Eclipse to debug Cocoon.
On 1/4/2007 12:14 PM, Mark Lundquist wrote:
On Jan 4, 2007, at 7:49 AM, Lars Huttar wrote:
If I don't find a solution for debugging with Jetty, I may try
Eclipse as you suggest. The headache there is that if I really do
have to maintain a SVN working copy of Cocoon for debugging,
huh, why do you have to have Cocoon sources in Subversion just to
debug with Eclipse? What does Eclipse care whether the sources are in
Subversion?
(See above response.)
I will have to keep manually updating it with changes from my
development copy of Cocoon, in which I have cocoon.xconf and some
other Cocoon config files tracked by our internal SVN repository.
Is it possible to use Eclipse to debug Cocoon without involving
Subclipse?
Subclipse!?!
Now, I /do/ keep Cocoon sources in my own Subversion repository [1],/
but/ I /don't/ use Subclipse. Just because your sources are in
Subversion (and once again, debugging with Eclipse doesn't require
this), wouldn't mean you have to use Subclipse.
HTH ...? :-)
Yes it does...
—ml—
[1] — http://wiki.apache.org/cocoon/CocoonVendorBranch
This looks very helpful, independent of the above problem.
Thanks again to all,
Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
