Sun plans to release a developer toolkit tailored to Sun's N1 architecture for IT infrastructure management.
Company officials have also defended the process for publicly submitting improvements to the Java programming language.
During a Software Developer Chalk Session at Sun's Californian offices, officials touted the Java Community Process and plans for an N1 toolkit. They also discussed improvements to informational Web sites for Sun developers.
The N1 toolkit is intended for use with Sun's N1 architecture, which is Sun's virtualising and provisioning technology intended to provide for unified management of data center resources.
"We're working on an N1 software developer kit, which would greatly extend an IT developer's ability to interact with components of the system," Sun's CTO for software, John Fowler, said.
The kit would, for example, enabled a customised control system to be implemented within N1, he said.
Sun wanted to encourage developer participation in N1, Fowler said.
"In general, it's to our best interest and our historical interest has always been to encourage developers as much as possible," he said.
No date has been set yet for release of the kit.
Sun officials defended the Java Community Process (JCP), through which proposed improvements to Java were submitted for consideration by JCP participants.
Director of WebSphere infrastructure software at IBM, Bob Sutor, has charged that Sun controls the JCP.
IBM is a member of the JCP.
"What we would hope is eventually we would get to a point where there's no single company that has main control over it," Sutor said during the IBM developerWorksLive conference in New Orleans last month, referring to Sun as company in control.
But Fowler last week said Sun's control was limited to the trademark of the word, Java.
"The reason we control the word (is) we want to be sure when we use the trademark, Java, it's compatible," he said.
Fowler also said Sun could not offer Java under an open-source format because this could result in a fracturing of the language, with multiple versions arising.
"It would be very difficult to maintain compatability," Fowler said.
Sun did not want to see 20 incompatible flavors of Java, as has happened with the Unix operating system, he said.
"We have not chosen to go do a direct open-source development model with (Java)," Fowler said. "However, we allow anyone to develop compliant implementations," Fowler said.
He also said IBM and Microsoft had put forth Web services specifications to the industry without seeking input from other vendors.
"IBM (and Microsoft have) participated in more than a dozen specifications in which nobody participates," Fowler said. "They don't go to anybody's standards committees."
IBM and Microsoft in April did submit the Business Process Execution Language (BPEL) specification to the Organisation for the Advancement of Structured Information Standards (OASIS), eight months after announcing the Web services proposal. Fowler said it was disappointing that BPEL was not submitted to W3C (World Wide Web Consortium).
BPEL and Sun's own Web Services Choreography Interfaces (WSCI) specification were intended to provide automation of back-end interaction of Web services, considered critical for e-business via Web services. WSCI has been submitted to W3C, but BPEL has much greater industry support.
Sun recently joined the BPEL Web services working group at OASIS, known as the WSBPEL technical committee.
In joining, Sun was looking for a compromise on the issue, Fowler said.
Asked if WSCI is effectively dead, Fowler said, "I don't think so. Sun and Oracle are working together [on WSCI]. We'll make sure there's something good there."
Sun also is improving its informational Web sites for developers, senior director of the Voice to the Developer program at Sun, Paul Pangaro, said.
Sun developer resources are found online at www.sun.com/developers. The company plans to allow developers to get a wide variety of content through a single portal, featuring content and community areas and subjects such as Web services, Panjaro said.
Content syndication, or sharing of content with other organisations, was also planned.