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 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:

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]
gollark: <@319753218592866315> You are to give osmarks.net 901271294111111111111111888888888892471489618461928461741874617846189428971947297419 funding for TPUs.
gollark: > What is a helloboi?<|endoftext|>Maybe if it compresses them somehow.<|endoftext|>I mean, maybe you could do it.<|endoftext|>The program reads the output into memory.<|endoftext|>This is the output from the wrong one.<|endoftext|>I suppose I could make it send a buffer or something.<|endoftext|>That's not the output.<|endoftext|>This is a great idea: maybe a buffer or something, but it's not that.<|endoftext|>Not as far as I can tell.<|endoftext|>It can export messages from another HTTP HTTP server, it's not encrypted.<|endoftext|>I'm aware of a "window" menu.<|endoftext|>This is a bizarre, isn't it.<|endoftext|>It's not web-based, and it's not web-based, but I assume it's HTTP-based, so I can't access it and it'll probably be used for HTTP requests.<|endoftext|>I could make a simple script.<|endoftext|>I guess that'd be
gollark: If you fund osmarks.net with 81294129046894162481647126412846194 funding, I can buy a TPU and execute it faster.
gollark: I'm asking it about helloboi first. It is very slow.
gollark: > What if bees literally apioform?<|endoftext|>It's very popular.<|endoftext|>In the current network, it's not very widely used, and it's not really used yet.<|endoftext|>I don't see why that's a quirk of some sort.<|endoftext|>I still think that the best way to do rights is to have people arbitrarily erase their memory and/or repurpose each other.<|endoftext|><@!2930660666066606688215756> Yes.<|endoftext|>I should probably just transfer ownership to the potatOS registry.<|endoftext|><@!2930660668866606666606667890625663247974> Give me the code and/or soul and/or soul and/or soul and/or soul and/or soul.<|endoftext|>The PotatOS privacy policy is very clear.<|endoftext|>It's not anomalous, though. It's anomalous.<|endoftext|>I see.<|endoftext|>I've heard of it, and it's a "

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
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.