Short summary presentation about the new features in JPA 2.0.
Friday, February 5, 2010
Thursday, February 4, 2010
GlassFish vs. WebLogic - 10 visions for the future
The Sun/Oracle merger raised some questions about the future of different components. One of interest to me is the GlassFish Application Server. Beside the Oracle WebLogic it is the next Java EE Application Server in Oracle's portfolio.
Not really much concrete has been said about the future coexistence of both. But some postings, slides and webcasts are around. Time to summarize them and draw some conclustions. To be honest: Non of the thoughts here are confirmed by anybody. Especially not by Oracle! I don't know if the described things will happen and I don't have any detailed insights in both products timelines or roadmaps. Happy to discuss everything and read about your thoughts.
1) "GlassFish continues as the Java EE reference implementation and as an open source project"
This is a statement, that is totally clear. Nothing will change. It will continue as an Open Source project and you will have a new RI for any of the comming Java EE versions.
2) GlassFish software licensing
Most of the components of the GlassFish plattform are available under a Dual License consisting of the Common Development and Distribution License (CDDL) v1.0 and GNU Public License (GPL) v2. Details for GFv2 kann be found on the GF Wiki. This will stay the same for most of the modules. Except for those, making the way into WebLogic Server. I expect this to be at least the following three: Metro, Jersey, Grizzly
3) Equinox will NOT be the OSGI platform for the Weblogic DM Server
As presented on last years OOW (WebLogic Server Architecture, OSGi and Java Enterprise Edition, Adam Leftik and Jeff Trent), the Equinix Platform has some drawbacks (Lacks a Generic Application Framework, Application Isolation, RFC-133 Context Class Loader). Therefore I expect the Weblogic DM server to use something else. I don't know if this will have any effect on GF. It is possible that the OSGI platform of GF will change, too.
4) There will be NO GlassFish v3 with clustering capabilities
The slide #15 of the Oracle + Sun: Application Server webcast states, that GF will be for productive and agile development. WLS is the availabillity and scalability solution. Therefore the v2 was the last GF with clustering facilities.
5) Metro, Jersey and Grizzly will make it to the WebLogic 11g
As mentioned by Thomas Kurian in the strategy webcast. These are great assets from the GF family and I believe that those three projects will make it to WLS.
6) There will be tool support for migrating GF Apps to WLS
The complete development to production staging process will be adressed by upcomming Oracle solutions. JDeveloper and/or OEPE will have plugins/support for automatic migration of GF apps to WLS. The WLS split deployment directory structure will also be enhanced with staging features. There will probably also be new maven plugins supporting dev and productive builds with GF and WLS.
7) Embedded GlassFish will be bundled with the OEPE
Beeing the development platform of the future, it is obvious that OEPE will bundle an embedded GF in the future.
8) JDeveloper will get support for GF
Beeing the development platform of Oracle could lead to having build in support for GF development in JDeveloper.
9) NetBeans will become the Java ME IDE
Having more and more GF support in JDeveloper and OEPE leads to a further specialization of NetBeans. It will become the Java ME IDE of the Future.
10) There will be a complete ADF implementation for GF
ADF will become available on GF, too.
Not really much concrete has been said about the future coexistence of both. But some postings, slides and webcasts are around. Time to summarize them and draw some conclustions. To be honest: Non of the thoughts here are confirmed by anybody. Especially not by Oracle! I don't know if the described things will happen and I don't have any detailed insights in both products timelines or roadmaps. Happy to discuss everything and read about your thoughts.
1) "GlassFish continues as the Java EE reference implementation and as an open source project"
This is a statement, that is totally clear. Nothing will change. It will continue as an Open Source project and you will have a new RI for any of the comming Java EE versions.
2) GlassFish software licensing
Most of the components of the GlassFish plattform are available under a Dual License consisting of the Common Development and Distribution License (CDDL) v1.0 and GNU Public License (GPL) v2. Details for GFv2 kann be found on the GF Wiki. This will stay the same for most of the modules. Except for those, making the way into WebLogic Server. I expect this to be at least the following three: Metro, Jersey, Grizzly
3) Equinox will NOT be the OSGI platform for the Weblogic DM Server
As presented on last years OOW (WebLogic Server Architecture, OSGi and Java Enterprise Edition, Adam Leftik and Jeff Trent), the Equinix Platform has some drawbacks (Lacks a Generic Application Framework, Application Isolation, RFC-133 Context Class Loader). Therefore I expect the Weblogic DM server to use something else. I don't know if this will have any effect on GF. It is possible that the OSGI platform of GF will change, too.
4) There will be NO GlassFish v3 with clustering capabilities
The slide #15 of the Oracle + Sun: Application Server webcast states, that GF will be for productive and agile development. WLS is the availabillity and scalability solution. Therefore the v2 was the last GF with clustering facilities.
5) Metro, Jersey and Grizzly will make it to the WebLogic 11g
As mentioned by Thomas Kurian in the strategy webcast. These are great assets from the GF family and I believe that those three projects will make it to WLS.
6) There will be tool support for migrating GF Apps to WLS
The complete development to production staging process will be adressed by upcomming Oracle solutions. JDeveloper and/or OEPE will have plugins/support for automatic migration of GF apps to WLS. The WLS split deployment directory structure will also be enhanced with staging features. There will probably also be new maven plugins supporting dev and productive builds with GF and WLS.
7) Embedded GlassFish will be bundled with the OEPE
Beeing the development platform of the future, it is obvious that OEPE will bundle an embedded GF in the future.
8) JDeveloper will get support for GF
Beeing the development platform of Oracle could lead to having build in support for GF development in JDeveloper.
9) NetBeans will become the Java ME IDE
Having more and more GF support in JDeveloper and OEPE leads to a further specialization of NetBeans. It will become the Java ME IDE of the Future.
10) There will be a complete ADF implementation for GF
ADF will become available on GF, too.
Monday, February 1, 2010
Need new boxes ;) Oracle, please help ;)
As you might have read: I was switching office rooms today. Somehow, I really do not like moving at all. But one good thing happened. I found some (very) old boxes and put them on my cabinet. Do you remember them? I absolutely need new ones :)
@Oracle: Can you help? :-D
@Oracle: Can you help? :-D
Saturday, January 30, 2010
260 posts and some reworks, personal comments
Weekend. Finally. Hard weeks at the moment. Lot to do and too less time.
The blog move did not went smooth enough at all. Lost my template. This is basically the cause for the actuall simple look and feel. I'll try to rework this as fast as possible but I need to switch to the newer blogger template features. This takes some time.
After the Oracle/Sun merger I was posting a lot about the strategy and the webcast. Some followers already suggested I should work for Oracle ;)
I am not. And I don't know, if I ever will. But I like their products (especially the Weblogic family) and I also like Java EE 6 (and therefore GlassFish as the RI).
You will read more about best practices and experiences, if everything comes back to normal. Forgive me, thanks for following, I'll be back in less than two weeks ;)
UPDATE (01.02.10)
Things are slowly getting back normal. Improving the design step by step when there is time for it. So many template and design changes ;)
The blog move did not went smooth enough at all. Lost my template. This is basically the cause for the actuall simple look and feel. I'll try to rework this as fast as possible but I need to switch to the newer blogger template features. This takes some time.
After the Oracle/Sun merger I was posting a lot about the strategy and the webcast. Some followers already suggested I should work for Oracle ;)
I am not. And I don't know, if I ever will. But I like their products (especially the Weblogic family) and I also like Java EE 6 (and therefore GlassFish as the RI).
You will read more about best practices and experiences, if everything comes back to normal. Forgive me, thanks for following, I'll be back in less than two weeks ;)
UPDATE (01.02.10)
Things are slowly getting back normal. Improving the design step by step when there is time for it. So many template and design changes ;)
Subscribe to:
Posts
(
Atom
)
