I had a bad experience with weblogic:
- I would provide bugs with cases to them and their support would take forever to understand the issue.
- Their compliance to the servlet and JSP spec is comparable to Microsoft's IE. (Just because it looks right and runs right - doesn't mean compliance)
- Converting to tomcat was an undertaking because the site originally coded by a consulting firm which knew buzzwords, but not coding.
- We had massive stability issues with the site. (It was as stable as a 4 year old running on the beach on a windy day carrying a giant beach ball) They recommended a firm and with a straight face - the firm recommended that they recode the entire site (offshore) for an incredible price tag. (And 4 months of frozen dev time)
After switching to tomcat + apache over 2 years ago, I can count on one hand the number of times we had unexpected outages due to tomcat's bugs. (Which were easily diagnosed and fixed(worked around) since we had the source)
The site was also significantly faster after the move.
In summary - I'm kind of jaded against weblogic.
-Tim
Bj�rn T Johansen wrote:
I am taking over a project that's running on Weblogic 8.1 SP3 today.. They are only using the jsp-container and it is time to renew the support agreement with BEA.
So I was just wondering, is it worth it? Or is Tomcat as good as WL or maybe better? Does WL have features that is missing in Tomcat? When the time comes to use EJB, is JBoss as good as/better than WL?
So basically, I would like some advice on why I should/shouldn't continue with Weblogic? :)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
