Ricahrd Monson-Haefel and James Strachan have submitted Java Specification Request (JSR) 241, The Groovy Programming Language, to the Java Community Process (JCP). According to the Groovy web site, "Groovy is a new agile dynamic language for the JVM combining lots of great features from languages like Python, Ruby and Smalltalk and making them available to the Java developers using a Java-like syntax." I haven't looked at Groovy in depth. What I have seen shows some good points and some bad points. What I can't figure out is what's gained by putting this langauge through the Java Community Process.
Open Cloud and Sun released the final version of JSR-22 Java Advanced Intelligent Networks (JAIN) Service Logic Execution Environment (SLEE) API Specification. "The specification includes complete descriptions of all the interfaces, classes, exceptions and requirements to develop portable telecommunication services and application framework so that services once developed will run on any JAIN SLEE compliant execution environment."
Shortly thereafter Open Cloud and Sun posted Java Specification Request 240, JAIN SLEE (JSLEE) v1.1. Sccording to the JSR:
Briefly JSLEE 1.0 specifies the event and programming model, application lifecycle and management for portable communications application. It additionally specifies the management and lifecycle of the JSLEE container itself. The JSLEE expert group deliberately avoided specifying the Resource Adaptor(RA) architecture as it was felt that this was a non-trivial piece of work and would delay the release of JSLEE 1.0.
The goal of the RA architecture is to allow Resource Adaptor implementations that use and fulfill contracts defined in the JSLEE 1.1 specification to be deployed and run in any compliant JSLEE.
Standardizing the RA architecture for JSLEE will ease the integration of JSLEE based applications into operator networks as a party other than the JSLEE vendor may provide the resource adaptor. For example call control in current mobile networks is delivered by many proprietary signaling protocols, and network specific variations of standardized signalling protocols. Network operators therefore expect significant integration work to be completed before a call control solution is deployed. If the interface between the JSLEE and RA is standardized the responsibility for the network integration could be the Network Operator, the Systems Integrator, the Network Equipment Providor or the JSLEE vendor.
Greg Hinkle has posted the fifth beta of MC4J 1.2, an open source (MPL) GUI interface for Java Management Extensions (JMX) based servers. Supported servers include JBoss, WebLogic, WebSphere, and Tomcat. MC4J is built on top of netbeans 3.6.