Welcome!

From the founding editor of XML Journal

Ajit Sagar

Subscribe to Ajit Sagar: eMailAlertsEmail Alerts
Get Ajit Sagar via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: Java EE Journal

J2EE Journal: Article

'Tis the Season for Amalgamations

'Tis the Season for Amalgamations

By the time you get this issue, Christmas will be around the corner. From the J2EE arena, what is on your wish list for the coming year? More sophisticated tools? All-encompassing solutions for your business? More J2EE-related jobs next year? A utopia where J2EE and .NET can live together happily ever after? Better, cheaper, faster environments to build your solutions?

For me, one of the most significant developments this year has been the tighter relationships that open source products have developed with commercial J2EE or related technology vendors, and vice versa. At JDJ, we've been covering a lot of activity in the world of open source vis-à-vis Java. Given the state of today's economy, one of the trends you must have noticed is the strategy that commercial vendors have adopted - embrace open source, embed it in your offerings, and promote a unified, standardized Java environment. This gets the buy-in from the Java community. But more important, Java developers get a better-supported product suite to build enterprise applications.

There is a symbiosis between the different environments right now. As always, established vendors are magnifying their footprints by integrating with products and frameworks that are not a part of their core technology. However, there's a greater focus on adopting open source development to achieve this. This happens at several levels. Let's consider IDEs first.

Most of the leading IDEs, including Sun ONE Studio, WebSphere Studio, JBuilder, IDEA - almost every application server worth its salt - provides varying levels of support for the open source build tool (Ant) and testing framework (JUnit). Others provide support for tools that are not yet de facto standards, like Cactus. At the same time, the J2EE application servers have adopted these tools as de facto standards for configuration and deployment.

To take the acceptance of open source software one level higher, let's look at J2EE IDEs. WebSphere Studio is an example of an IDE that has not only adopted these standards, but is building the next version of their product on an open source framework - Eclipse. Struts is becoming a default standard for most IDEs. This doesn't mean your IDE can just integrate with Struts applications; it lets you build the presentation tier on Struts components that are natively supported from within the development environment.

Now let's look at J2EE and open source from the perspective of business solution and enterprise integration providers. Vendors in this area, as expected, are expanding into each other's space. In the past few years, this expansion was achieved by acquisitions and mergers. Naturally, vendors are a lot more conservative in today's economy. Besides the cost of acquiring a company, one of the concerns is the long-term viability of the company being acquired. Open source again emerges as cost effective and the more stable choice.

webMethods, a leading vendor in the enterprise integration space, recently made a very smart move by planning to integrate the JBoss J2EE application server directly within the webMethods integration platform. J2EE application server vendors have tried to grow into the enterprise integration space via J2EE Connector Architecture or direct integration via native connectors. This recent move by webMethods is an example of integration servers growing into the J2EE application server space.

In the near future, a business solution provider can look at an integrated platform that offers connectivity to legacy systems via Web services, as well as J2EE components that are natively hosted by a single vendor.

Earlier I mentioned symbiosis. On the other side of the coin, the J2EE open source community gains a lot too. The industry as a whole is always a little wary of something that is free. When open source is backed by popular commercial vendors, and much-needed marketing clout is put behind such initiatives, the community has a far greater chance of survival and future growth. The result is a shrink-wrapped offering that should make it onto all our Christmas lists. On that note, I hope all of you have a happy holiday!

More Stories By Ajit Sagar

Ajit Sagar is a principal architect with Infosys Technologies, Ltd., a global consulting and IT services company. Ajit has been working with Java since 1997, and has more than 15 years experience in the IT industry. During this tenure, he's been a programmer, lead architect, director of engineering, and product manager for companies from 15 to 25,000 people in size. Ajit has served as JDJ's J2EE editor, was the founding editor of XML Journal, and has been a frequent speaker at SYS-CON's Web Services Edge series of conferences, JavaOne, and international conference. He has published more than 125 articles.

Comments (4) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Brad Ayers 12/13/02 08:43:00 AM EST

Frank, if you like coding in Java but need it to run as fast as native code can, consider this java compiler which can compile Java programs into native code.

Steve 12/09/02 06:16:00 AM EST

If there wasn't something to the J2EE framework, do you think Microsoft would have traveled down the .NET road? After all, isn't .NET just java re-sculpted by Microsoft to be proprietarily run on their OS? It is the way of the future, so hold on to any thoughts of taking steps backwards into C++ land. I'm no big fan of Microsoft, but they are huge and I don't think they would bet so much of their stakes on a framework that wasn't going to be around for a while.

scot 12/08/02 07:05:00 PM EST

'java is slow, costs too much in hardware'?

here is your answer; hardware is cheap, programmers are expensive.

Frank LaRosa 12/08/02 02:31:00 AM EST

I wish for J2EE projects that aren't web sites. For some reason, this is the only type of project I ever get, and as a result, I'm widely know as that "web guy" instead of the versatile programmer that I actually am. It's become so annoying that I'm considering going back to C++ programming just so I don't have to keep doing the same project over and over again.

The company I work for considers Java inappropriate for anything other than Web sites. A common notion among the non-Java programmers where I work is that Java is too slow to do anything important, or worse, that it's a toy scripting language for Web sites. (Many don't even appreciate that J2EE is different from JavaScript). In this kind of environment, I have little chance of going very far.

I recently had a discussion about this with a C++ programmer. He said, "Java is slow". I said, "Computers are so much faster than they used to be, that it doesn't matter". He said, "For single-user applications that makes sense, but servers are designed to accomodate multiple users. No matter how fast the server is, it will be too slow if you throw enough users at it. If a C++ server is faster, it can accomodate more users, thus costing the company less in hardware". I have to admit, his point made sense. I still believe that much of what Java does is worth it in terms of increased programmer productivity (fewer bugs) but I don't see why we don't convert our finished server apps to native code before deploying them in large-scale production environments.