At my work, we use Weblogic Server to host an enterprise portal. Which is fine.
However, I\'ve recently had the opportunity to use Tomcat for some side projects, and I a
You will not be able to turn the frog into a princess. I would wonder slightly about those startup times for weblogic - they seem a bit excessive, you're not running on linux by any chance ?
If you're running nested archives (wars within ears etc) and also directory-scanning technologies (hibernate, spring etc), you may try unpacking it all to the corresponding exploded structure before deploying; it has been known to help a bit.
Tomcat contains a very small subset of the features weblogic has. We develop on jetty but deploy on weblogic for acceptance/production environments and this works fairly well. You can do the same with tomcat.
Tomcat is a fairly strict container whilst weblogic is lenient, so you'll normally have only minor troubles deploying to weblogic, especially as long as you continuously do both.
You can also use a tool like javarebel to do really nifty hot-deployment and avoid all those restarts.
WebLogic can also be slow to start up on Linux if it's connecting to a database and you haven't set up DNS properly.
Depending on your setup, you might be able to edit /etc/resolv.conf and comment out the nameserver line. This can reduce WebLogic's startup time from 20 minutes to less than a minute.