Lotus' Shift On Java Support Raises Eyebrows

The ongoing issue centers on Lotus' decision to remove Java Server Page (JSP)/servlet support that shipped with a beta version of Domino 6 in the third quarter. Lotus said at Lotusphere here last week that it plans to fill that gap with technology from WebSphere, IBM's application server.

Partners are concerned with Lotus' move because IBM is struggling to position Domino and WebSphere, both of which have application-serving capabilities.

>> 'It has never been our intent to step backward, but instead leverage WebSphere in some sort of bundle.' -- Carl Kraenzel, Lotus

"The conspiracy theory is they did this because, once again, Domino was getting too close to the WebSphere franchise," said one developer attending Lotusphere.

Lotus executives describe the move as pragmatic. J2EE services will be delivered through WebSphere, which is "really turning out to be a significant integration platform for tying together all the things that enterprises are trying to do," Lotus General Manager Al Zollar said. "The model calls for JSPs/servlet engines, and rather than embedding those capabilities into Domino 6, we'll be linking into those services as they're delivered through WebSphere."

id
unit-1659132512259
type
Sponsored post

That notion irks partners who think IBM is trying to sell both servers.

But Lotus executives counter that claim.

"It has never been our intent to step backward, but instead leverage WebSphere in some sort of bundle," said Carl Kraenzel, technical strategist, Lotus Worldwide Development.

Lotus opted to drop the Domino J2EE support, code-named Garnet, because it was not standard, Kraenzel said.

"It would have been a proprietary flavor of J2EE . . . and rather than invest in a blind alley that was downright counter to our strategy, we concluded it would be best to take that stuff out."

Lotus does not plan to charge extra for the J2EE functionality, Kraenzel said.