Skip to main content

On the Bus

Posted by editor on October 18, 2005 at 7:14 AM PDT

Riding the Enterprise Service Bus

The Enterprise Service Bus (ESB) "has evolved out of necessity, and hence there are no issues of adoption and acceptance." That ought to satisfy critics of "ivory tower" type standards enterprise development, right?

Practically speaking, ESB offers a layer over existing standards, allowing disparate systems to communicate and coordinate. Author Binildas C. A. explains:

When it comes to integration, it is more easily said than done. This is because there exists no de-facto standard for integration end points. The scenario worsens when we try to do integration at the enterprise level or across enterprises. Each application will have its own way of exposing services. And we cannot revamp all of these applications in a day or two. Instead, the practical approach is to define a top-level integration infrastructure. The Enterprise Service Bus (ESB) is one such middleware infrastructure that provides, at the application platform level, pipes for information to flow and handshake with applications in silos.

In the Feature Article,

Service Provisioning Through ESB, he goes on to define ESB as a de-coupling of enterprise services from the transport systems used to communicate between them. This allows you to develop deeply distributed systems without getting hung up on the messaging details. The article goes on to show how to use a J2EE ESB implementation, Mule, to run an ESB-style application.

Planning the feature set of your next release? In
Also in
Java Today
, the Joel on Software entry Set Your Priorities starts by arguing that the wrong things to do are to add features just because they've been promised to a customer and to add what seems inevitable. His alternative approach offers a novel way to get consensus and to expose the cost/benefit trade-offs of new features: "Mike Conte taught me this system during the planning of Excel 5, where it only took a couple of hours even with a couple of dozen people in a conference room. The cool thing was that the roughly 50% of the features that we didn't have time to do were really stupid features, and Excel was better because it didn't have them."

Misconceptions and FUD? Senior Director and Chair of the Java Community Process (JCP), Onno Kluyt discusses widely-held beliefs about the JCP in the interview Ensuring Speed and Openness at the Java Community Process. He discusses the JCP's openness and the balancing of innovation and standarization, saying "Sometimes, experimentation is needed, in which case 'innovate, implement, standardize' may be a better way to come to consensus."

In Projects and
the Java Tools Community project JavaChecker is a static Java source code analyzer, which can spot coding errors like inappropriate exception handling (empty catch blocks and throwing of generic Exceptions), hiding and style defects, contract violations, synchronization defects, and more.

The Portlet Community notes the recent release of Stringbeans 3.0. This web services platform offers support for JSR-168 portlets and the Web Services for Remote Portlets (WSRP) standard. It also offers bridges to JSF and Struts, an interceptor framework for AOP-style development, and more.

Sayed Hashimi wants to know about Your build tool experience in today's Weblogs:
"I was wondering what is your experience with build tools. What build tool do you use at your orginization and what do you think of it? Specifically how do you use your build tool currently? What challenges have you faced, and how did you overcome it? What is your build tool lacking?"

Felipe Gaucho takes a look at OpenSource Management in Practice:
"Management models are a fever of this time - CMM, PMBOK, XP and several other magical formulas induce you to think about sophisticated levels of planning and scheduling as a pre-requisite of a successful project, isn't it? This blog entry just reports a personal experience using different approaches in OS project management and its results."

Persistence Stew II: JDJ Article (JDBC - The Indipensible Component of Persistence Mechanisms), Jonathan Bruce writes about his
"JDJ Article on the importance of picking the best-of-breed components no matter what ORM mechanism works for you."

tberthel adds some perspective to the many international salary reports in the Re: Application devlopers salary discussion in today's Forums. He writes:
"Many of the posts are using average income not the pay of an Application Developer. Also, many of them ignore exchange rates. In the real world dollars only have a value based on their location. So if you're in Brazil, Argentina, China, or India your dollar buys more. It's relative to your location. So India, China, Brazil, and Argentina App Devs are making a killing despite their USD amount."

kohsuke offers some help
Re: namespace definitions in XML output using JAXB2.0:
"The default printer of the JAXB RI prints out all 'known' namespaces upfront. This is because it generally improves the performance. One quick way around the problem would be for you to use a custom writer and filter out things that you think unnecessary. For example, you can marshal it to DOM, remove some unused namespace declarations, and write the DOM tree out. Or you can implement a SAX filter if you need more performance than DOM."

In today's
News Headlines

Registered users can submit news items for the href=""> News Page using our
news submission
. All submissions go through an editorial review before being
posted to the site. You can also subscribe to the href=""> News RSS

Current and upcoming Java

Registered users can submit event listings for the href=""> Events Page using our href=""> events submission form.
All submissions go through an editorial review before being posted to the

Archives and Subscriptions: This blog is delivered weekdays as
the Java
Today RSS feed
. Also, once this page is no longer featured as the
front page of it will be
archived along with other past issues in the href=""> Archive.

Riding the Enterprise Service Bus