[CONF] Apache Camel: JBI (page edited)

[confluence]

Page Edited : CAMEL : JBI JBI has been edited by willem jiang (Mar 11, 2009). (View changes) Content: JBI Component The jbi: component is provided by the ServiceMix Camel module and provides integration with a JBI Normalized Message Router such as provided by Apache ServiceMix See below for information regarding using StreamSource types from ServiceMix in Camel. Following code from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint") automatically exposes new endpoint to the bus where service qname is {http://foo.bar.org}MyService and endpoint name is MyEndpoint (refer to URI format later). All that has to be done to use this endpoint is to send messages from some endpoint already declared (for example with jms:endpoint) to this JBI camel endpoint (the same way as messages are sent to EIP endpoints or any other endpoint) and camel will pick it up the same way as it picks any other messages. Sending works in the same way: to("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint") Is used to send messages to JBI endpoint already deployed to the bus. It could be an endpoint exposed by jms:endpoint, http:provider or anything else. URI format jbi:service:serviceNamespace[sep]serviceName jbi:endpoint:serviceNamespace[sep]serviceName[sep]endpointName jbi:name:endpointName The separator used will be: '/' if the namespace looks like 'http://' ':' if the namespace looks like 'urn:foo:bar' For more details of valid JBI URIs see the ServiceMix URI Guide. Using the jbi:service: or jbi:endpoint: URI forms will set the service QName on the JBI endpoint to the exact one you give. Otherwise the default Camel JBI Service QName will be used which is {http://activemq.apache.org/camel/schema/jbi}endpoint Examples jbi:service:http://foo.bar.org/MyService jbi:endpoint:urn:foo:bar:MyService:MyEndpoint jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint jbi:name:cheese URI options Name Default value Description mep <MEP of Camel Exchange> Allows users to override the MEP being used for interacting with JBI (values are in-only, in-out, robust-in-out and in-optional-out) operation <value of the jbi.operation header property> Specify the JBI operation to be used for the MessageExchange. If no value is supplied, the JBI binding will use the value of the jbi.operation header property Examples 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) Using Stream bodies If you are using any stream types as bodies then you should be aware that a stream is only capable of being read once. So if you are enabling DEBUG logging then the body is usually debug logged and thus read. To cater for this Camel has streamCaching that caches the stream is it can be read multiple times. from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething"); In Camel 1.5 onwards the stream caching is default enabled, so adding streamCaching() is not needed. In Camel 2.0 we are storing the big (over than 64K by default) input stream into to a temp file by using CachedOutputStream(TODO need to add the java doc link), and when you close the input stream , the temp file will be deleted. Creating a JBI Service Unit If you have some Camel routes you want to deploy inside JBI as a Service Unit you can use the JBI Service Unit Archetype to create a new project. If you have an existing maven project which you need to convert into a JBI Service Unit you may want to refer to the ServiceMix Maven JBI Plugins for further help. Basically you just need to make sure you have a spring XML file at src/main/resources/camel-context.xml which is used to boot up your routes inside the JBI Service Unit you change the pom's packaging to jbi-service-unit Your pom.xml should look something like this to enable the jbi-service-unit packaging. <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>myGroupId</groupId> <artifactId>myArtifactId</artifactId> <packaging>jbi-service-unit</packaging> <version>1.0-SNAPSHOT</version> <name>A Camel based JBI Service Unit</name> <url>http://www.myorganization.org</url> <properties> <camel-version>1.0.0</camel-version> <servicemix-version>3.3</servicemix-version> </properties> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-jbi</artifactId> <version>${camel-version}</version> </dependency> <dependency> <groupId>org.apache.servicemix</groupId> <artifactId>servicemix-core</artifactId> <version>${servicemix-version}</version> <scope>provided</scope> </dependency> </dependencies> <build> <defaultGoal>install</defaultGoal> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> <!-- creates the JBI deployment unit --> <plugin> <groupId>org.apache.servicemix.tooling</groupId> <artifactId>jbi-maven-plugin</artifactId> <version>${servicemix-version}</version> <extensions>true</extensions> </plugin> </plugins> </build> </project> See Also Configuring Camel Component Endpoint Getting Started ServiceMix Camel module Using Camel with ServiceMix Cookbook on using Camel with ServiceMix

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences