Sure, I've had to use JRun for a client and here's my experience with it:
JRun does not support hot deployments. Any deployment requires a server
restart.
JRun does not automatically pick up .war file changes. Really, I found war
file support to be minimal, compared to Orion. There's very little that
'drops in', everything has to be through the management console (in my
experience, they might provide for dynamic changes to configs, but it's
subtle and not something I could access!)
Orion performs much better
JRun does not support servlet 2.3 API (nor will they in their 3.1 release,
which is in beta right now).
There are small differences in JSP parsing:
Orion allows myTags:stuff
param1=%=request.getParameter("foo")%blahblah/myTags:stuff, JRun does
not (it barfs on the inner quotation mark)
JSP error reporting is much better in JRun.
The management console for JRun seems slick initially, but rapidly becomes
a pain in the ass if you're the kind of person who doesn't worship the
web, and believes that changing text config files is faster and better.
On Mon, 19 Mar 2001, waheed_rahuman wrote:
Can anyone using orion can campare the JRun webserver regarding
servlets,JSP and EJB with postgresql.
regards
waheed
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
