Re: [Springframework-developer] Orion 2.0.2

[Rod J. <rod...@in...>]

>Orion 2.0.2's JSP engine is hopelessly broken. Have a look at the following
issue that I submitted back in July:
http://bugs.orionserver.com/issue/view.jsp?id=1081

>Therefore, let's simply forget about Orion - it's effectively an abandoned
product. We recently had to use Oracle's OC4J at werk3AT: It's far ahead in
terms of the JSP engine - everything works nicely. OC4J has its problems in
the EJB container, though, but that doesn't worry me at all.

It's a pity, I used to like Orion. I did most of the early work on the book
and what became Spring on Orion (1.5.2 I think).

There are also EJB problems in Orion. A few months ago I was doing a
prototype for work project involving remote SLSBs, and couldn't get Orion
2.0.1 to pass parameters of types other than int (I think) over RMI. I was
wondering whether or not there was some dreadful bug in the Spring AOP stuff
I was using on the client side until I switched to WLS 8.1.

Not only did everything work perfectly in WLS (although I did later run into
a more complicated problem with RMI that required upgrading to the latest
service pack), but I found that WLS 8.1 is a joy to develop on. Just drop
the Jar in the applications directory and you're done.

I now tend to use JBoss 3.2.2 and WebLogic 8.1 interchangeably for my own
projects, with deployment descriptors for both.

Regards,
Rod