[Laszlo-dev] JRun 4 support / jdom
dhughes at alagad.com
Sun Jan 16 10:36:54 PST 2005
Thanks for the info. At this particular point in time I'm not going to
promise anything at all. There's about a 50/50 chance I'll just set Tomcat
up to work with IIS and forget about JRun.
However, time permitting, I will sit down and see if I can build Laszlo. If
that works I'll dig into the code a bit and see what I can break.
If we all get lucky maybe something will come of this. Don't hold your
From: laszlo-dev-bounces at openlaszlo.org
[mailto:laszlo-dev-bounces at openlaszlo.org] On Behalf Of Eric Bloch
Sent: Sunday, January 16, 2005 1:04 PM
To: OpenLaszlo platform development and bug reporting
Subject: Re: [Laszlo-dev] JRun 4 support / jdom
Doug Hughes wrote:
> 1) Is there room in the community for someone who wants Laszlo to run
> on JRun?
Yes, Laszlo is intended to be 'servlet-container-agnostic'.
> 2) Are there specific reasons JRun is not supported?
Other than time to find and fix problems, no. JRun is known to have
some java class loading conflicts. We'd be thrilled if someone could
> 3) Are there resources and people who will be willing to help me out a
> little as I get up to speed on this?
I can help with some issues as I'm familiar with some of these issues.
> 4) What sort of processes are gone though to begin official support for
> a specific platform such as JRun?
We have servlet container compatibility tests. Mark Davis has full details.
> 5) Are there any hints on how someone might begin approaching the errors
> listed below?
> Thanks, I look forward to hearing back from you guys.
> Here are the details I have on the errors.
> When I access an lzx file (any that I've tried) I see this error
> returned from JRun via the web browser. This page has the title "JRun
> Servlet Error":
lps 2.2.x requires jdom b8. You could provide a patch to bring lps 2.2
to jdom 1.0 (see task on http://openlaszlo.org/wiki).
Or youi can configure jrun to prefer the classes in the lps webapp. I
did this once and can dig up the details. This is obviously easier than
the port to jdom 1.0 although the port is more valuable.
Once you get this done, I suspect you'll hit another conflict or two.
We've yet to have the time and resources to find and fix them. One of
them had to do with our XSLT jar (saxon) and another was appeared to be
one of the oft-reported commons-loggging disasters
(FYI, org.openlaszlo doesn't use commons-logging directly. But
commons-httpclient does and we rely heavily on commons-httpclient. I
did make a version of commons-httpclient that avoids commons-logging and
can provide it, if you want to try it.)
Best of luck!
> Info from the error log:
> 01/16 10:58:56 error
> at com.laszlosystems.server.Configuration.<init>(Configuration.java:59)
> at com.laszlosystems.server.LPS.initialize(LPS.java:60)
> at com.laszlosystems.servlets.LZServlet.initLPS(LZServlet.java:164)
> at com.laszlosystems.servlets.LZServlet.doGet(LZServlet.java:232)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
> at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
> at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
> at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
> Thanks again,
> Doug Hughes
> Laszlo-dev mailing list
> Laszlo-dev at openlaszlo.org
Laszlo-dev mailing list
Laszlo-dev at openlaszlo.org
More information about the Laszlo-dev