META-INF.mule-ajax.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of mule-transport-ajax Show documentation
Show all versions of mule-transport-ajax Show documentation
A Mule transport for receiving and dispatching AJAX events using Cometd (Bayeux)
The new AJAX connector allows Mule events to be sent and received in a web browser. The connector includes a JavaScript client that can be used to listen for events, send events and perform RPC calls. The AJAX connector works when deployed in Mule stand-alone or embedded in a servlet container such as Apache Tomcat.
AJAX
Ajax Transport
Allows Mule to expose Mule Services over HTTP using a Jetty HTTP server and Cometd. A single Jetty server is created for each connector instance. One connector can serve many endpoints. Users should rarely need to have more than one AJAX servlet connector.
When using AJAX embedded (not within a servlet container) a URL needs to be configured to create an AJAX server hosted in Mule. The URL should be in the form of http://(host):(port)/(path) note that https can also be used, but you will need to set the TLS information on the connector.
Specifies a local path where files will be served from. The local path gets mapped directly to the path on the 'serverUrl'.
By default, an asynchronous reply to the inbound endpoint is sent back. This can cause unwanted side effects in some cases, use this attribute to disable.
Allows a Mule service to receive AJAX events over HTTP using a Jetty server. This is different from the equivalent {{servlet-inbound-endpoint}} because it uses an embedded servlet container rather that relying on a pre-existing servlet container instance. This endpoint type should not be used if running Mule embedded in a servlet container.
the ajax channel to bind the service endpoint to. This channel path is independent context path that your application is deployed to in the servlet container.
Allows a Mule service to send AJAX events over HTTP using Bayeux. JavaScript clients can register interest in these events using the Mule JavaScript client.
Allows users to configure a global AJAX endpoint. Global endpoints can be referenced in the configuration and further configuration added. Think of global endpoints as template endpoint configurations. Using global endpoints has the advantage that endpoint configuration can be separated from the service flow.
the ajax channel to bind the service endpoint to. This channel path is independent context path that your application is deployed to in the servlet container.
Allows a Mule service to receive AJAX events sent via a servlet container. This endpoint should be used if Mule is embedded inside a servlet container. This endpoint will bind to the servlet http connection (typically port 8080).
Allows a Mule service endpoint to send AJAX events to a browser using cometd. The default outbound transformer will convert the payload of the event to JSON, The only other formats that are useful at the browser are XML and plain text. However, neither are as easierto use and JSON is recommended. To use a different format you just need to add a different transformer to the endpoint endpoint configuration.
Allows users to configure a global Servlet endpoint.
the ajax channel to bind the service endpoint to. This channel path is independent context path that your application is deployed to in the servlet container.
If set to true the dispatcher will cache messages if there are no clients subscribed to this channel.
If cache messages is set to true, this value determines the size of the memory cache. The cache will automatically expire older items to make room for newer items.
0=none, 1=info, 2=debug
The server side poll timeout in milliseconds (default 250000). This is how long the server will hold a reconnect request before responding.
he client side poll timeout in milliseconds (default 0). How long a client will wait between reconnects
The max client side poll timeout in milliseconds (default 30000). A client will be removed if a connection is not received in this time.
If "true" (default) then the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.
The client side poll timeout if multiple connections are detected from the same browser (default 1500).
The number of message refs at which the a single message response will be cached instead of being generated for every client delivered to. Done to optimize a single message being sent to multiple clients.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy