Skip to main content

What is Consumer JRE, Java Kernel

The JRE 1.6 update 10 around the corner. Sun's Initiative to slim down a huge 14 MB JRE download is very much understandable to keep itself in competition. But for an average joe, How would this matter? There is some confusion in understanding what is this release about. Why is this in minor release update? What is expected? Why now?

Java Kernel, has been in talks for a while now. Why now - because with AIR, SilverLight taking on RIA market, Java cannot lag behind sticking to its thick client apis (AWT,SWT). But here is the thing, This release hass no change in API. Its just a new JRE implementation.

Okay What is it? The JRE consists of a bootstrap library and a bunch of system, language and util libraries. There may be inter dependencies in these libraries. Making the smallest possible JRE that can start on itself is the Java Kernel. After You get java kernel, Consider that a java program is asking for some dependencies, The Java Kernel *downloads* it and loads in the program for you. So its *gradually* getting the complete JRE over time. This way, A system that doesn't have JRE at all, can start loading an application/applet with a bare minimum start up time.

Does it effect you? Yes and No. Technically, you wont even bother about this change. as it is an implementation difference. but performance and deployment wise, it would give you more bang for the buck in User experience. Like say an applet can be made a web start program just like that. and to run a small web start program you need not have the customer load a huge VM.

What is Expected? If you are familiar with OSGi philosophy, you can compare this modularisation with that philosophy. Right now, Sun's move is only the first step. Moving forward, this modularisation will only benefit The experience. Having said that, One can attribute this move only to the lazy-ness of Sun, waiting on others to innovate and Sun playing only the catch up. However, its good for java community.

If you are keen on reading more technical details. Read here.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>