World Library  
Flag as Inappropriate
Email this Article

Java Api For Xml Messaging

Article Id: WHEBN0006189782
Reproduction Date:

Title: Java Api For Xml Messaging  
Author: World Heritage Encyclopedia
Language: English
Subject: JSR 250, Bean Validation, J2EE Management, Unified Expression Language, Java API for RESTful Web Services
Collection:
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Java Api For Xml Messaging

The Java API for XML Messaging (JAXM) enables distributed software applications to communicate using XML (and SOAP). JAXM supports both asynchronous and synchronous messaging. JAXM is a replacement for SOAP with Attachments API for Java

JAXM is one of the Java XML programming APIs

Overview

The Java API for XML Messaging (JAXM) enables developers to use XML messaging using the Java platform. Developers can create and send XML messages over the internet using the JAXM API.[1]

The following figure presents a conceptual relationship between JAXM and other architectural elements required in web-based, business-to-business messaging.

Also, Java API for XML Messaging has several advantages over Remote Procedure Call such as the following:

  • One-way (asynchronous) messaging
  • Routing of a message to more than one party
  • Reliable messaging with features such as guaranteed delivery

The complete JAXM API comes with two packages:[2]

  • javax.xml.soap: This package contains the API for creating and populating a SOAP message.
  • javax.xml.messaging: This package allows one to send one-way messages via a messaging provider.

Messages

Messages in JAXM are XML messages that follow the prescribed SOAP format and standards. There are two main types of SOAP messages: those that have attachments and those that do not. For example, if you want your message to contain an image, you must send an attachment with the message. The SAAJ API provides the AttachmentPart class for attachments in SOAP messages.[3]

Connections

A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.[4] The JAXM API provides the class and interface to represent two kinds of connections:

  • javax.xml.soap.SOAPConnection—a connection from the sender directly to the receiver (a point-to-point connection)
  • javax.xml.messaging.ProviderConnection—a connection to a messaging provider

SOAP Connection

A SOAPConnection is a point-to-point connection for sending messages directly to a remote party.[5] A SOAPConnection object, which represents a point-to-point connection, is simple to create and use. You do not have to do any configuration to use a SOAPConnection object because it does not need to run in a servlet container (like Tomcat) or in a J2EE server. It is the only way for a client to have a connection without a service provider.[6]

Provider Connection

A ProviderConnection object represents a connection to a messaging provider. (The next section explains more about messaging providers.) When you send a message via a ProviderConnection object, the message goes to the messaging provider. The messaging provider forwards the message, following the message's routing instructions, until the message gets to the ultimate recipient's messaging provider, which in turn forwards the message to the ultimate recipient.[7]

Messaging Providers

A messaging provider keeps track of messages and routes them to the correct destination or destinations. It is a service that handles the transmission and routing of messages.[8]

When to use a Messaging Provider

A JAXM client may or may not use a messaging provider. Generally, you do not need a messaging provider if you just want to be a consumer of Web services. Some limitations of not using a messaging provider are the following:

The client can send only request-response messages The client can act in the client role only

Some advantages to not using a messaging provider are the following:

  • The application can be written using the J2SE platform
  • The application is not required to be deployed in a servlet container or a J2EE container
  • No configuration is required[9]

References

  1. ^ http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html
  2. ^ http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html
  3. ^ http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936
  4. ^ http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936
  5. ^ http://docs.oracle.com/javaee/5/api/javax/xml/soap/SOAPConnection.html
  6. ^ http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html
  7. ^ http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html
  8. ^ http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936
  9. ^ http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM2.html#63942

See also

  • JSR 67: Java(TM) APIs for XML Messaging
  • Java API for XML Messaging (JAXM) Specification 1.1
  • SOAP with Attachments API for Java (SAAJ) Specification 1.3
  • javax.xml.messaging - this package is specified in the JAXM 1.1 specification
  • javax.xml.soap - this package is specified in the SAAJ 1.3 specification
  • Overview of JAXM
  • Hello World Example for JAXM
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.