Phil,
> We're not exactly "migrating" from JBoss to Websphere, actually. We're
> really migrating from Tomcat to WAS ( the early version of this
> application was servlets / jsp only, no EJB )... But I have been
> using a JBoss / Tomcat bundle for development and testing up until now,
> and we're at a point where we want to deploy an integrated build onto
> the WAS server and see how it goes (I'm scared after reading your
> writeup!). And of course the main reason for going with WAS has to
> do with our being an IBM Business Partner. Sound familiar?
I can only recommend using JBoss/Tomcat for development. It's such a pain to work with
WAS - even though I have to admit that I haven't really tried WSAD yet and supposedly
it makes things easier (if you're willing to lock yourself into using one particular
vendor's tool, that is). I am just too much in love with IDEA.
That said, our loadtests indicate that WAS on Linux is much more reliable than JBoss
with Sun JDK 1.4.x on Linux. So for production WAS might not be such a bad idea after
all.
> In at least this one regard (auto deployment), I do consider JBoss
> superior to Websphere. Deploying apps is (usually) very easy. However,
> JBoss annoys the mess out of me with their weird class-loader scheme.
> The first time I realized classes were being shared across applications,
> when I didn't expect them to, I almost passed out.
You have to pay attention to classloaders in WAS, too. They are highly configurable!
Feel free to drop me a private email and let me know how things went...
-hendrik
_______________________________________________
Juglist mailing list
[EMAIL PROTECTED]
http://trijug.org/mailman/listinfo/juglist_trijug.org
