If you are switching from JBoss to WebSphere or just porting an application to WebSphere, you might find this writeup interesting: http://www.theserverside.com/reviews/thread.tss?thread_id=25532
(I know - shameless self-advertising ;)
Interestingly enough, I found and read that writeup earlier this morning, when googling for information on this very subject. I
didn't really notice the name though, and realize that you were
also the author of that, until just now!
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?
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.
TTYL,
Phil
--
When the 1st Amendment no longer protects your voice.
And when the 4th Amendment no longer protects your privacy or your stuff.
Thank God we have the 2nd Amendment to tell our elected representatives that enough is enough.
It's time to put "... from my cold, dead hands" back where it belongs.
FREE AMERICA Vote Libertarian www.lp.org
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
