Go to JSR:
On this page:
 
Print Format
JSRs: Java Specification Requests
JSR 67: JavaTM APIs for XML Messaging 1.0

JAXM provides an API for packaging and transporting business transactions using on-the-wire protocols being defined by ebXML.org, Oasis, W3C and IETF.

  Status: Final              
  Stage       Start   Finish  
  Maintenance Release 3   Download page   12 Apr, 2006      
  Maintenance Draft Review 4   Download page   14 Dec, 2005   16 Jan, 2006  
  Maintenance Draft Review 3   Download page   15 Sep, 2005   17 Oct, 2005  
  Maintenance Release 2   Download page   21 Oct, 2003      
  Maintenance Draft Review 2   Download page   17 Mar, 2003   21 Apr, 2003  
  Maintenance Release   Download page   16 Apr, 2002      
  Maintenance Draft Review   Download page   12 Mar, 2002   15 Apr, 2002  
  Final Release   Download page   20 Dec, 2001      
  Final Approval Ballot   View results   30 Oct, 2001   12 Nov, 2001  
  Proposed Final Draft   Download page   25 Sep, 2001      
  Public Review   Download page   28 Jun, 2001   28 Jul, 2001  
  Community Draft Ballot   View results   12 Jun, 2001   18 Jun, 2001  
  Community Review   Login page   04 May, 2001   18 Jun, 2001  
  CAFE       02 Jun, 2000   23 Jun, 2000  
  JSR Approval       27 May, 2000   02 Jun, 2000  
   
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0
Please direct comments on this JSR to: jsr-67-comments@jcp.org
  
 
Specification Lead
V B Kumar Jayanti   Sun Microsystems, Inc. 
 
Expert Group
BEA Systems   Bluestone Software   Cisco Systems
Commerce One   Electronic Data Systems (EDS)   Hewlett-Packard
IBM   IONA Technologies PLC   Macromedia, Inc.
Oracle   Progress Software   SAP AG
Software AG   Sonic Software   Sun Microsystems, Inc.
Sybase   WebMethods Corporation
 

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Participant: Sun Microsystems, Inc.

Contact Persons:

  • Nicholas Kassem

    E-mail address: Nickk@eng.sun.com
    Telephone number: +1 408 863 3535


  • Mark Hapner

    E-mail address: Mark.Hapner@eng.sun.com
    Telephone number: +1 408 343 1609

List of other Participants who endorse this JSR:

  • Fujitsu Limited
    Contact: Kazuto Fujioka


  • Vitria Technology, Inc.
    Contact: Prasad Yendluri


  • Netscape Communications Corporation
    Contact: Larry Cable


  • Allaire Corporation
    Contact: Simeon Simeonov


Section 2: Request

2.1 Please describe the proposed Specification:

This JSR requests the creation of the Java API's for XML Messaging 1.0 specification (JAXM). This specification will describe Java API's designed specifically for the exchange of XML business documents such as, invoices, purchase orders, and order confirmations. This JSR will refer to such documents generically as business messages or messages for short.

The business messaging community is working to converge on a set of standard message headers and industry-specific message payloads. It is planned that this JSR will leverage work currently under way in the ebXML Transport Working Group, Oasis, W3C, IETF and potentially other relevant and open standards bodies.

This JSR does not aim to define either XML messaging standards or XML schemas for particular tasks. These networking and formatting standards belong in networking standards bodies such as Oasis or IETF. Instead this JSR aims to define standard Java APIs to allow convenient access from Java to emerging XML messaging standards, such as the emerging ebXML Transport/Packaging & Routing standard.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

The JAXM 1.0 specification will be provided, at least initially, as a standard extension but will be incorporated into the Java 2 Enterprise Edition platform as soon as this is practical and there is sufficient demand to warrant such integration.

2.3 What need of the Java community will be addressed by the proposed specification?

JAXM 1.0 will specify API's enabling the Java Community to develop portable applications that support emerging industry messaging standards:

  • Support for industry standard message envelope and headers for routing of message content,
  • Support for the reliable delivery of messages,
  • Support for message exchange templates (message choreographies),
  • Support for a variety of data types in message payloads,
  • Support for the non-repudiation of messages - privacy and integrity of communications between parties - authentication of senders of messages - Access control to business "services",
  • Support for secure audit trails.

2.4 Why isn't this need met by existing specifications?

Given the diversity of communication requirements and technologies amongst multiple trading partners, there is currently no standard way to accomplish the secure, reliable exchange of business documents. However, industry standards are emerging.

More specifically, there is currently no standard Java API facilitating the exchange of XML messages over the Web. The ability to describe a "software contract" in XML such that Java applications can exchange data (either synchronously or asynchronously) with other business applications will facilitate Web based business-to-business communication.

Although, this specification will focus exclusively on business applications written in the Java Programming language and messages described using XML (as specified by open industry standards e.g. ebXML), such applications will be capable of interoperating with all applications conforming to a common message exchange Schema.

2.5 Please give a short description of the underlying technology or technologies:

The JAXM 1.0 specification will most likely specify a low-level abstract Java interface specifically targeting the transmission and reception of XML messages. The specifications will be developed by industry experts to ensure that message delivery can be accomplished by supporting a number of communications infrastructures and key networking transports including, but not limited to, HTTP(S) and SMTP.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

javax.jaxm

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No.

2.8 Are there any security issues that cannot be addressed by the current security model?

The goal is to leverage the security services of the JavaTM 2 platform, Standard Edition and Java 2 platform, Enterprise Edition where possible.

2.9 Are there any internationalization or localization issues?

The goal is to leverage the I18N services of the Java 2 platform, Standard Edition. There are no localization implications at this time.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

None.



Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

3.2 Explanation of how these items might be used as a starting point for the work.

These documents are being developed independently and are therefore at different stages of completion and can serve as a starting point for the work of the Expert Group.
 
Sun Microsystems
What's New
JSRs
JCP Procedures
Community Resources
Participation
Press & Success
What is the JCP