Paul Krill
Editor at Large

BEA readying Java Web services technology

news
Nov 26, 20032 mins

Reference implementation of specification due in early 2004

BEA Systems early in 2004 plans to have a reference implementation of Java technology intended to simplify deployment of Web services, based on the company’s own WebLogic Workshop IDE.

Java Specification Request (JSR) 181 enables cross-container deployment of Java Web Services consistent with the Workshop framework, the company said. BEA defines Java Web Services as a Web services file extension used in Workshop.

The proposal, entitled “Web Services Metadata for the Java Platform,” was launched by BEA in 2002 and submitted to the Java Community Process (JCP) for standardizing new Java technologies. JSR 181 defines an annotated Java syntax for programming Web services.

The reference implementation will be publicly downloadable for use as a blueprint in developing like frameworks to Workshop for Web services deployment, according to BEA.

Through JSR 181, a Java Web services file created in Workshop could more easily run on other vendors’ J2EE-compliant application servers, said Dave Cotter, BEA director of developer product marketing. Web services files developed in Workshop can be deployed on other application servers besides BEA’s now, but developers lose productivity gains available in Workshop, according to Cotter.

JSR 181 “is the specification with associated reference implementation of how somebody could create a framework that could interpret these Java Web Services files that have annotations in them,” Cotter said.

An analyst was not impressed with JSR 181.

“All in all, [JSR is] not really all that significant,” said Jason Bloomberg, senior analyst at ZapThink, in an e-mail response to questions.

“The main point to JSR 181 is to provide for greater simplicity for developers of Web services on a Java platform,” Bloomberg said. “The key to understanding this JSR is that it consists of metadata for describing Web services and is proposed as an instance of the JSR 175 metadata facility for Java. In other words, the Java source code can be commented [on] in a programmatic, rigorous way, providing a consistent way of explaining the Java code to developers.”

But Cotter said the company has received positive responses.

“The feedback that we’ve gotten from the industry and customers is that 181 is significant in how it makes Java or Java programming much more approachable,” he said.

According to the JCP Web site, JSR 181 has the support of BEA, Borland, Sun Microsystems, and Iona Technologies.

Paul Krill

Paul Krill is editor at large at InfoWorld. Paul has been covering computer technology as a news and feature reporter for more than 35 years, including 30 years at InfoWorld. He has specialized in coverage of software development tools and technologies since the 1990s, and he continues to lead InfoWorld’s news coverage of software development platforms including Java and .NET and programming languages including JavaScript, TypeScript, PHP, Python, Ruby, Rust, and Go. Long trusted as a reporter who prioritizes accuracy, integrity, and the best interests of readers, Paul is sought out by technology companies and industry organizations who want to reach InfoWorld’s audience of software developers and other information technology professionals. Paul has won a “Best Technology News Coverage” award from IDG.

More from this author