Breaks in Orion?

[bchan]

I just tested lps 2.2 core in Tomcat (works great). But I couldn't get it to work on Orion? Any ideas? I hit the hello example and nothing comes up. A lot of server side programmers love Orion, so I think supporting that app server will greatly help make Laszlo the standard for server side Flash.

I'm pretty proficient with Orion too. Any suggestions would be much appreciated. I'm looking into possibly bundling this with my j2ee open source portal called "Liferay" See www.liferay.com

[bloch]

I'm not familiar with the Orion directory layout.

1) Which JDK are you using?

2) Are there server logs for you to see? I'd look there for an exception stack trace or log message.

It could easily be a java classpath problem and/or container config issue... we've seen a bunch of these in the past (see the install notes for the "core" http://www.laszlosystems.com/developers/learn/documentation/installation/install-instructions-core.php
)

I believe

[bchan]

yes, I've read that html doc and I'm pretty sure it's a classpath issue.

To duplicate:

Download orion 2.0.2 from http://www.orionserver.com/

Unzip it somewhere.

Copy tools.jar from your jdk into orion 2.0.2 (I'm using jdk 1.4.2)

Type "java -jar orion.jar" now Orion is running.

Hit "http://localhost" with your brower. Voila. Up and running. hit any of the test jsps to see that your jdk is set up right.

Now hit control c to shut down orion.

/orion/default-web-app

is a default web app. delete everything in there.

Copy everything from lps 2.2 core into there.

start orion. It's up and running. Hit the hello, nothing shows up.

The same thing works for Tomcat. Thanks for the help. I'm really looking forward to integrating this into Liferay :)

[bloch]

Could you check the orion logs as well as java stderr/stdoutt and report back? I don't have the cycles to install orion.

-Eric

[bchan]

orion's global-application.log says:

com.laszlosystems.servlets.LZServlet: init
com.laszlosystems.servlets.LZServlet: Must be at least Version 2.3 Servlet Container!

But Orion is j2ee 1.3 compliant and is a 2.3 servlet container.

When I actually hit http://localhost/examples/hello.lzx

Nothing shows in the console.

Thanks bloch. (What's a cycle?)

[bloch]

Looks to me like the version of Orion you are using has a bug in ServletContext.getMajorVersion() or ServletContent.getMinorVersion()

or there is a bug in our code that checks
the version:

// Sanity check the servlet context version
if ((ctxt.getMajorVersion() < 2) ||
(ctxt.getMajorVersion() == 2 && ctxt.getMinorVersion() < 3)) {
respondWithInitError(req, res, "Must be at least " +
"Version 2.3 Servlet Container!");
return false;
}

-Eric



You can check with a simple jsp that prints

application.getMajorVersion()
application.getMinorVersion()


can you check the following jsp

[bchan]

You're right. It's a bug in Orion. Major and Minor return "2"

I don't know how that got passed the j2ee TCK.

One thing though, your web.xml does say for the 2_2.dtd. I changed it to 2_3 but Orion still returns 2.2 and not 2.3.

Any ideas on how to fix this? Short of me writing a wrapper servlet to pass in a servletcontextwrapper that will return 2.3 always?

[bloch]

You could be intrepid... grab the LPS source distro... and remove the sanity check and attempt to build it.

Or (less good) you could run LPS 2.1 which works against 2.2 containers.

I think writing the wrapper you suggested would probably be best for now though.

If you file a bug against the orion, folks I'd like to know about it.

-Eric

[bchan]

Hmm.. Orion's kinda slow with things like that. So I wouldn't bet on it. I'll probably just recompile that servlet class to not have that check.

[hqm]

Yow, Laszlo's first 3rd party open source developer!

[samflores]

I've found a way to execute lps-2.2 using Orion Applicarion Server 2.0.3 (i haven't tried in 2.0.2, but I belive it works too), but I think (read I'm sure :D) I'm breaking the IronFlare license. I've made a patch in the class that contains the bug to fix the problem.

[bchan]

Haaa.. well. You can submit that patch to Ironflare so they can fix it on their next release.