A Twitter Bootstrap Based Self-Measuring Application To Quantify the Effect of Precompilation on WebLogic – Part I by Frank Munz
By JuergenKress on Aug 28, 2013
Sounds cool, doesn’t it? Yet a bit academic - I agree. So why this title? It is as precise as it gets. And it’s less 140 chars, so I can even tweet it. Yet no worries, I’ll enjoy dissecting the headline for. There are a number of important messages. To make it more readable I will split it into three parts.
- So let’s get to the topic right away (which by the way is precompilation).
- To prove it makes a real difference, I will show in part II how you can measure the effect of precompilation since quite often people fail to do so.
- Later in the cool part, part III, we look at some exciting bells and whistles for web applications (Twitter Bootstrap framework).
Why would you precompile your application?
Precompilation isn’t really necessary to make an application work correctly. WebLogic will compile necessary artifacts when they are needed. For example a JSP page which is not precompiled will be compiled at the time it is accessed.
Deploying an application without precompilation forces you to use lame excuses such as “It’s a bit slow right now, because it is running for the first time after deployment“. I am sure you don’t want to be remembered for lame comments. Running your applications without precompilation costs you time. And time is expensive.
What is the difference between precompilation and compilation?
Well, every Java class has to be compiled before it is executed by the JVM. The .java file is converted into a .class file. Other stuff, such as a JSP page could be deployed as is. It will then be compiled by WebLogic. Read the full article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.