| |
|
WebLogic 9.0 takes J2EE to a new level of reliability and scalability |
|
|
|
Written by Content Team
|
|
May 29, 2005 at 06:56 PM |
|
Page 3 of 7
IndicThreads >> BEA joined Eclipse a few months back. So what's happening on that front? When can we see the next version of Workshop and why should a developer adopt Workshop?
Jesper Joergensen >> The next version of WebLogic Workshop will be based on Eclipse and we expect to ship it at the end of 2005. WebLogic Workshop combined with Apache Beehive demonstrates how an ease-of-use programming model with a supporting IDE can drastically increase developer productivity and improve maintainability and overall cost of ownership for enterprise software projects.
"The next version of WebLogic Workshop
will be based on Eclipse and we expect to ship it at the end of 2005..."
This removes a major obstacle to developer adoption. Many people decided not to try out Workshop because it was a separate program with different user experience. Now, developers can work with this new programming model within Eclipse and accordingly every Eclipse developer can test Workshop and Beehive in a painless way.
IndicThreads >> BEA gave Beehive to the open source community quite some time back and I remember it had generated a lot of interest at that time. There's again some buzz about Beehive lately. So at what stage is Beehive today? When can we expect to see it ready for general use?
Jesper Joergensen >> Since we started the Beehive open source project we have come a long way. Beehive 1.0 is now available in beta and the final version will be available soon. WebLogic Server 9.0 which is expected to be released this summer will support Beehive 1.0 which means that you will be able to use Beehive based web services, controls and page flows on WLS.
"WebLogic Server 9.0 will support Beehive 1.0..."
IndicThreads >> The Beehive site states the project goal as "To make J2EE programming easier by building a simple object model on J2EE and Struts". Nice and simple. However as you know, J2EE has no dearth of application frameworks and so every time a new framework is released, the most common reaction is "Another One?". What's special about Beehive? Can you give us a comparison with the popular frameworks of today?
Jesper Joergensen >> It is true that there is a lot of activity around various programming ?frameworks?. In the community. Beehive represents BEA?s response to a problem that has also caused many other responses. Therefore we now have a proliferation of ideas for how we can make J2EE simpler which of course is a good thing.
Most of the initiatives have not only received little attention from customers and developers in the community. But there is one project that our customers have shown particular interest in and that is Spring. Beehive and Spring have a number of similarities and differences. They both address the problem of instantiation of components and the wiring together of component instances that reference each other. The major difference is that Beehive stores the wiring metadata and other metadata as JDK 5 annotations in the code while Spring uses XML configuration. Beehive also has special focus on web services with its JSR 181 subproject.
"Beehive stores the wiring metadata and other metadata as JDK 5 annotations in the code..."
"Beehive also has special focus on web services with its JSR 181 subproject..."
BEA is working together with the community and with our customers to find out how Beehive and Spring should be interoperable and whether in some distant future they can be closer related. Meanwhile, we are committed to supporting both programming models as well as any other J2EE programming model that our customers find valuable. We want as many developers as possible to be able to use WebLogic as their app server regardless of the programming model they choose.
|
|
|
|
Home | 
