| |
|
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 1 of 7  In this interview, Jesper Joergensen talks about BEA's involvement in open source, its approach to J2EE and the changing nature of the J2EE application servers.
He also shares his views on the Apache Beehive project and why he thinks the WebLogic Server has now reached a level of reliability and scalability that makes it capable of replacing even some of the old and reliable systems in existence today.
Jesper tells us what's special about the new Weblogic Server 9.0 and the new WebLogic Workshop that's being built on top of Eclipse. He also shares his thoughts on when it makes sense to adopt a commercial application server like Weblogic over its free and open source alternatives.
IndicThreads >> Hi Jesper! Thanks for being on IndicThreads. Could you introduce yourself to our readers?
Jesper Joergensen >> Hi, and thanks for inviting me. I work in product marketing for BEA systems. Product marketing is responsible for telling the world about BEA?s products and help facilitate two-way communication between BEA?s product groups and the people who use our products.
"I am responsible for BEA?s product marketing efforts
around SOA (service-oriented architecture)...
Personally, I am responsible for BEA?s product marketing efforts around SOA (service-oriented architecture). I?ve be doing this job for over two years at BEA. Before joining BEA, I was the CTO of a small ISV in Denmark that build a set of applications on WebLogic Server. In this previous job, I also coded J2EE applications myself, so I have tried a little bit of everything.
IndicThreads >> BEA has been a major J2EE player for many years now. How do you think has BEA's approach towards J2EE evolved?
Jesper Joergensen >> I think BEA has always stood for ?pragmatic J2EE?. We were the first to provide a reliable, high-performance application server that implemented the J2EE specs, and since then we have always seen J2EE through the perspective of the programmers and administrators that are using it.
"BEA has always stood for pragmatic J2EE... In the beginning, BEA was focused on delivering a J2EE server that was easy to use but provided the best scalability and reliability. As we achieved this goal, we shifted our focus to J2EE as a programming model itself. Years of experience showed that certain parts of J2EE were really difficult to learn and certain parts made it hard to manage the application lifecycle.
We have worked on this issue in different ways. We started the Apache Beehive project to provide a more easy-to-use programming model for J2EE that was more aligned with ?modern? needs, such as asynchronous programming and web services.
"We started the Apache Beehive project to provide
a more easy-to-use programming model for J2EE
that was more aligned with ?modern? needs...
But we have also worked on specifications to introduce things such as deployment plans (JSR 88) and we have implemented these improvements in our latest version (WebLogic Server 9.0).
We continue to see J2EE as an important standard in the enterprise software space. But BEA?s main focus is to provide enterprises with the infrastructure they need and to help create industry standards that gives our customers investment protection. Some of this work takes place outside the scope of J2EE.
"BEA?s main focus is to provide enterprises
with the infrastructure they need and to help create industry standards
that gives our customers investment protection...
<< Start < Previous 1 2 3 4 5 6 7 Next > End >>
|
|
|
|
Home | 
