Java API for XML Messaging - Revision history

InternetArchiveBot: Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.3) (Whoop whoop pull up - 13006

2023-03-29T23:33:07Z

Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.3) (Whoop whoop pull up - 13006

← Previous revision		Revision as of 23:33, 29 March 2023
Line 59:		Line 59:
	* [https://mq.java.net/nonav/javadoc/5.0/javadoc/index.html?javax/xml/messaging/package-summary.html javax.xml.messaging] - this package is specified in the JAXM 1.1 specification		* [https://mq.java.net/nonav/javadoc/5.0/javadoc/index.html?javax/xml/messaging/package-summary.html javax.xml.messaging] - this package is specified in the JAXM 1.1 specification
	* [http://docs.oracle.com/javaee/7/api/index.html?javax/xml/soap/package-summary.html javax.xml.soap] - this package is specified in the SAAJ 1.3 specification		* [http://docs.oracle.com/javaee/7/api/index.html?javax/xml/soap/package-summary.html javax.xml.soap] - this package is specified in the SAAJ 1.3 specification
	* [http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 Overview of JAXM]		* [http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 Overview of JAXM] {{Webarchive\|url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|date=2017-05-10 }}
	* [http://www.java2s.com/Code/Java/J2EE/ThisexampledemonstratesahelloworldexampleforusingJAXMAPI.htm Hello World Example for JAXM]		* [http://www.java2s.com/Code/Java/J2EE/ThisexampledemonstratesahelloworldexampleforusingJAXMAPI.htm Hello World Example for JAXM]

Citation bot: Alter: title. | Use this bot. Report bugs. | Suggested by AManWithNoPlan | #UCB_CommandLine

2022-08-22T19:00:38Z

Alter: title. | Use this bot. Report bugs. | Suggested by AManWithNoPlan | #UCB_CommandLine

← Previous revision		Revision as of 19:00, 22 August 2022
Line 19:		Line 19:

	==Messages==		==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.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=~~Archived~~ ~~copy~~ \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>		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.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=The Java(tm) XML Pack \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>

	==Connections==		==Connections==
	A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=~~Archived~~ ~~copy~~ \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>		A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=The Java(tm) XML Pack \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>
	The JAXM API provides the class and interface to represent two kinds of connections:		The JAXM API provides the class and interface to represent two kinds of connections:
	*[http://docs.oracle.com/javaee/1.4/api/javax/xml/soap/SOAPConnection.html javax.xml.soap.SOAPConnection]—a connection from the sender directly to the receiver (a point-to-point connection)		*[http://docs.oracle.com/javaee/1.4/api/javax/xml/soap/SOAPConnection.html javax.xml.soap.SOAPConnection]—a connection from the sender directly to the receiver (a point-to-point connection)
Line 35:		Line 35:

	==Messaging Providers==		==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.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=~~Archived~~ ~~copy~~ \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>		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.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=The Java(tm) XML Pack \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>

	===When to use a Messaging Provider===		===When to use a Messaging Provider===

InternetArchiveBot: Rescuing 3 sources and tagging 0 as dead.) #IABot (v2.0.8.8) (Ost316 - 10336

2022-07-10T07:16:41Z

Rescuing 3 sources and tagging 0 as dead.) #IABot (v2.0.8.8) (Ost316 - 10336

← Previous revision		Revision as of 07:16, 10 July 2022
Line 19:		Line 19:

	==Messages==		==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.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 ~~{{Dead~~ ~~link~~\|date=~~February~~ ~~2022~~}}</ref>		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.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=Archived copy \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>

	==Connections==		==Connections==
	A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 ~~{{Dead~~ ~~link~~\|date=~~February~~ ~~2022~~}}</ref>		A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=Archived copy \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>
	The JAXM API provides the class and interface to represent two kinds of connections:		The JAXM API provides the class and interface to represent two kinds of connections:
	*[http://docs.oracle.com/javaee/1.4/api/javax/xml/soap/SOAPConnection.html javax.xml.soap.SOAPConnection]—a connection from the sender directly to the receiver (a point-to-point connection)		*[http://docs.oracle.com/javaee/1.4/api/javax/xml/soap/SOAPConnection.html javax.xml.soap.SOAPConnection]—a connection from the sender directly to the receiver (a point-to-point connection)
Line 35:		Line 35:

	==Messaging Providers==		==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.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 ~~{{Dead~~ ~~link~~\|date=~~February~~ ~~2022~~}}</ref>		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.<ref>{{Cite web \|url=http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|title=Archived copy \|access-date=2013-02-05 \|archive-date=2017-05-10 \|archive-url=https://web.archive.org/web/20170510093344/http://www4.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 \|url-status=dead }}</ref>

	===When to use a Messaging Provider===		===When to use a Messaging Provider===

VulcanSphere: Adding short description: "Application programming interface" (Shortdesc helper)

2022-04-29T12:02:18Z

Adding short description: "Application programming interface" (Shortdesc helper)

← Previous revision		Revision as of 12:02, 29 April 2022
Line 1:		Line 1:
			{{Short description\|Application programming interface}}
	The '''Java API for XML Messaging (JAXM)''' enables [[Distributed computing\|distributed software]] applications to communicate using [[Extensible Markup Language\|XML]] (and [[SOAP]]). JAXM supports both asynchronous and synchronous messaging.		The '''Java API for XML Messaging (JAXM)''' enables [[Distributed computing\|distributed software]] applications to communicate using [[Extensible Markup Language\|XML]] (and [[SOAP]]). JAXM supports both asynchronous and synchronous messaging.

Uzume: /* Overview */ fix URL

2022-03-02T14:05:35Z

Overview: fix URL

← Previous revision		Revision as of 14:05, 2 March 2022
Line 15:		Line 15:
	The complete JAXM API comes with two packages:<ref>{{Cite web\|url=http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html\|title = Java API for XML Messaging}}</ref>		The complete JAXM API comes with two packages:<ref>{{Cite web\|url=http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html\|title = Java API for XML Messaging}}</ref>
	*[http://docs.oracle.com/javaee/7/api/index.html?javax/xml/soap/package-summary.html '''javax.xml.soap:'''] This package contains the API for creating and populating a SOAP message.		*[http://docs.oracle.com/javaee/7/api/index.html?javax/xml/soap/package-summary.html '''javax.xml.soap:'''] This package contains the API for creating and populating a SOAP message.
	*[https://mq.~~java~~.~~net~~/~~nonav~~/javadoc/5.0/javadoc/~~index.html?~~javax/xml/messaging/package-summary.html '''javax.xml.messaging:'''] This package allows one to send one-way messages via a messaging provider.		*[https://javaee.github.io/openmq/www/javadoc/5.0/javadoc/javax/xml/messaging/package-summary.html '''javax.xml.messaging:'''] This package allows one to send one-way messages via a messaging provider.

	==Messages==		==Messages==

BrownHairedGirl: {{Dead link}} tag on bare URL refs which return HTTP 404 or 410

2022-02-22T15:58:48Z

{{Dead link}} tag on bare URL refs which return HTTP 404 or 410

← Previous revision		Revision as of 15:58, 22 February 2022
Line 18:		Line 18:

	==Messages==		==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.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936</ref>		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.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 {{Dead link\|date=February 2022}}</ref>

	==Connections==		==Connections==
	A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936</ref>		A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 {{Dead link\|date=February 2022}}</ref>
	The JAXM API provides the class and interface to represent two kinds of connections:		The JAXM API provides the class and interface to represent two kinds of connections:
	*[http://docs.oracle.com/javaee/1.4/api/javax/xml/soap/SOAPConnection.html javax.xml.soap.SOAPConnection]—a connection from the sender directly to the receiver (a point-to-point connection)		*[http://docs.oracle.com/javaee/1.4/api/javax/xml/soap/SOAPConnection.html javax.xml.soap.SOAPConnection]—a connection from the sender directly to the receiver (a point-to-point connection)
Line 34:		Line 34:

	==Messaging Providers==		==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.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936</ref>		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.<ref>http://www.tecnun.es/asignaturas/InteInfo/Recursos/Xml/docs/tutorial/doc/JAXM3.html#63936 {{Dead link\|date=February 2022}}</ref>

	===When to use a Messaging Provider===		===When to use a Messaging Provider===

Citation bot: Add: title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 794/2189

2022-02-15T12:42:08Z

Add: title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 794/2189

← Previous revision		Revision as of 12:42, 15 February 2022
Line 4:		Line 4:

	==Overview==		==Overview==
	The [[List of Java APIs\|Java API]] for XML Messaging (JAXM) enables developers to use [http://www.ibm.com/developerworks/library/co-tutintro.html XML messaging] using the Java platform. Developers can create and send XML messages over the internet using the JAXM API.<ref>http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html</ref>		The [[List of Java APIs\|Java API]] for XML Messaging (JAXM) enables developers to use [http://www.ibm.com/developerworks/library/co-tutintro.html XML messaging] using the Java platform. Developers can create and send XML messages over the internet using the JAXM API.<ref>{{Cite web\|url=http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html\|title = Java API for XML Messaging}}</ref>
	[[File:B2B Messaging Conceptual Model.png\|thumbnail\|The following figure presents a conceptual relationship between JAXM and other architectural elements required in web-based, business-to-business messaging.]]		[[File:B2B Messaging Conceptual Model.png\|thumbnail\|The following figure presents a conceptual relationship between JAXM and other architectural elements required in web-based, business-to-business messaging.]]

Line 13:		Line 13:
	*Reliable messaging with features such as guaranteed delivery		*Reliable messaging with features such as guaranteed delivery

	The complete JAXM API comes with two packages:<ref>http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html</ref>		The complete JAXM API comes with two packages:<ref>{{Cite web\|url=http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM.html\|title = Java API for XML Messaging}}</ref>
	*[http://docs.oracle.com/javaee/7/api/index.html?javax/xml/soap/package-summary.html '''javax.xml.soap:'''] This package contains the API for creating and populating a SOAP message.		*[http://docs.oracle.com/javaee/7/api/index.html?javax/xml/soap/package-summary.html '''javax.xml.soap:'''] This package contains the API for creating and populating a SOAP message.
	*[https://mq.java.net/nonav/javadoc/5.0/javadoc/index.html?javax/xml/messaging/package-summary.html '''javax.xml.messaging:'''] This package allows one to send one-way messages via a messaging provider.		*[https://mq.java.net/nonav/javadoc/5.0/javadoc/index.html?javax/xml/messaging/package-summary.html '''javax.xml.messaging:'''] This package allows one to send one-way messages via a messaging provider.
Line 28:		Line 28:
	===SOAP Connection===		===SOAP Connection===
	{{see also\|SOAP with Attachments API for Java}}		{{see also\|SOAP with Attachments API for Java}}
	A SOAPConnection is a point-to-point connection for sending messages directly to a remote party.<ref>http://docs.oracle.com/javaee/5/api/javax/xml/soap/SOAPConnection.html</ref> 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.<ref>http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html</ref>		A SOAPConnection is a point-to-point connection for sending messages directly to a remote party.<ref>{{Cite web\|url=http://docs.oracle.com/javaee/5/api/javax/xml/soap/SOAPConnection.html\|title = SOAPConnection (Java EE 5 SDK)}}</ref> 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.<ref>{{Cite web\|url=http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html\|title=Overview of JAXM}}</ref>

	===Provider Connection===		===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.<ref>http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html</ref>		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.<ref>{{Cite web\|url=http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html\|title=Overview of JAXM}}</ref>

	==Messaging Providers==		==Messaging Providers==
Line 47:		Line 47:
	*The application can be written using the J2SE platform		*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		*The application is not required to be deployed in a servlet container or a J2EE container
	*No configuration is required<ref>http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM2.html#63942</ref>		*No configuration is required<ref>{{Cite web\|url=http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM2.html#63942\|title=Overview of JAXM}}</ref>

	==References==		==References==

Uzume: /* SOAP Connection */

2020-07-12T22:03:26Z

SOAP Connection

← Previous revision		Revision as of 22:03, 12 July 2020
Line 27:		Line 27:

	===SOAP Connection===		===SOAP Connection===
			{{see also\|SOAP with Attachments API for Java}}
	A SOAPConnection is a point-to-point connection for sending messages directly to a remote party.<ref>http://docs.oracle.com/javaee/5/api/javax/xml/soap/SOAPConnection.html</ref> 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.<ref>http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html</ref>		A SOAPConnection is a point-to-point connection for sending messages directly to a remote party.<ref>http://docs.oracle.com/javaee/5/api/javax/xml/soap/SOAPConnection.html</ref> 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.<ref>http://docs.oracle.com/javaee/1.3/tutorial/doc/JAXM3.html</ref>

Informatik01: Removed the outdated information.

2016-08-08T11:18:08Z

Removed the outdated information.

← Previous revision		Revision as of 11:18, 8 August 2016
Line 1:		Line 1:
	The '''Java API for XML Messaging (JAXM)''' enables [[Distributed computing\|distributed software]] applications to communicate using [[Extensible Markup Language\|XML]] (and [[SOAP]]). JAXM supports both asynchronous and synchronous messaging. ~~JAXM is a replacement for [[SAAJ\|SOAP with Attachments API for Java]]~~		The '''Java API for XML Messaging (JAXM)''' enables [[Distributed computing\|distributed software]] applications to communicate using [[Extensible Markup Language\|XML]] (and [[SOAP]]). JAXM supports both asynchronous and synchronous messaging.

	JAXM is one of the [[Java XML]] [[programming language\|programming]] [[Application programming interface\|API]]s		JAXM is one of the [[Java XML]] [[programming language\|programming]] [[Application programming interface\|API]]s

BG19bot: Remove blank line(s) between list items per WP:LISTGAP to fix an accessibility issue for users of screen readers. Do WP:GENFIXES and cleanup if needed. Discuss this at Wikipedia talk:WikiProject Accessibility#LISTGAP

2016-03-22T07:01:32Z

Remove blank line(s) between list items per WP:LISTGAP to fix an accessibility issue for users of screen readers. Do WP:GENFIXES and cleanup if needed. Discuss this at Wikipedia talk:WikiProject Accessibility#LISTGAP

← Previous revision		Revision as of 07:01, 22 March 2016
Line 10:		Line 10:

	*One-way (asynchronous) messaging		*One-way (asynchronous) messaging

	*Routing of a message to more than one party		*Routing of a message to more than one party

	*Reliable messaging with features such as guaranteed delivery		*Reliable messaging with features such as guaranteed delivery

Line 47:		Line 45:

	*The application can be written using the J2SE platform		*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		*The application is not required to be deployed in a servlet container or a J2EE container

	*No configuration is required<ref>http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM2.html#63942</ref>		*No configuration is required<ref>http://www.inf.fu-berlin.de/lehre/SS03/19560-P/Docs/JWSDP/tutorial/doc/JAXM2.html#63942</ref>