Now it's easier than ever to access
Duke images. A logo library of 15
Duke images is now available for use in a variety of places such as web
sites, blogs and email signatures. Duke is for everyone--pass along the
word.

Hello Java EE, Java SE, and Java ME! Back in 2005, Sun Microsystems
announced a new Java naming convention, whereby future versions of the
platform would be called "Java EE 5", "Java SE 6", and "Java ME". A few
members of the Java community are using "JEE", "JSE", and "JME" as
shorthand. We'd like to encourage you to spell out "Java" - i.e. Java
EE, Java SE, and Java ME as "JEE", "JSE", and "JME" have different
meanings that are not associated with Java technology. For example, a
Google search on "JEE" returns topics unrelated to Java EE. Please take
a few minutes to understand the reasons for the new naming schema, which
are spelled out in this article (FAQs and a 1-pager are also available
here).
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Notewothy JSRs

Did you know that the PMO offers Public Relations support to spec
leads? The JCP conducts outreach to the press with JSR news on an ongoing bi-weekly basis. If would like to
highlight your JSR, please contact Corina Ulescu at corina@jcp.org.

JSR 304, Mobile Telephony API version 2, has been approved for
development. This JSR will extend the interfaces defined in JSR 253,
Mobile Telephony API, to cover additional use cases and features not
covered in that JSR.

JSR 303, Bean Validation, has been approved for development. This JSR
will define a meta-data model and API for JavaBean validation based on
annotations, with overrides and extended meta-data
through the use of XML validation descriptors.

JSR 302, Safety Critical Java Technology, has been approved for
development. This specification creates a J2ME capability, based on the
Real-Time Specification for Java (JSR-1), containing minimal features
necessary for safety critical systems capable of certification.

JSR 301, Portlet Bridge Specification for JavaServer Faces, has been
approved for development. The Portlet Bridge Specification for
JavaServer Faces will define the semantics of a JSR 168/JSR 286 portlet
that proxies for JSF artifacts.

JSR 298, Telematics API for Java ME, has been approved via
reconsideration ballot for development by the ME EC. This JSR seeks to
define the API set for Telematics services on embedded devices.

JSR 291, Dynamic Component Support for Java SE, has entered Early Draft
Review. The review is open until 1 September.

JSR 286 is now available for Early Draft Review. This first draft is
not feature complete, but provides
the most often requested features and the features needed for
implementing Web Services for Remote Portlets (WSRP) 2.0 services in
Java. The review is open until 1 September.

JSR 232, Mobile Operational Management, has published a Proposed Final
Draft of the specification.

JSR 223, Scripting for the Java Platform, has published a Proposed
Final Draft of the specification.

JSR 221, JDBC 4.0 API, has published a Proposed Final Draft of the
specification.

Expert Group (EG) Coordination: If you have an EG kick-off meeting and
would like to get an overview of the JSR 2.6 program please contact the
JSR Program Manager, Liz Kiener at: Liz@jcp.org or +1 510 550
4353. Liz is also available to facilitate face to face meetings for
your EG or help two or more EGs of related or dependent JSRs to meet.

spec-submit@jcp.org: to send in your draft and/or final specification
documents and related materials (as .pdf or Zip archive, please. Other
formats will not be posted).

admin@jcp.org: to submit Expert Group lists, in case you misplaced
your password, requests for your Member access information, updates to
your contact information.

pmo@jcp.org: to reach the PMO for general inquiries.

corina@jcp.org: to submit news items for Press & Analysts, and/or
explore further opportunities to talk to press and analysts about your
contribution to Java standards development through the JCP program.