All about Java
Adobe Ajax Android Anwendung Apache API C++ Community Developer Eclipse Eclipse Foundation Embedded English Enterprise Entwickler Equinox Galileo Google Handy IBM IDE Individual Java Member Microsoft Mobile Modeling NetBeans News Open …
In case you have not seen this entry (like me) on the Lotus Notes and Domino Wiki, there is an article that explains how to add an iWidget to an XPage application.
I noted recently that http:eclipse-brazil-luiscm.blogspot.com
is nicking content wholesale and then reposting them. Planet Eclipse should not be including such spam content.
Link http://soa.sys-con.com/node/1250088
Ironically, probably the only post that was written by the author was the one that got it added into PlanetEclipse in the first place: http:eclipse-brazil-luiscm.blogspot.com/2010/01/i-thank-people-below.html
Lynn Gayowski, Wayne Beaton, Chris Aniszczyk,
Rüdiger Herrmann and Benjamin Muskalla.On the other note, I would like to welcome everyone at Eclipse Planet. It’s a pleasure to be here.
We don’t need this kind of plagiarism on PlanetEclipse. I’ve raised bug 301747 to track this.
Time flies, it is more than 3 years ago that Bjorn Freeman-Benson, BJ Hargrave, and me sat down after the 2006 conference to discuss the possibilities to organize an OSGi DevCon in conjunction with EclipseCon. Today I am proud to announce the 4th OSGi DevCon in Santa Clara, March 22-25. The program is, as usual, staggering. It always impresses me how many people are willing to contribute to EclipseCon/OSGi DevCon. Overall there were more than 350 submissions and about 60 of those were for OSGi DevCon. Picking the most interesting program was even harder than previous years because there is less space; we therefore have less time for OSGi DevCon. However, the resulting program is probably of even higher quality.
First I would like to draw your attention to the fact that we will officially publish the OSGi Enterprise Specification during EclipseCon. The OSGi Alliance will host a BOF on Monday night. One of the co-chairs of the OSGi Enterprise Expert Group, Tim Diekmann, will give a presentation during this BOF of what is in this specification and why it is ground breaking.
We have three tutorials. The first tutorial is from the people that wrote the OSGi and Equinox: Creating Highly Modular Java Systems book. You will get a feel for Toast telematics! See Working with OSGi: The stuff you need to know.
The next tutorial is from Kirk Knoernschild and Neil Bartlett, both very experienced developers and excellent writers and presenters. This tutorial was actually chosen in the EclipseCon Program Commitee top 5. The subject is a very hot topic at the moment: modularity. We all learned the lessons about coupling and cohesion. However, applying those lessons in large developments is still hard. This tutorial will give you theoretical as well as practical insight in modularity and using OSGi to achieve it. See Modular Architecture from Top to Bottom.
The last tutorial is from Karl Pauls and Marcel Offermans. They are the lead developers of the Apache ACE project and have been developing with OSGi forever. Their subject is absolutely core for OSGi although not always that visible. OSGi is not a “Hello World” technology, such examples only work well when the scope is small. The scope of OSGi is, however, large scale technology. Size does matter for OSGi. A consequence of the scale is that systems have a large number of bundles. This number becomes so large that handling these bundles requires automation because it is just too much to do by hand. Karl and Marcel will teach how to manage installations that reach these problems. See Become a Certified Bundle Manager today.
The first long talk is a must for anyone using OSGi. One of the most exciting pieces of work inside the OSGi is the nested framework RFC. Nested frameworks bring back the initial philosophy of OSGi: the bundles are your application. Enterprise servers based on OSGi starting to deploy many applications inside a single framework. In such a constellation, your peer bundles and peer services might no longer be yours. Nested frameworks returns to this model, an application will be installed in a child framework, also called composite bundles. The lead developers of Eclipse Equinox as well as Apache Felix will present the proposed architecture and discuss merits, pitfalls, and problems that still need to be solved. So do not miss Composite Bundles – Isolating Applications in a Collaborative OSGi World.
OSGi is like a sharp knife. When used well, it is extremely useful, when used wrongly it hurts. Chris Aniszczyk, Jeff McAffer, Martin Lippert, and Paul Vanderlei have been working with OSGi for the better part of the noughties and therefore have lots of experiences and the bruises and cuts to prove it. Between them they cover almost any computing aspect that can be used in conjunction with OSGi. Jeff was the driver behind Eclipse’s adoption of OSGi, Chris is the lead developer of PDE, Martin has worked on Aspect Oriented Programming in Eclipse including the weaving issues and is an aficionado of OSGi as well, and Paul brings the experience from the embedded world. A must for anybody that wants to adopt OSGi. See OSGi Best and Worst Practices.
OSGi is at the foundation of RCP, obviously. However, you can use RCP and not see much of OSGi. David Orme has been contracting for J.P. Morgan where they created an internal platform based on RCP. In the last few years they re-architected this platform to take more advantage of OSGi. This is a very good experience report for anybody that has to develop software to be used inside large organizations. See OneBench Reloaded – Pushing the (OSGI) Modularity Story in an Enterprise-wide Rich Client Stack.
Looking at the size of this blog, I do not think I should loose more readers going through each of the 25 mins talks, even though I think they’re more than worth it. I therefore list them here as bullets:
On Valentine’s day the early registration price will end and you’ll have to pay the full amount. So be sure to register as soon as possible to take advantage of this discount. If you’re an OSGi member, you can get an additional discount if you register here with the email address you use on the OSGi members web site.
I am looking forward to see you again in this 4th OSGi DevCon, lets hope it will be the best ever!
Book: IBM Lotus Notes and Domino 8.5.1, The Upgraders Guide.
I will start by saying this book is a good resource for anyone wanting to know what features are in Lotus Notes and Domino 8.5.1. The book pretty much covers most areas you would expect in Lotus Notes and is a great overall summary with many examples. I really love the format of the book, it was very easy to follow, very well written, and easy to read. I loved the appendix! The different chapters about add-on products was a great benefit. There were at times I felt like I read some things in one chapter and almost the same thing in another chapter with little value added. I really wish there was more around development techniques and best practices and in general I would have preferred a little more depth in some areas. For instance, there was a lot of material about Composite Applications but most of the information was based on 8.0.x stuff.
There is also a free chapter you can preview: Chapter 8 – which is an extracted Chapter that anyone can check out here, it covers a lot of information and should be quite useful for developers.
Ok, here is my constructive feedback. I will first say that the product documentation is something that needs to be addressed and I can see why many of these areas were not covered, but if you follow the yellowverse you will see the many blogs from IBMer’s, partners, and customers talking about these topics. Since this is an “upgraders guide” it was difficult for me to figure out how hard I should judge on some of the areas. The book clearly hits end user, admins, and developers so I took the liberty to just throw it all out there!
End user and Administrative areas:
Managed Settings – using Domino policies you can push down Eclipse plug-in preferences. They definitely should have mentioned this or walked through the policy screen like they did the Widget policies.
LiveText, Toolbox, and Widgets – arguably one of the most popular areas of the 8.x release and I see a small mention of it in this book. This probably deserves its own chapter considering the new options that were added in 8.5.1. Creating your own recognizers is also a popular topic in the forums.
Serviceability - it would have been nice if the book included a chapter on serviceability. For instance, what the directory structures are, where to find logs, how to look at and evaluate the output from the IBM support assistant. In my experience this stuff is very valuable to companies and admins supporting a rich client.
Developer areas: being a developer myself I would have wanted to get some detailed information about the following areas. It looks like the title of the book was changed from 8.5 to 8.5.1 because the developer chapter only talks about 8.5 and really the content is based on 8.0. So I would update this chapter in a revision to include some of the 8.5.1 enhancements.
XPages - even though this could be an entire book on its own, I think it warranted at least its own chapter. With the introduction to XPages on the client in 8.5.1 this should have been clearly highlighted! You will have to settle for the yellowverse, product documentation and the Designer Wiki.
Eclipse plug-in development – It would have been nice to have a chapter to primer the Eclipse/Java developers – or the want-to-be’s. plugins, Java UI, extensions. On Page 151, the screen shot not the CAE Palette in 8.5.1. It looks like a palette from 8.0 with all of the views in the system loaded into it.
Composite applications – None of the following was mentioned in the book: Container framework, Containers (Document and View, HOD, Symphony, Web), NSF Update Site.NTF, Side bar control. I recommend hitting the Composite Application Wiki, Lotus Expeditor Wiki, and Designer Wiki for these areas.
Lotus Symphony – even though Symphony could be its own book. It would have been nice to see integration with Composite Applications or how to extend Symphony with Eclipse and the JUNO API’s.
Lotus Expeditor – it would have been nice if they mentioned how Portal can manage composite applications for role based application support and also explain the value-add over base Eclipse.
Lastly, for many of the areas I mention about Composite Applications you can get it from the CA Wiki: What’s new in Lotus Notes 8.5.1 & Expeditor 6.2.1. The Domino Designer wiki is filled with XPage material – not too mention many of the business partner bloggers constantly write about XPages.
Also, this review and opinion is my own personal opinion and does not reflect the opinion of my employer or anyone else.
At the end of the week I will be leaving IBM / OTI. I have truly been honored to be part of the Eclipse Platform team and through this experience redefine the IDE, deliver RCP, shape up Java componentry and perform many other stunts. It has been 7 fantastic years.As hard as it is to leave, I’m very excited about the opportunity to join Sonatype [1] because they have an exciting portfolio of
This is a great article to start learning about Web 2.0 aggregation and interoperability between iWidget technology and Open Social gadgets.
Almost two years passed since the Memory Analyzer tool (MAT) was published at Eclipse. Since then we have collected a lot of feedback, questions and comments by people using it, and we also gathered experience in using the tool ourselves. Most of the people find their way to solve memory problems using MAT relatively easy, but I am convinced there are also a lot of unexplored features and concepts within the tool, which can be very handy if properly understood and used. Therefore I decided to start a series of blog posts dedicated to memory analysis (with MAT) – starting from the basics and covering the different topics in detail. I would try to answer there some of the questions which pop-up most often, give some (hopefully useful) hints, explain the benefit of certain “unpopular” queries, and (please, please, please…) collect your feedback.
As the Memory Analyzer is a tool working with heap dumps, I will start with a detailed look at heap dumps – what they are, which formats MAT can read, what can be found inside, how one can get them, etc… If you are interested in the topic, read further.
What Is a Heap Dump?
A heap dump is a snapshot of the memory of a Java process at a certain point of time. There are different formats for persisting this data, and depending on the format it may contain different pieces of information, but in general the snapshot contains information about the java objects and classes in the heap at the moment the snapshot was triggered. As it is just a snapshot at a given moment, a heap dump does not contain information such as when and where (in which method) an object was allocated.
What Are Heap Dumps Good for?
So what are heap dumps good for? Well, for a lot of things 
If there is a system which is crashing sporadically with an OutOfMemoryError, then analyzing an automatically written heap dump with MAT can be a very easy way to find the root cause of the problem (read more here).
If you wan to analyze what the footprint into memory of your application is, then MAT and heap dumps are again a good choice. This combination can also help you to find which are your biggest structures, to find redundant data structures, to find space wasted in unused collections, and much more. Such topics will be covered later in this blog series.
If you however are trying to find out why too many garbage objects are produced during a certain operation, or want to see which methods allocate most of the objects, then you would need to use a profiler which is collecting data over time from the VM. Leak detecting techniques relying on analysis of the objects behaviour (allocation / garbage collection) are difficult to inplement using heap dumps (see object identity below).
Types of Heap Dumps
Currently the Memory Analyzer is able to work with HPROF binary heap dumps (produced by Sun, HP, SAP, etc… JVMs), IBM system dumps (after preprocessing them), and IBM portable heap dumps (PHD) from a variaty of IBM platforms. Let’s have a closer look at each of the types.
HPROF Binary Heap Dumps
A detailed specification of the content of an HPROF file can be found here.
Below are summarized some of the important pieces of the information used within MAT:
IBM System Dumps
On IBM platforms one can preprocess a system dump (core file) from a Java process with the jxtract tool, and analyze the result with Memory Analyzer on an arbitrary other box (DTFJ libraries have to be additionally installed, see details below in the “How to get heap dump” section). As the core file contains the whole process memory, this kind of dump also provides all the details seen in an hprof heap dump (including the field names, primitive fields’ values, stacktraces, etc…). There is even more information (e.g. process related information), but at the moment it is not used in Memory Analyzer.
IBM Portable Heap Dumps (PHD)
The PHD files are much smaller in size than the corresponding system dumps. However, they contain less information.
The major difference between the HPROF dumps (or the IBM system dumps) and PHD dumps is that a PHD dump does not contain the values of the primitive fields. Only the non-null references from an object are provided. The second important difference is that the field names are not present, i.e. one can’t distinguish from which field a reference is made, and because of this the presented reference chains (paths) are not as concrete as with the other dumps. Using just the object graph is still enough for the analysis of many memory-related problems, but when the content of some fields is needed to get an idea why an object is too big then one has to use the system dumps.
Usually when a PHD dump is generated there is also a corresponding javacore file. If they are put together in the same directory when the PHD dump is opened with MAT, then some of the data in the javacore file will also be used.
So, having less information has both advantages and disadvantages – the PHD dumps are ways easier to transport from a customer (smaller size), can be used to find the biggest objects in the heap. And as they are usually written by default they are a good place to start the analysis. However, in some cases the information is enough to analyze in details the root cause of a problem.
A Common API for Them All?
Having different formats for the heap dumps is definitely easier for the VM providers, as they can provide very efficiently the specific data they have. This however doesn’t hold true for the tools, which are faced with the different formats, have to understand each of them, and possibly optimize for every format separately.
An attempt to solve this problem and make the life of tool writers easier is made under the Apache Kato project and the related JSR 326. They put efforts to provide a common API for accessing data from vendor specific snapshots and thus give tools a standard way to extract the data needed for post-mortem diagnostics (including memory related problems).
How To Get a Heap Dump
How to obtain a heap dump depends on the platform and the used JVM. In general all VMs provide the possibility to request a heap dump manually, or to get one written from the VM when an OutOfMemoryError occurs. The second option is very convenient for the analysis of problems happening on production systems, or happening only sporadically, as one does not have to observe the system and wait for the problem to reoccur.
A detailed description how a heap dump can be obtained depending on the JVM is provided here.
Object Identity
One of the questions which we are asked very often is if MAT can recognize the same objects in two or more heap dumps from the same process. The answer is unfortunately still no. Object IDs which are provided in the known to us heap dumps are just the addresses at which the objects are located. As objects are often moved and reordered by the JVM during a GC these addressed change. Therefore they cannot be used to compare the objects. Tagging the objects while they are allocated is something a profiler could do (usually at a relatively high cost), but in the standard heap dumps described above such information is missing. Some ideas how to guess identical objects were discussed in this bugzilla entry.
Are Dead Objects Present In the Heap Dump?
Another question which often pops up is if garbage objects are included in the heap dump. This again depends on the heap dump, but usually a GC is done before the heap dump is written. Nevertheless there are always some objects which are unreachable from the GC roots, i.e. should be thrown away. The Memory Analyzer removes such objects during the initial parsing of a heap dump in order to simplify the analysis. If you want to have a look at the “garbage” or even want the objects to remain, then find here what to do.
In Closing …
This was my attempt to give a detailed explanation of the different heap dump formats which the Memory Analyzer understands, and also give the answers to some of the questions which we frequently get. I’m sure there are still questions to be answered, and the MAT team will be very happy to get them from you, be it as comments here, in our fourm, or in bugzilla.
Der Sun-Chef bedankt sich in einem internen Memo bei der von ihm bislang geführten Firma sowie ihren Angestellten und setzt nahezu unbemerkt eine Spitze gegen den Oracle-Rivalen IBM.
Ottawa, Canada – January 21, 2010 – The technical program and gold sponsors for EclipseCon
2010 have been announced. Cisco, IBM, Oracle, Red Hat, SAP and Sonatype have agreed to be Gold sponsors for
the 7th annual Eclipse conference, to be held March 22-25, 2010 in Santa Clara, CA.
“Our sponsors provide the support necessary to make EclipseCon a continued success,” said Mike
Milinkovich, Executive Director of the Eclipse Foundation. “The conference provides a vital
opportunity for Eclipse users, developers and adopters to collaborate and advance the Eclipse
platform. We’re privileged to have the support of Cisco, IBM, Oracle, Red Hat, SAP and Sonatype to enable
us to put on each year a fantastic community event.”
The technical program will feature over 160 sessions and over 90 speakers. Session tracks include
EclipseRT, Modeling, OSGi DevCon, e4 and many more. In addition, the conference keynotes include:
The complete conference program is available at www.eclipsecon.org/2010/sessions.
Registration for EclipseCon 2010 is now open, with a 20% early discount being offered until February
14. To register, visit www.eclipsecon.org/2010/registration.
About the Eclipse Foundation
Eclipse is an open source community, whose projects are focused on building an open development
platform comprised of extensible frameworks, tools and runtimes for building, deploying and
managing software across the lifecycle. A large, vibrant ecosystem of major technology vendors,
innovative start-ups, universities and research institutions and individuals extend, complement
and support the Eclipse Platform.
The Eclipse Foundation is a not-for-profit, member supported corporation that hosts the Eclipse
projects. Full details of Eclipse and the Eclipse Foundation are available at www.eclipse.org.
All company/product names and service marks may be trademarks or registered trademarks of
their respective companies.
It’s sounds strange, but today we have few alternatives for the really good version control system (VCS).
What do I mean by good?
Reliable. If VCS isn’t reliable, it is worthless. If it looses your data (or does not allow you to access it), it is just a crap.
Fast. If you spent more time with your VCS as with programming, then you waste you time (and money).
Scalable. If it only works fast with less then 10000 files or requires a huge and expensive server to manage them, it will not scale with 1000000 files in the enterprise multi site world.
It can branch and merge. Most of professional developers are working in parallel on different branches of the same product. Being able to (automatically) propagate changes from one branch to another is the very important to save you time (and money), because otherwise you have to patch you bug in each and every branch again and again. Some VCS claim that they can branch and merge (like SVN), but merge != merge. It is not enough to copy files to a different folder and say “it’s a new branch now”. The true merge is if the VCS can track your changes across moved (renamed) files through different release streams. If it can NOT, you will fail to propagate your changes to a different branch immediately after the first refactoring.
Usable. If you have to spend days to read cryptic man pages instead of simply doing your work, then you waste you time (and money) again. Basically it means, it has to be integrated into your IDE of choice in the way that you do not need to read any man page at all.
Distributed. If you ever wanted to switch to the different branch in few seconds, or commit as often as you like (even while being offline), you must try a distributed (decentralized) VCS.
Open for third parties (or even open source). Being open is important, because in most cases you can get better/faster support for open systems. In case VCS is open source, you can try to fix it for your needs.
So which VCS I know personally? Perforce, Clearcase, CVS, Subversion, Mercurial and Git.
Clearcase is very often used in the enterprise world, because it is from IBM. Actually it is not, but anyway, it is expensive enough to buy it, so as IT manager in the big company it is your choice. Personally I hate Clearcase. It is neither fast nor reliable (I’ve seen 200 people waiting for a single defective server and being unable to simply read their own code), it does not really scale (until you upgrade to fiber glass network and buys some expensive IBM servers) and can not be really used in multi-site environment (it allows you to see the code committed in the other site after a DAY delay, because it need to run synchronization job between sites!), and it is of course closed source. BTW it is wrong to assume that because both Clearcase and Eclipse are from IBM, that Clearcase has outstanding Eclipse plugin. It doesn’t. The plugin is a joke wrapper to native Clearcase controls and windows, it is not really integrated into Eclipse. They do not have a simple list of checked out files (can you believe it !?!). The only one thing they do very good is branching and merging, I think this is the best implementation you can buy today. But except this – hey, it’s expensive and it is from IBM, so it must be good…
Perforce is a good candidate if you have some money left after the Clearcase deal, but it is neither distributed nor open (but they have good support). So if you do not need distributed VCS, and simply want a good, supported VCS, Perforce is your choice.
CVS and SVN are more or less the same. Some says “SVN is a better CVS”, but some says “if CVS was worse, then SVN is even worse” (enjoy the famous Linus video, it is highly recommended). I know SVN better then CVS, so I would say it is neither fast nor it can merge. In this mail thread you can read why it can not merge (short answer: by design). Of course both are not distributed, but at least open source and have perfect (CVS) or less then perfect (SVN) Eclipse support. So if you are alone developer or have one small project with a single branch, SVN is your choice. If you are seriously thinking about multiple branches or really huge projects, don’t touch SVN before it is too late. Perforce is your choice then, if you do not want to try Git or Mercurial.
Git and Mercurial are both the most promising, active, feature reach, open source VCS today. If your could not convince your IT manager to buy Perforce (because it is not from IBM), or your IT manager has not already decided to buy Clearcase (because it is from IBM) or you finally found that SVN synchronization and merge tree conflicts sucks, welcome in the world of happy Git/Mercurial users. I think that both Git and Mercurial are very similar and the difference is more or less matter of your taste. Both are extremely fast (they are as fast as your hard drive allows to read files). Try to switch to another branch on SVN – you know what I mean, it takes time. On Mercurial, it is matter of seconds, because all the data is on your local hard disk. Both have excellent branch and merge implementations (which is capable to track changes also for renamed files). Both are distributed (it means they support ANY workflow you like). Both have Eclipse plugins, and here we are finally there.
Mit einer ordentlichen Ergebnissteigerung nimmt Big Blue den von Intel vorgegebenen Trend auf und nährt damit die Hoffnungen der Analysten, die Branche könne die Krise überwunden haben.
About
Last year we had a successful Eclipse Demo Camp in Bangalore. In a post-event survey, many people said that they are willing to attend a full day event, and here we are.
Me and Ankur are planning for an Eclipse Day in Bangalore on April 9th. This year’s theme would be “Eclipse Plug-in Development”. It will be a full day event. Unlike the Demo Camp, there will be three types of talks (Long talk, Short talk and Lightning talk) and we have a committee (Ketan from ThoughtWorks, Anshu Jain from IBM & Madhu, an Independent Eclipse Consultant) to review the proposals. So you will get to attend only the best out of the proposals.
Want to attend?
Just like the Demo Camp, the entry is free. However you have to pre-register and the registrations open on Feb 1st. There are only 100 seats available, so you want to register as soon as its opens. Registrations can be done from here.
Interested in presenting?
Fill in this form and submit your proposals. The review team will get back to you.
Sponsoring:
Last but not least, sponsors. We are reaching out various companies for sponsorship. Your company can support the event by sponsoring it. It also had added advantage of:
* 5 reserved attendee seats
* One lightning talk
* Ads & stall space in the venue (banners and contact booth at sponsor’s cost. We will help provide as much space possible.)
* Mention in various promotions on Eclipse websites as mentioned here.
Do contact me or Ankur if you have any questions.
From Eclipse Tips
Like the tip? Subscribe via RSS or Email or Twitter
Auf der Lotusphere hat Canonical, das Unternehmen hinter Ubuntu, ein Supportprogramm für IBMs Office-Suite angekündigt.
I do not think we had application servers in mind when we had our first OSGi discussions in 1998. On the contrary, the OSGi service platform was the application; the idea of running multiple applications inside the same OSGi Service Platform did not cross our minds. Would somebody have explained the concept at that time, it would probably have been considered an anathema to us. Bundles were not meant to be applications, they were meant to be the constituents; the application was what appeared when you ran different bundles together in a service platform.
History played an interesting trick with this model. The class loading model of OSGi was more or less an afterthought, necessary to support the service oriented programming model. This detail caught the eye of many developers struggling with the class loaders in Java. However, instead of seeing a collaborative programming model, most saw class loaders on steroids. With release 4 we provided the zenith of all class loaders: allowing multiple versions to reside in the same framework. This was by many seen as the grail that solved the pesky problem of using multiple libraries that had conflicting version requirements. Though OSGi indeed could solve this problem better than anyone else it is illustrative that multiple versions was completely unnecessary for the original OSGi service oriented programming model. Actually, Richard Hall and BJ Hargrave had to explain the paradoxically sounding idea of exporting implementation classes many times to me.
With release 4, OSGi became salon fähig for the Application Server space. JONAS was the first but over time BEA WebLogic, IBM Websphere, JBoss followed. Even SAP and Oracle promised to follow this lead. The advantages of OSGi on this level are crystal clear but having the OSGi framework so close to the applications creates the temptation to allow applications to also use OSGi. Many applications are bursting out of their WAR format seams. The modularization provided by OSGi seems very attractive to remove the duplication that is embedded in the WAR architecture. It was Spring Source that made this module first available for enterprise developers with their Spring Source server. This lead is now followed by Oracle, IBM, and JBoss in a diverse set of open source projects.
The first automobiles in 1889 looked very much like the technology they replaced: horse carts. Over time the unique capabilities and requirements of an internal combustion engine resulted in the designs we see today. Is there an analogy with Application Servers and OSGi? Is OSGi just like an Application Server’s programming model or should it be treated differently?
Though the OSGi indeed has class loaders on steroids, these class loaders can only alleviate the dependency problems caused by today’s application models. I do not believe that the Application Server model where a number of WAR files are running in the same VM should be followed by an OSGi model where these WAR files are running in an OSGi framework only sharing their dependencies. Though it is good to manage a dependency (as OSGi does), it is best to not have a dependency in the first place. It is good to handle multiple versions of the same library but the problems caused by multiple versions quickly cascades to umanageable proportions.
I therefore believe that the original model promoted by OSGi, where the application emerges from the installed bundles, is still by far the best model we have. In this model bundles adapt to each other and collaborate with each other through services; exporting implementation classes is an anathema in this model. Any services in the service registry are available to all bundles because the framework is the application.
This model raises the question how to handle multiple independent applications. Do they all require their own framework? The answer is an unequivocal yes! The cost of this model with the current OSGi frameworks could be quite high. Fortunately, the OSGi CPEG is currently working on nested frameworks. Nested frameworks allow the creation of a composite bundle. This is a bundle that acts as a wormhole to another framework. Nested frameworks will have low overhead and can easily share services and packages among each other.
Nested frameworks will likely appear in a future OSGi specification. It will definitely take time to work out all the special cases but it looks very promising so far. Thomas Watson from IBM has been experimenting and the latest versions of Equinox already provide some of the behavior in experimental form. For me, this is the most exciting RFC in progress. The nested model will enable an application programming model very close to the original OSGi service oriented programming model we envisioned a decade ago. However, with this simple recursive rule of nested frameworks we do not limit it to small embedded devices but enable the same model for (very) large enterprise applications running in large application servers as well.
Today we formalized some changes in the Eclipse Series of books. Some time ago Lee Nackman left IBM and his various roles related to Eclipse. Many of you may not know Lee but he was instrumental in the early days of Eclipse and IBM’s ongoing contribution and commitment to Eclipse. Lee, Erich Gamma and John Weigand envisioned and created the Eclipse Series of more then 20 books that today conveys so much vital information to the Eclipse community.
I’m pleased to report that I am taking over Lee’s place on the Eclipse Series editorial board. One of my first tasks has been to help in the redesign of the series look. The result of that effort can be seen in the OSGi and Equinox book going to press this week.
The original series had a sequence of Eclipse photos. This was fitting and attractive. Unfortunately, many of the photos looked similar and as a result is was hard to distinguish one book from another. For the new look we have standardized on a new color scheme and layout. Different books will have distinct images largely at the discretion of the authors but the overall look will be consistent.
We have also introduced a subtle branding differentiation through the use of the Eclipse or EclipseRT logos (see the top left corner) depending on their focus (tooling vs. runtime).
In this new role I will be looking for new ways to drive the content that the community needs. Writing a book is a huge investment and while many teams have made very significant technical contributions, they are not big enough or well-funded enough to write books. There are a few ideas kicking around for how to lower the barrier and what topics are in most need of coverage. While we have great wealth of new projects at Eclipse, the book pipeline is surprisingly sparse.
As with everything at Eclipse, the community can help. Your suggestions for formats, topics and indeed, content are more than welcome. Feel free to contact me directly or post comments on this blog.
Für unserer Kunden suchen wir derzeit einen IBM Websphere/Java Entwickler. Bewerben Sie sich bis zum 11.02.2010. Projekt von projektwerk.
|
SYKORA-ML und agentes realisieren Technologiewechsel für IBM AS/400-Nutzer
fair-News.de (Pressemitteilung) Während SYKORA-ML ein Tool zur Java-Konvertierung beisteuert, bringt agentes sein Know-how in der Migration und Implementierung von IT-Systemen mit ein. … und weitere » |
Next Monday myself and Mike Cooper will be presenting AD202 – What’s New in Composite Applications in Lotus Notes 8.5.1. We will be showing a few technologies and demos but one application is pretty interesting because it has helped me add Lotusphere sessions to my calendar that I wish to attend.
The video shows me using that application and walks through it. It uses a single web container and an XPage component that runs locally in the Notes Client. We leverage the side bar for the XPage component placement, so it can be optionally shown. The web browser also has landmarks defined to publish the session information when the user lands on a session details page.
If you want to see how this application was assembled come to our session on Monday!
Ab diesem Frühjahr wird Alfresco eine Integration seines Content Management Systems in Lotus Quickr, Lotus Notes, Lotus Connections und das IBM WebSphere Portal anbieten. Die Lösung soll Kunden eine flexible Alternative zu Microsoft SharePoint bieten.
|
Webanwendungen mit IBM Rational und IBM WebSphere V6
PC-Welt Nach einer kurzen Einführung in Enterprise Java und J2EE-Architekturen werden zunächst umfassend und klar verständlich die verschiedenen Technologien des … und weitere » |
Hello World
Finally: Yet Another Eclipse Blog! I will try this time to not let this blog become yet another zombi blog. I’ve use to blog about the Java Development Tooling and Platform Text back in the days when I worked as an active eclipse committer at IBM and I actually enjoyed writing blogs. But writing good blogs is time consuming and with customers on your back and milestones ahead writing blogs is never a priority. But this time everything is going to be different, promised;-)
In this blog I’d like to write about the stuff we do with Eclipse here at Comerge, the company I work for. At the moment we use Eclipse as a tool to develop Java code (what else:-) . We create GWT frontends and use the JDT to code that stuff. We also use the Eclipse Rich Client platforms to build applications for our customers. We also maintain and develop Aranea and its Java port. We are using Open Architecture Ware there. Then we also develop and maintain Origo and its Mylyn Origo connector. And in the spare time which I unfortunately don’t have anymore I also work on another RCP: The Evolution Player.
I hope this will give me enough topics to blog about. Of course I’ll try to blog only about stuff which is of interest to most of you.
Benno
This is great news! As Lotus Notes, Sametime, Domino Designer, and Lotus Expeditor are all based on Eclipse, not too mention all of the Rational tools and many more products, it is great to see Eclipse being recognized like this. They don’t really mention the fact that many of the IBM installed client portfolio is based on Eclipse, and they seem to focus on tooling.
Link.
