WebLogic 12c (=Java EE 6 Full Profile Edition) And A Server Smoke Test
Oracle WebLogic 12c is a, certified, full profile Java EE 6 server:
- Download size of wls1211_dev.zip is 172 MB
- Installation requires you to unzip the archive, run some scripts and set the following JVM options:
-Xmx1024m -XX:MaxPermSize=256m(without setting the PermSize, the deployment didn't work)
- Disc size (server): 383 MB after installation
- Disc size (domain): 26 MB after installation
- Startup: execution of
[DOMAIN-FOLDER]/startWebLogic.shis fast (< 7 secs)
- Deployment: copy the ServerSmokeTest.war into [DOMAIN-FOLDER]/standalone/autodeploy/. The application becomes available under: http://localhost:7001/ServerSmokeTest
- Full deployment of ServerSmokeTest took < 5 secs.
- Tested were: Stereotypes (encapsulating @Named and @RequestScoped), @RequestScoped, @Named CDI-Beans, Injection of EJB 3.1 (no interface view), into CDI bean, @Singleton,@Stateless, CDI-events, POJO-injection, Interceptors
- ServerSmokeTest works without any modification on Glassfish v3, JBoss 7.0.2, JBoss 6m5, SIwpas-1.0.0-CR4, resin-4.0.12
The application was deployable without any modifications.
- Installation is a bit more complicated, comparing it to GlassFish, JBoss, TomEE or Siwpas. All Java EE 6 servers so far can be installed just by unzipping the archive. WebLogic requires you to run some scripts after unzipping. However: the installation can be performed in a few minutes.
- The server is lean and fast. Startup and deployment performance is good.
- The admin console http://localhost:7001/console is fast, clean and usable. WebLogic comes with extensive monitoring capabilities.
These vendors have got to deliver spec impls faster than this. Two full years to give us WebLogic for Java EE 6? Even though Oracle already controls Java and GlassFish? Ridiculous. It took them over a year just to deliver a release (10.3.4) that didn't require you to jump through hoops to use JPA 2.0 properly. That all said, I'm glad I'll finally be able to put some of your EE 6 patterns into production!
Posted by Ari Meyer on December 16, 2011 at 11:44 AM CET #
BUT: all other vendors were really quick - only 50% of Oracle application servers (GlassFish was immediately available), was late to the party.
This is actually a very good sign for the popularity of Java EE...
thanks for reading my patterns!,
Posted by Adam Bien on December 17, 2011 at 05:05 PM CET #
You're right, Adam -- 50% isn't bad. The problem is when your company is stuck with the other 50%. ;-) It's even worse when, like you probably do, you have some clients on 5 and others on 6, and you have to keep flipping back and forth. It would be nice if all the vendors could agree to a reasonable deliverable date for a spec impl. Otherwise all you have is a nice spec (and maybe RI) that you can't deploy to. Pipe dream...
Posted by Ari Meyer on December 18, 2011 at 04:28 AM CET #
Why don't you do the same test with WebSphere Application Server 8
Posted by Rohit Kelapure on December 21, 2011 at 08:19 AM CET #
I tried once, but the size of the WebSphere Application Server (just the installer) 8 Installer was greater, than the size of GlassFish or JBoss full profile download.
I suspect WebSphere Application server comes with its own operating system :-),
I will re-evaluate it soon,
Posted by Adam Bien on January 04, 2012 at 05:55 PM CET #
How did you managed to deploy CDI applications on WLS12c without experiencing problems like:
Normal scoped managed bean implementation class has a public field:..."
Posted by Will on January 09, 2012 at 04:04 PM CET #
I have this problem in weblogic 12.1.1 too!!
Do you know how to handle this error?
I don't have any public field in my bean but i get this error!
Posted by Mehdi Heidarzadeh on May 20, 2012 at 02:51 PM CEST #