On 1/4/2007 2:56 PM, Grzegorz Kossakowski wrote:
Lars Huttar napisał(a):
Lars Huttar napisał(a):
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>?
Mark explained in detail that this is not supposed to be that way, now I
will explain how to turn on debug logging in Jetty ;)
So before running cocoon.bat servlet[-debug] you have to set
JAVA_OPTIONS environment variable to '-DDEBUG' (double d is not typo!).
So in cmd line do this:
set JAVA_OPTIONS=-DDEBUG
cocoon.bat servlet[-debug]
and you will get _lots_ of debug messages, I think you will be satisfied
with the amount ;-)
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.
When you figure out how to get Jetty happy with servlet-debug we'll be
able to pass on this. I'll describe it in detail.
OK, I'll take you up on that offer! :-)
Jetty is now happy with servlet-debug.
My previous email mentions what happens when I try to debug it remotely
using Eclipse:
When I click the "Debug" button, I get a dialog saying, "Errors exist
in required project(s): Apache cocoon. Continue launch?"
I click Yes, and after a moment of "Establishing connection...", I get:
Exception occurred during launch
Reason: failed to connect to remote VM. Connection refused.
Details:
Connection refused: connect
Let me elaborate by saying what the errors in the "Apache Cocoon"
project are.
The first error I see is in org.apache.cocoon/CocoonTask.java. On line
132 it says "BuildException cannot be resolved to a type."
I assume that has something to do with specifying classpaths?
When I go to the Properties dialog for the project, and click on Java
Build Path, I see an info (yellow "!" triangle icon) message saying "2
build path entries are missing." Under "JARs and class folders on the
build path", it lists a bunch of jars, starting with
altrmi-common-0.9.2.jar. The last two have yellow "!" triangle icons:
C:/Program Files/Apache Software
Foundation/cocoon-2.1.7/build/cocoon-2.1.7/classes and .../mocks.
If I expand them, there is an item "Access rules: No rules defined"
under each.
That's as far as I know how to get... it's not clear to me how these
path entries are "missing". (The folders "classes" and "mocks" exist on
disk.)
Any idea what I should do? Maybe "Add JARs" or Library or Class Folder?
Thanks for your help,
Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
