You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicemix.apache.org by ge...@apache.org on 2010/05/25 14:02:17 UTC
svn commit: r948016 - in /servicemix/documentation/trunk/docs/jbi/src:
confluence/ docbkx/
Author: gertv
Date: Tue May 25 12:02:16 2010
New Revision: 948016
URL: http://svn.apache.org/viewvc?rev=948016&view=rev
Log:
Adding pages for the JBI components
Added:
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-bean.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-bc.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-se.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-drools.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-eip.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-file.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-ftp.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-http.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-jms.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-mail.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-osworkflow.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-quartz.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-saxon.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-scripting.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-snmp.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-validation.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-vfs.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-wsn2005.wiki
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-xmpp.wiki
Removed:
servicemix/documentation/trunk/docs/jbi/src/docbkx/servicemix-bean.xml
servicemix/documentation/trunk/docs/jbi/src/docbkx/servicemix-saxon.xml
Modified:
servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki
servicemix/documentation/trunk/docs/jbi/src/docbkx/index.xml
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-bean.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-bean.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-bean.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-bean.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,34 @@
+h1. servicemix-bean
+
+h2. Overview
+The ServiceMix Bean component provides integration with beans (POJOs) with the JBI bus to make it easy to use POJOs to process JBI message exchanges. Like in an Message Driven Bean in J2EE a POJO will receive a message from the NMR and process it in any way it likes. Unlike in a JMS component where the coding is already done the Bean component gives the developer the freedom to create any type of message handling but it must be hand coded all the way.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/bean/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:bean="http://servicemix.apache.org/bean/1.0">
+
+ <!-- add bean:endpoint definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-bean component only defines one endpoint, called {{bean:endpoint}}. It can be used to receive and send message exchanges from/to the NMR.
+
+h2. {{Endpoint bean:endpoint}}
+
+h3. Using a Java class
+When definining a {{bean:endpoint}} specifying a Java class name, a new instance of this class will be created for handling a single message exchange.
+
+{code}
+ <beans xmlns:bean="http://servicemix.apache.org/bean/1.0"
+ xmlns:my="urn:org:servicmix:docs:examples">
+
+ <bean:endpoint service="my:service" endpoint="endpoint"
+ class="org.apache.servicemix.docs.bean.MyHandlerBean"/>
+
+ </beans>
+{code}
+
+h3. TODO: add other configuration types
Modified: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki?rev=948016&r1=948015&r2=948016&view=diff
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki (original)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki Tue May 25 12:02:16 2010
@@ -17,11 +17,11 @@ This is an example {{camel-context.xml}}
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd">
- <camelContext xmlns="http://camel.apache.org/schema/spring">
- <route>
- <!-- route defined in the Spring DSL -->
- </route>
- </camelContext>
+ <camelContext xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <!-- route defined in the Spring DSL -->
+ </route>
+ </camelContext>
</beans>
{code}
@@ -37,9 +37,149 @@ It is also possible to use the Java DSL
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd">
+ <camelContext xmlns="http://camel.apache.org/schema/spring">
+ <packages>org.apache.servicemix.examples.camel</packages>
+ </camelContext>
+
+</beans>
+{code}
+
+h2. URI
+Camel routes use URIs to interact with the ESB. You can use these URIs to expose new endpoints on the ESB as well as to send message exchanges to existing endpoints.
+
+The snippet below automatically exposes a new endpoint to the bus, where the service QName is {{{http://foo.bar.org}MyService}} and the endpoint name is {{MyEndpoint}}.
+{code}
+from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
+{code}
+
+When a JBI endpoint appears at the end of a route, as in the example below, that will send
+{code}
+to("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
+{code}
+
+The messages sent by this producer endpoint are sent to the already deployed JBI endpoint.
+
+h3. URI format
+
+{code}
+jbi:service:serviceNamespace[sep]serviceName[?options]
+jbi:endpoint:serviceNamespace[sep]serviceName[sep]endpointName[?options]
+jbi:name:endpointName[?options]
+{code}
+
+The separator that should be used in the endpoint URL is:
+* {{/}} (forward slash), if {{serviceNamespace}} starts with {{http://}}
+* {{:}} (colon), if {{serviceNamespace}} starts with {{urn:}}.
+
+You can append query options to the URI in the following format, {{?option=value&option=value&...}}
+
+h4. Examples
+h5. Using {{jbi:service}}
+
+{code}
+jbi:service:http://foo.bar.org/MyService
+jbi:service:urn:foo:bar:MyService
+{code}
+
+h5. Using {{jbi:endpoint}}
+{code}
+jbi:endpoint:urn:foo:bar:MyService:MyEndpoint
+jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint
+{code}
+
+h5. Using {{jbi:name}}
+When using {{jbi:name}}, the component uses {{http://activemq.apache.org/camel/schema/jbi}endpoint}} as the default Service QName.
+{code}
+jbi:name:MyEndpoint
+{code}
+
+h3. URI options
+|| Name || Default value || Description ||
+| {{mep}} | MEP of the Camel Exchange | Allows users to override the MEP set on the Exchange object. Valid values for this option are {{in-only}}, {{in-out}}, {{robust-in-out}} and {{in-optional-out}}. |
+| {{operation}} | Value of the {{jbi.operation}} header property | Specifies the JBI operation for the {{MessageExchange}}. If no value is supplied, the JBI binding will use the value of the {{jbi.operation}} header property. |
+| {{serialization}} | {{basic}} | Default value ({{basic}}) will check if headers are serializable by looking at the type, setting this option to {{strict}} will detect objects that can not be serialized although they implement the {{Serializable}} interface. Set to {{nocheck}} to disable this check altogether, note that this should only be used for in-memory transports like SEDAFlow, otherwise you can expect to get {{NotSerializableException}} thrown at runtime. |
+| {{convertException}} | {{false}} | {{false}}: send any exceptions thrown from the Camel route back unmodified \\ {{true}}: convert all exceptions to a JBI FaultException (can be used to avoid non-serializable exceptions or to implement generic error handling |
+
+h4. Examples
+{code}
+jbi:service:http://foo.bar.org/MyService?mep=in-out (override the MEP, use InOut JBI MessageExchanges)
+jbi:endpoint:urn:foo:bar:MyService:MyEndpoint?mep=in (override the MEP, use InOnly JBI MessageExchanges)
+jbi:endpoint:urn:foo:bar:MyService:MyEndpoint?operation={http://www.mycompany.org}AddNumbers
+(overide the operation for the JBI Exchange to {http://www.mycompany.org}AddNumbers)
+{code}
+
+h2. Example routes
+h3. Simple Spring route
+This simple Spring route registers a new endpoint on the ESB (service {{{urn:org:example}Router}}, endpoint name {{orders}}). The message exchange contents will be logged and then forwarded to another JBI service endpoint (service {{{http://services.example.org}OrderService}})
+{code}
+<beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
+ http://www.springframework.org/schema/beans
+ http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://camel.apache.org/schema/spring
+ http://camel.apache.org/schema/spring/camel-spring.xsd">
+
<camelContext xmlns="http://camel.apache.org/schema/spring">
- <packages>org.apache.servicemix.examples.camel</packages>
+ <route>
+ <from uri="jbi:endpoint:urn:org:example:Router:orders"/>
+ <to uri="log:OrderLogging"/>
+ <to uri="jbi:service:http://services.example.org/OrderService" />
+ </route>
</camelContext>
</beans>
-{code}
\ No newline at end of file
+{code}
+
+h3. The same route using the Java DSL
+When we implement the same route in the Java DSL, we first code our {{RouteBuilder}} implementation
+{code}
+package org.apache.servicemix.example;
+
+import org.apache.camel.builder.RouteBuilder;
+
+public class JbiRouteBuilder extends RouteBuilder {
+
+ @Override
+ public void configure() throws Exception {
+ from("jbi:endpoint:urn:org:example:Router:orders")
+ .to("log:OrderLogging")
+ .to("jbi:service:http://services.example.org/OrderService");
+ }
+}
+{code}
+
+In our {{camel-context.xml}} file, we just refer to the {{org.apache.servicemix.example}} package that contains our {{JbiRouteBuilder}}.
+{code}
+<beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
+ http://www.springframework.org/schema/beans
+ http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://camel.apache.org/schema/spring
+ http://camel.apache.org/schema/spring/camel-spring.xsd">
+
+ <camelContext xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <packageScan>
+ <package>org.apache.servicemix.example</package>
+ </packageScan>
+ </route>
+ </camelContext>
+
+</beans>
+{code}
+
+
+
+
+
+h2. Special considerations
+h3. Stream handling
+If you are using a stream type as the message body, you should be aware that a stream is only capable of being read once. So if you enable {{DEBUG}} logging, the body is usually logged and thus read. To deal with this, Camel has a {{streamCaching}} option that can cache the stream, enabling you to read it multiple times.
+
+{code}
+from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething");
+{code}
+
+Camel will cache large input streams (by default, over 64K) in a {{temp}} file using {{CachedOutputStream}}. When you close the input stream, the temp file will be deleted.
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-bc.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-bc.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-bc.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-bc.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,32 @@
+h1. servicemix-cxf-bc
+
+h2. Overview
+A JBI compliant HTTP/SOAP or JMS/SOAP binding component named servicemix-cxf-bc which use apache cxf internally.
+
+The main features are:
+* JBI compliant Binding Component
+* Usable in a lightweight mode in servicemix.xml configuration files
+* SOAP 1.1 and 1.2 support
+* MIME attachments
+* Support for all MEPs as consumers or providers
+* SSL support
+* WS-Security support
+* WS-Policy support
+* WS-RM support
+* WS-Addressing support
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/cxfbc/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0">
+
+ <!-- add cxfbc:consumer or cxfbc:provider definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-cxf-bc component defines two endpoints:
+- {{cxfbc:consumer}} :: a server-side cxf endpoint that will consume plain HTTP+SOAP requests and send them into the NMR to a given JBI endpoint
+- {{cxfbc:provider}} :: a client-side jbi endpoint which can receive requests from the NMR and send them to a given url where the service is provided
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-se.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-se.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-se.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-cxf-se.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,27 @@
+h1. servicemix-cxf-se
+
+h2. Overview
+ServiceMix CXF SE component is a JBI Service Engine exposing (annotated) POJO as services on the JBI Bus.
+It uses Apache CXF internally to perform service invocations and xml marshaling.
+
+Features:
+* jsr181 annotations
+* jaxb2/aegis/xmlbeans databinding
+* wsdl auto generation
+* java proxy support
+* MTOM / attachments support
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/cxfse/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:cxfse="http://servicemix.apache.org/cxfse/1.0">
+
+ <!-- add cxfse:endpoint definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-cxf-bc component defines one endpoint type:
+- {{cxfse:endpoint}} :: no description yet
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-drools.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-drools.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-drools.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-drools.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,23 @@
+h1. servicemix-drools
+
+h2. Overview
+The ServiceMix Drools component provides JBI integration to the Drools Rules Engine.
+
+This Service Engine can be used to deploy a rules set that will implement a router or an actual service.
+
+A router will mostly act as a transparent proxy between the consumer and the target service provider mad will mostly be implemented by the jbi.route(uri) method below. This method creates a new exchange identical to the one received by the component and will send it to the specified destination. You can also send back a Fault if needed. A router can also be implemented by using directly the JBI Apis (available with the jbi helper) by using the provided client.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/drools/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:drools="http://servicemix.apache.org/drools/1.0">
+
+ <!-- add drools:endpoint definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-drools component defines one endpoint type:
+- {{drools:endpoint}} :: no description yet
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-eip.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-eip.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-eip.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-eip.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,30 @@
+h1. servicemix-eip
+
+h2. Overview
+The servicemix-eip component is a routing container where different routing patterns can be deployed as service unit.
+This component is based on the great Enterprise Integration Patterns book.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/eip/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:drools="http://servicemix.apache.org/eip/1.0">
+
+ <!-- add one of the eip endpoint definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-eip component defines several endpoint types:
+- {{eip:content-based-router}} :: Implements the Content-Based Router EIP
+- {{eip:message-filter}} :: Implements the Message Filter EIP
+- {{eip:pipeline}} :: Implements the Pipeline EIP
+- {{eip:static-recipient-list}} :: Implements the Static Recipient List EIP
+- {{eip:static-routing-slip}} :: Implements the Static Routing Slip EIP
+- {{eip:wire-tap}} :: Implements the Wire Tap EIP
+- {{eip:xpath-splitter}} :: Uses XPath to split a message
+- {{eip:split-aggregator}} :: Aggregates messages that have been split by the {{xpath-splitter}}
+- {{eip:content-enricher}} :: Implements the Content Enricher EIP
+- {{eip:resequencer}} :: Implements the Resequencer EIP
+- {{eip:async-bridge}} :: Handles an InOut exchange by correlating to separate InOnly exchanges
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-file.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-file.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-file.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-file.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,21 @@
+h1. servicemix-file
+
+h2. Overview
+The ServiceMix File component provides JBI integration to the file system. It can be used to read & write files via URI or to periodically poll directories for new files.
+
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/file/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:file="http://servicemix.apache.org/file/1.0">
+
+ <!-- add file:poller and file:sender definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-file component defines two endpoint type:
+- {{file:poller}} :: Periodically polls a directory for files and sends an exchange for every file
+- {{file:sender}} :: Writes the contents of an exchange to a file
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-ftp.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-ftp.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-ftp.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-ftp.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,21 @@
+h1. servicemix-ftp
+
+h2. Overview
+The ServiceMix FTP component provides JBI integration to the FTP servers. It can be used to read & write files over FTPor to periodically poll directories for new files.
+
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/ftp/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:ftp="http://servicemix.apache.org/ftp/1.0">
+
+ <!-- add ftp:poller and ftp:sender definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-ftp component defines two endpoint type:
+- {{ftp:poller}} :: Periodically polls a directory on an FTP server for files and sends an exchange for every file
+- {{ftp:sender}} :: Writes the contents of an exchange to a file on an FTP server
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-http.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-http.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-http.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-http.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,41 @@
+h1. servicemix-http
+
+h2. Overview
+ServiceMix ships with a JBI compliant HTTP/SOAP binding component named servicemix-http.
+
+Here are the main features:
+* JBI compliant Binding Component
+* Usable in a lightweight mode in servicemix.xml configuration files
+* Integrated HTTP server based on Jetty 6
+* HTTP Client using Jakarta Commons HTTP Client
+* Highly performant and scalable using Jetty 6 continuations
+* SOAP 1.1 and 1.2 support
+* MIME attachments
+* WS-Addressing support
+* WSDL based and XBean based deployments
+* Support for all MEPs as consumers or providers
+* SSL support
+* WS-Security support
+
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/http/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:http="http://servicemix.apache.org/http/1.0">
+
+ <!-- add http:consumer, http:soap-consumer
+ http:provider and http soap:provider definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-http component defines four endpoint type:
+- {{http:consumer}} :: This endpoint allows you to expose a service in the ESB to the outside world over HTTP. Whenever it receives an HTTP request, it will interact with the configured services on the ESB to provide the HTTP response.
+- {{http:soap-consumer}} :: Similar to {{http:consumer}}, but specifically geared towards handing SOAP requests and responses
+- {{http:provider}} :: This endpoint allows you to access remote services from within the ESB. It will perform an external HTTP request whenever it receives a JBI MessageExchange
+- {{http:soap-provider}} :: Similar to {{http:provider}}, but specifically geared towards performing SOAP requests
+
+It also provides one additional legacy endpoints, which are still available to ease migration from ServiceMix 3:
+- {{http:endpoint}} :: (Deprecated) Legacy endpoint, capable to acting as a consumer or provider based on the configuration
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-jms.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-jms.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-jms.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-jms.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,38 @@
+h1. servicemix-http
+
+h2. Overview
+ServiceMix ships with a JBI compliant JMS binding component named servicemix-jms.
+
+Here are the main features:
+* JBI compliant Binding Component
+* Usable in a lightweight mode in servicemix.xml configuration files
+* SOAP 1.1 and 1.2 support
+* MIME attachments
+* WS-Addressing support
+* WSDL based and XBean based deployments
+* Support for all MEPs as consumers or providers
+
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/jms/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:jms="http://servicemix.apache.org/jms/1.0">
+
+ <!-- add jms:consumer, jms:soap-consumer, jms:jca-consumer,
+ jms:provider, jms:soap-provider and jms:jca-provider definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-jms component defines six endpoint type:
+- {{jms:consumer}} :: This endpoint allows you to expose a service in the ESB to the outside world over JMS. Whenever it receives a JMS message, it will interact with the configured services on the ESB.
+- {{jms:soap-consumer}} :: Similar to {{jms:consumer}}, but specifically geared towards handing SOAP requests and responses
+- {{jms:jca-consumer}} :: Similar to {{jms:consumer}}, but adds the possibility of using a JCA resource adapter
+- {{jms:provider}} :: This endpoint allows you to access remote services from within the ESB. It will send a JMS message whenever it receives a JBI MessageExchange
+- {{jms:soap-provider}} :: Similar to {{jms:provider}}, but specifically geared towards performing SOAP requests
+- {{jms:jca-provider}} :: Similar to {{jms:provider}}, but adds the possibility of using a JCA resource adapter
+
+It also provides one additional legacy endpoints, which are still available to ease migration from ServiceMix 3:
+- {{jms:endpoint}} :: (Deprecated) Legacy endpoint, capable to acting as a consumer or provider based on the configuration
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-mail.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-mail.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-mail.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-mail.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,21 @@
+h1. servicemix-mail
+
+h2. Overview
+he ServiceMix Mail component provides support for receiving and sending mails via the enterprise service bus.
+
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/mail/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:mail="http://servicemix.apache.org/mail/1.0">
+
+ <!-- add mail:poller and mail:sender definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-mail component defines two endpoint type:
+- {{mail:poller}} :: Connect to a POP3 or IMAP server and send a MessageExchange for every mail
+- {{mail:sender}} :: Connect to an SMTP server and send a mail for every JBI MessageExchange it receives
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-osworkflow.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-osworkflow.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-osworkflow.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-osworkflow.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,20 @@
+h1. servicemix-osworkflow
+
+h2. Overview
+The ServiceMix OSWorkflow component provides workflow functionality to the ESB. You can specify one or more workflows and it's processing will start when a valid message is received.
+
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/osworkflow/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:osworkflow="http://servicemix.apache.org/osworkflow/1.0">
+
+ <!-- add osworkflow:endpoint here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-osworkflow component defines a single endpoint type:
+- {{osworkflow:endpoint}} :: The endpoint will receive messages from the NMR and will then start the processing of the workflow.
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-quartz.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-quartz.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-quartz.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-quartz.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,19 @@
+h1. servicemix-quartz
+
+h2. Overview
+The servicemix-quartz component is a standard JBI Service Engine able to schedule and trigger jobs using the great Quartz scheduler.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/quartz/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:osworkflow="http://servicemix.apache.org/quartz/1.0">
+
+ <!-- add quartz:endpoint here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-quartz component defines a single endpoint type:
+- {{quartz:endpoint}} :: The quartz endpoint can be used to fire message exchanges at a given (recurrent) time.
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-saxon.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-saxon.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-saxon.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-saxon.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,169 @@
+h1. servicemix-saxon
+
+h2. Overview
+The servicemix-saxon component is a standard JBI Service Engine for XSLT / XQuery. This component is based on Saxon and supports XSLT 2.0 and XPath 2.0, and XQuery 1.0.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/saxon/1.0}}. This is an example of {{xbean.xml}} file with a namespace definition with prefix {{saxon}}.
+{code}
+ <beans xmlns:saxon="http://servicemix.apache.org/saxon /1.0">
+
+ <!-- add saxon:xslt, saxon:xquery or saxon:proxy definitions here -->
+
+ </beans>
+{code}
+
+h3. Endpoint types
+The servicemix-saxon component defines these endpoints:
+- {{saxon:xslt}} :: Translates the in message content using XSLT to send back the translated content in the out message
+- {{saxon:proxy}} :: Acts as a proxy for an endpoint, translating the message passed to/from the endpoint using XSLT
+- {{saxon:xquery}} :: Use xquery to extract parts of the XML
+
+h2. Endpoint {{saxon:xslt}}
+
+The XSLT endpoint can be used to apply an XSLT stylesheet to the incoming exchange and will return the transformed result as the output message.
+
+Simple transformation:
+{code:lang=xml}
+<saxon:xslt service="test:xslt" endpoint="endpoint"
+ resource="classpath:transform.xsl" />
+{code}
+
+Dynamic stylesheet selection:
+{code:lang=xml}
+<saxon:xslt service="test:xslt-dynamic" endpoint="endpoint">
+ <saxon:expression>
+ <bean class="org.apache.servicemix.expression.PropertyExpression">
+ <property name="property" value="xslt.source" />
+ </bean>
+ </saxon:expression>
+</saxon:xslt>
+{code}
+
+|| Name || Type || Description || Required ||
+| resource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | the spring resource pointing to the XSLT stylesheet | one of (resource, expression) |
+| expression | [ServiceMix expression|http://incubator.apache.org/servicemix/dist/servicemix-3.0-incubating/site/servicemix-core/apidocs/org/apache/servicemix/expression/Expression.html] | expression used to dynamically load the stylesheet | one of (resource, expression) |
+| wsdlResource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | if set, the wsdl will be retrieved from the given Spring resource | no |
+| transformerFactory | TransformerFactory | TraX factory to create transformers | defaults to Saxon implementation |
+| configuration | [Saxon configuration|http://www.saxonica.com/documentation/javadoc/net/sf/saxon/Configuration.html] | Saxon configuration | no |
+| result | String | Output result type | defaults to {{dom}}, possible values are {{dom}}, {{bytes}}, {{string}} |
+| copyAttachments | boolean | | defaults to {{true}} |
+| copyProperties | boolean | | defaults to {{true}} |
+| copySubject | boolean | | defaults to {{true}} |
+| useDomSourceForXslt | boolean | force the transformation of the xslt stylesheet into a DOM document before giving it to the transformer | defaults to {{true}} |
+| useDomSourceForContent | boolean | force the transformation of the incoming JBI message into a DOM document before giving it to the transformer | no |
+| parameters | Map | additional parameters to give to the transformation engine | no |
+
+h3. Using properties and parameters
+
+All properties defined on the JBI exchange and input JBI message will be available for use inside the XSLT stylesheet as parameters.
+In addtion to those properties and the one specified in the {{parameters}} property on the endpoint, the following objects are also available:
+* exchange: the JBI exchange
+* in: the input JBI NormalizedMessage
+* component: the XsltEndpoint instance being called
+
+All those parameters can be accessed using XSLT standard ways.
+For example:
+{code:lang=xml}
+<xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+ <xsl:param name="stringParam"/>
+ <xsl:param name="integerParam"/>
+ ...
+</xsl:stylesheet>
+{code}
+
+and the configuration of those values on the endpoint (in case they are not available on the JBI exchange / message):
+{code:lang=xml}
+<saxon:xslt service="test:xslt-params" endpoint="endpoint"
+ resource="classpath:parameter-test.xsl">
+ <property name="parameters">
+ <map>
+ <entry key="stringParam" value="cheeseyCheese"/>
+ <entry key="integerParam">
+ <bean class="java.lang.Integer">
+ <constructor-arg index="0" value="4002"/>
+ </bean>
+ </entry>
+ </map>
+ </property>
+</saxon:xslt>
+{code}
+
+h2. Endpoint {{saxon:proxy}}
+
+One common use case is the need to transform a request coming from a service and send it to another service and do the same with the response. A simple example is the need to translate the request and responses between two SOAP endpoints. Such a use case could be implemented using two XSLT endpoints and an EIP StaticRoutingSlip. However, there are some drawbacks, as the operation is lost in the process, and a static routing slip can not be used to process InOnly exchanges.
+
+The 4.0 version of servicemix-saxon provides such a feature in a single endpoint:
+
+{code:lang=xml}
+<saxon:proxy service="test:proxy" endpoint="endpoint"
+ resource="classpath:transform-in.xsl"
+ outResource="classpath:transform-out.xsl"
+ faultResource="classpath:transform-fault.xsl">
+ <saxon:target>
+ <saxon:exchange-target service="test:echo" />
+ </saxon:target>
+</saxon:proxy>
+{code}
+
+|| Name || Type || Description || Required ||
+| resource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | the spring resource pointing to the XSLT stylesheet used to transform the input message | no |
+| outResource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | the spring resource pointing to the XSLT stylesheet used to transform the output message | no |
+| faultResource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | the spring resource pointing to the XSLT stylesheet used to transform the fault message | no |
+| expression | [ServiceMix expression|http://incubator.apache.org/servicemix/dist/servicemix-3.0-incubating/site/servicemix-core/apidocs/org/apache/servicemix/expression/Expression.html] | expression used to dynamically load the stylesheet. If set, it will prevail against all resource, outResource and faultResource attributes | no |
+| wsdlResource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | if set, the wsdl will be retrieved from the given Spring resource | no |
+| transformerFactory | TransformerFactory | TraX factory to create transformers | defaults to Saxon implementation |
+| configuration | [Saxon configuration|http://www.saxonica.com/documentation/javadoc/net/sf/saxon/Configuration.html] | Saxon configuration | no |
+| result | String | Output result type | defaults to {{dom}}, possible values are {{dom}}, {{bytes}}, {{string}} |
+| copyAttachments | boolean | | defaults to {{true}} |
+| copyProperties | boolean | | defaults to {{true}} |
+| copySubject | boolean | | defaults to {{true}} |
+| target | ExchangeTarget | the destination where the transformed exchange will be sent to | yes |
+
+
+h2. Endpoint {{saxon:xquery}}
+
+The XQuery endpoint can be used to apply a selected XQuery to the input document.
+
+Simple XQuery:
+{code:lang=xml}
+<saxon:xquery service="test:xquery" endpoint="endpoint"
+ resource="classpath:query.xq" />
+{code}
+
+Inlined XQuery with specific output configuration:
+{code:lang=xml}
+<saxon:xquery service="test:xquery-inline" endpoint="endpoint">
+ <saxon:query>
+ for $x in /bookstore/book
+ where $x/price > 30
+ return $x/title
+ </saxon:query>
+ <saxon:outputProperties>
+ <saxon:property key="{http://saxon.sf.net/}wrap-result-sequence">yes</saxon:property>
+ </saxon:outputProperties>
+</saxon:xquery>
+{code}
+
+Dynamic selection of XQuery:
+{code:lang=xml}
+<saxon:xquery service="test:xquery-dynamic" endpoint="endpoint">
+ <saxon:expression>
+ <bean class="org.apache.servicemix.expression.PropertyExpression">
+ <property name="property" value="xquery.source" />
+ </bean>
+ </saxon:expression>
+</saxon:xquery>
+{code}
+
+|| Name || Type || Description || Required ||
+| query | String | inlined XQuery | one of (query, resource, expression) |
+| resource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | the spring resource pointing to the XQuery | one of (query, resource, expression) |
+| expression | [ServiceMix expression|http://incubator.apache.org/servicemix/dist/servicemix-3.0-incubating/site/servicemix-core/apidocs/org/apache/servicemix/expression/Expression.html] | expression used to dynamically load the xquery | one of (query, resource, expression) |
+| wsdlResource | [Spring resource|http://springframework.org/docs/api/org/springframework/core/io/Resource.html] | if set, the wsdl will be retrieved from the given Spring resource | no |
+| outputProperties | Map | Saxon specific output properties | no |
+| configuration | [Saxon configuration|http://www.saxonica.com/documentation/javadoc/net/sf/saxon/Configuration.html] | Saxon configuration | no |
+| result | String | Output result type | defaults to {{dom}}, possible values are {{dom}}, {{bytes}}, {{string}} |
+| copyAttachments | boolean | | defaults to {{true}} |
+| copyProperties | boolean | | defaults to {{true}} |
+| copySubject | boolean | | defaults to {{true}} |
\ No newline at end of file
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-scripting.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-scripting.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-scripting.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-scripting.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,24 @@
+h1. servicemix-scripting
+
+h2. Overview
+The ServiceMix Scripting component provides support for processing scripts using JSR-223 compliant scripting languages.
+
+The component is currently shipping with:
+* Groovy (1.5.6)
+* JRuby (1.1.2)
+* Rhino JavaScript (1.7R1)
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/scripting/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:scripting="http://servicemix.apache.org/scripting/1.0">
+
+ <!-- add scripting:endpoint here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-scripting component defines a single endpoint type:
+- {{scripting:endpoint}} :: The scripting endpoint can be used to use scripts to handle exchanges or send new exchanges
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-snmp.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-snmp.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-snmp.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-snmp.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,20 @@
+h1. servicemix-snmp
+
+h2. Overview
+The ServiceMix SNMP component provides support for receiving SNMP events via the enterprise service bus by using the SNMP4J library.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/snmp/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:snmp="http://servicemix.apache.org/snmp/1.0">
+
+ <!-- add snmp:poller or snmp:sender definitions here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-snmp component defines two endpoint types:
+- {{snmp:poller}} :: Periodically polls a device status using SNMP and sends the OIDs as a JBI MessageExchange
+- {{snmp:trap-consumer}} :: Consumes an SNMP trap message and sends the OIDs as a JBI MessageExchange
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-validation.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-validation.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-validation.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-validation.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,19 @@
+h1. servicemix-validation
+
+h2. Overview
+The ServiceMix Validation component provides schema validation of documents using JAXP 1.3 and XMLSchema or RelaxNG.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/validation/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:scripting="http://servicemix.apache.org/validation/1.0">
+
+ <!-- add validation:endpoint here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-validation component defines a single endpoint type:
+- {{validation:endpoint}} :: Validates the incoming XML message - can be configured to fail the exchange or to send validation errors back to the sender in the message body.
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-vfs.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-vfs.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-vfs.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-vfs.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,20 @@
+h1. servicemix-vfs
+
+h2. Overview
+The ServiceMix VFS component provides support for reading from and writing to virtual file systems via the enterprise service bus by using the Apache commons-vfs library.
+
+h3. Namespace and xbean.xml
+The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/vfs/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}.
+{code}
+<beans xmlns:vfs="http://servicemix.apache.org/vfs/1.0">
+
+ <!-- add vfs:poller or vfs:sender here -->
+
+</beans>
+{code}
+
+h3. Endpoint types
+The servicemix-vfs component defines two endpoint types:
+- {{vfs:poller}} :: Periodically polls a directory on one of the VFS-supported file systems for files and sends an exchange for every file
+- {{vfs:sender}} :: Writes the contents of an exchange to a file on one of the VFS-supported file systems
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-wsn2005.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-wsn2005.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-wsn2005.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-wsn2005.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,6 @@
+h1. servicemix-wsn2005
+
+h2. Overview
+The servicemix-wsn2005 is a standard JBI Service Engine which implements the WS-Notification specification from Oasis.
+
+
Added: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-xmpp.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-xmpp.wiki?rev=948016&view=auto
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-xmpp.wiki (added)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-xmpp.wiki Tue May 25 12:02:16 2010
@@ -0,0 +1,6 @@
+h1. servicemix-xmpp
+
+h2. Overview
+The ServiceMix XMPP component is used to communicate with XMPP (Jabber) servers through the JBI bus.
+
+
Modified: servicemix/documentation/trunk/docs/jbi/src/docbkx/index.xml
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/docbkx/index.xml?rev=948016&r1=948015&r2=948016&view=diff
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/docbkx/index.xml (original)
+++ servicemix/documentation/trunk/docs/jbi/src/docbkx/index.xml Tue May 25 12:02:16 2010
@@ -49,20 +49,32 @@
<part>
<title>ServiceMix JBI Components</title>
- <xi:include href="servicemix-bean.xml" parse="xml"/>
+ <xi:include href="servicemix-bean.wiki.xml" parse="xml"/>
<xi:include href="servicemix-camel.wiki.xml" parse="xml"/>
- <xi:include href="servicemix-saxon.xml" parse="xml"/>
-
+ <xi:include href="servicemix-cxf-bc.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-cxf-se.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-drools.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-eip.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-file.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-ftp.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-http.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-jms.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-mail.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-osworkflow.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-saxon.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-scripting.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-snmp.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-validation.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-vfs.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-wsn2005.wiki.xml" parse="xml"/>
+ <xi:include href="servicemix-xmpp.wiki.xml" parse="xml"/>
<chapter>
<title>Test snippets</title>
<xi:include href="snippet://&servicemix-bean-source;/src/test/java/org/apache/servicemix/bean/beans/AnnotatedBean.java"/>
</chapter>
-
</part>
-
-
-
+
<appendix>
<title>JBI Component XSD reference</title>
<xi:include href="appendix/servicemix-bean.xml" parse="xml"/>