<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>Keith's Web Blog RSS Feed</title>
<language>en-us</language>
<link>http://www.keithwatanabe.net/index.php</link>
<description>Keith Watanabe's Website</description>
<item>
<title>No WebLogic Love From Me</title>
<link>http://www.keithwatanabe.net/blogs/2007/8/27/83e223d89f19c3308f4c1eca1067d093.html</link>
<description><![CDATA[I'm still curious why people in the enterprise love WebLogic.  Is it nostalgia?  Is it the love of spending tons of dollars for bragging rights? Is it the sleepless nights of the thing falling over because there never was enough memory?<br />
<br />
I just don't get it.<br />
<br />
Half the features in WebLogic probably will never be touched by most people.  I'm certain that EJBs are dying a prolongated death as people realize that it was typical Sun overpromising and underdelivering.  I have no idea why people would want to use a session facade, using session beans.  The books I've read warn people away from entity beans (and I wholeheartedly agree!).  And if you really need messaging, just find something that focuses exclusively on messaging!<br />
<br />
The funnier thing is that I know a lot of places that are considered &quot;entrprise class&quot; have legacy databases with tons of stored procedures running.  If you're desperate and require a Java layer, iBatis seems like a good substitute.  Otherwise, you'd spend a crapload of time attempting to create an entity bean using BMP.  <br />
<br />
I think ORMs are okay, but mostly overrated.  Highly tuned SQL seems more reliable and comforting for people than object-relational modeling.  If you're expecting a ton of incoming hits or transactions, maybe something like Hibernate might be worth investigating.    However, EJBs to me are just too painful to implement,  even with the 3.0 spec coming out.  Perhaps, it's a case of too little too late for EJBs.<br />
<br />
Anyway, today we finally made it to SIT and the WebLogic server basically got overloaded since the application apparently was too heavy and memory intensive.  We were barely hitting 4 people hitting the application simultaneously.  Very sad.  <br />
<br />
My laptop contains WebLogic as well.  The thing is pathetically fat and slow.  There should be a way to disable features (maybe I haven't seen it; then again I'm no WebLogic expert and don't have a manual readily available).  That said, for what we're doing Tomcat with clustering probably would've sufficed and then some (like save us a few hundred grand in licensing!)<br />
<br />
I'm actually quite happy that I had the opportunity to work with WebLogic.  I've worked with Tomcat, JRun, JBoss and now WebLogic and can safely say that I am pretty disappointed with this whole J2EE crud.  I think I'm going to stick with PHP and mod_perl and attempt to retain my sanity.]]></description>
<pubDate>Mon, 27 Aug 2007 07:12:04 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2007/8/27/83e223d89f19c3308f4c1eca1067d093.html</guid>
</item>
</channel>
</rss>
