IBM's Lotus Software division may have been testing the market when it announced last month that it was yanking its Java Server Pages (JSP) engine, known as Garnet, from the upcoming finished version of Domino 6. Some users and analysts now think the company hasn't actually decided what, if any, Java development environment it will include in the final release, due later this year.
A Lotus official, who requested anonymity, told searchDomino "IBM hasn't decided what [Java support] is going to be put into Domino 6."
Beta versions of Domino 6, known as Rnext prior to Lotusphere, included native support for JSPs using Lotus' Garnet technology. At Lotusphere 2002 last month, Lotus announced that it would instead use an embedded version of parent IBM's WebSphere application server, saying Garnet would be non-standard and obsolete by the time the final version of Domino 6 is released.
Lotus currently offers a stripped-down version of WebSphere 3.5 Standard Edition included with Domino R5.
Notes and Domino developers, meanwhile, are still struggling with Lotus' summary decision to break its commitment to Garnet.
For years, developers have tried to integrate Domino with a number of Java servers and development environments. Now some suspect IBM pushing them into purchasing WebSphere by making it the only environment that will work with Domino.
"We had hoped that Domino 6 would support JSP and J2EE," said Matthew Henry, Web development team leader at Greenville, S.C.-based KEMET Corp., "so we wouldn't have to continue to run multiple apps."
Henry currently cobbles together his Domino applications with J2EE-compliant Servlets and JSP with Sun Microsystems' Java Development Kit (JDK) and Macromedia's JRun Server.
Developers want some assurance that Domino 6 will work with servers other than WebSphere, Henry said. "And we don't want WebSphere. We want to use Apache [open-source code] or Macromedia with Domino if we have to make a choice."
But IBM has yet to offer specific details on whether Domino 6 buyers will have to pay for WebSphere, in order to play with Java.
If Domino 6 ships with WebSphere components, at no additional charge, "then Lotus will have removed the most significant argument against WebSphere [the additional cost]," said John Vester, principal technical analyst at Indianpolis, Ind.-based Meritage Technologies.
"When Lotus people are asked whether developers will have to purchase WebSphere to create and run Java Servlets, they begin waving their hands around in the air, and talk about packaging issues," said Meta Group analyst Matthew Cain. "Frankly, I don't think they know the answer."
IBM's nixing of Garnet, Cain said, "may have been a trial balloon." He thinks IBM Lotus will make a packaging decision as it nears its ship date for Domino 6, which will be in the third or fourth quarter of 2002.
Lotus may also be saving users time and trouble in the long run by killing Garnet while it's young.
"If we had gone down the Domino-JSP road," Vester said, "we would have found in all likelihood that it's not standardized, doesn't run fast enough and has buggy limitations."
Notes and Domino developers, meanwhile, aren't waiting for IBM to make up its mind about Java development for Domino 6: some are building their own, open-source alternatives to WebSphere.
The Notes Open Source Software Organization (NotesOSS.org), also known as "Notes Sauce," has announced Project Crimson, which will integrate Domino 6 with Apache's Jakarta Tomcat application server. A member of the group has also published instructions for integrating JSP engines with Domino 6 servers.
But IBM and Lotus, with WebSphere, may still have the upper hand over Tomcat in mid-size and large companies.
"Tomcat is going to work fine, no doubt about it," Henry said. "But a lot of CIOs and IT people don't trust applications that you can get for free."
Mark Baard is a contributing writer based in Milton, Mass.
FOR MORE INFORMATION:
CLICK for searchDomino's Featured Topic on Domino and J2EE
CLICK for searchDomino's full coverage of Lotusphere 2002