this topic has been covered before in this forum and the IBM app servers forum. You could try doing a search on the two words for this forum and youi should find those posts. The guys in the IBM app servers forum will try and convince you that Websphere is better (they're wrong of course). I would rather direct you to a white paper on the subject, referred to in the following previous thread: http://www.javaranch.com/ubb/Forum40/HTML/000185.html Although I haven't worked with Websphere myself, people that I know who have worked with Websphere tell me that it's a pain to set up and manage. Hence I would recommend Weblogic (naturally). I hope that helps.
Hi! we port the same application writtten for tomcat on bea webLogic6 and websphere 3.5. For bea weblogic it was a peace of cake but for websphere it's a matter of hours (several). That's all i know! ------------------ Benjamin l�onard www.evisor.com
Hi, I've previously worked with Weblogic(EJBs and all), and now I am working with WebSphere. Haven't deployed EJBs on Websphere. But, as far as configuration issues are concerned, Weblogic is way ahead of WebSphere. WebSphere uses its excruciatingly slow GUI(yes, Java based) and our team has agreed that this tool itself was enough to bring down our cumulative productivity. There are other ways of configuring WebSphere, but they are not for the novices nor the usual developers. So, ease of administration, Weblogic gains full marks. We've faced a multitude of problems with JSP cacheing in websphere. It took us a while to figure out that unless we delete all the cache that websphere maintains, and restart the app.server instance(which in itself can take several minutes), this problem can not be solved. Right now, I don't know much about performance and other issues, but my vote goes to weblogic, beyond any hesitation. -Asuthosh.
What's gotten into you? Could it be this tiny ad?
how do I do my own kindle-like thing - without amazon