This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: strange problem with jetty
- From: John Smith <jsmith030416 at yahoo dot co dot uk>
- To: "kawa at sourceware dot org" <kawa at sourceware dot org>
- Date: Fri, 2 Dec 2011 15:45:43 +0000 (GMT)
- Subject: Re: strange problem with jetty
- References: <CAP33cna46J5rzps7pN0w_+8PCCJjcsAk=W_+_31_HqMsoCHLuQ@mail.gmail.com>
- Reply-to: John Smith <jsmith030416 at yahoo dot co dot uk>
I used this command line:
java -classpath /home/john/kawa-1.11/kawa-1.11.jar:jetty.jar:/usr/share/java/jetty-util.jar:/usr/share/tomcat5.5/common/lib/servlet-api.jar kawa.repl
and then from the REPL
#|kawa:1|# (org.mortbay.jetty.Server:start (org.mortbay.jetty.Server 8094))
2011-12-02 15:40:40.158:INFO::jetty-6.1.22
2011-12-02 15:40:40.289:INFO::Started SocketConnector@0.0.0.0:8094
and was able to point my browser to localhost:8094 and see a Jetty response.
I started out with exactly the same error as you.
However, I found the clues from using (require <org.mortbay........ )
This told me that Jetty needed the jetty-util.jar and servlet-api.jar files as dependencies.
Hope that helps.
John.
----- Original Message -----
From: RÄzvan Rotaru <razvan.rotaru@gmail.com>
To: kawa@sourceware.org
Cc:
Sent: Friday, 2 December 2011, 12:49
Subject: strange problem with jetty
Hi,
I'm having some strange problems with launching Jetty from Kawa. I am
launching "java kawa.repl", with jetty-6.1.26.jar in the classpath,
but the classes are not available:
#|kawa:1|# (org.mortbay.jetty.Server 8080)
/dev/stdin:1:1: warning - no declaration seen for org.mortbay.jetty.Server
/dev/stdin:1:1: unbound location org.mortbay.jetty.Server
ÂÂÂ at gnu.mapping.Location.get(Location.java:67)
ÂÂÂ at atInteractiveLevel$1.run(stdin:1)
ÂÂÂ at gnu.expr.ModuleExp.evalModule2(ModuleExp.java:284)
ÂÂÂ at gnu.expr.ModuleExp.evalModule(ModuleExp.java:185)
ÂÂÂ at kawa.Shell.run(Shell.java:281)
ÂÂÂ at kawa.Shell.run(Shell.java:194)
ÂÂÂ at kawa.Shell.run(Shell.java:175)
ÂÂÂ at kawa.repl.main(repl.java:848)
Any ideas what the problem could be. Classes from other jars, which
are also in the classpath have no problems.
Thanks,
Razvan