...
No Format |
---|
$ [SMX_HOME]/bin/mvnsmx-arch su http-consumer \ -DgroupId=com.mycompany \ -DartifactId=my-consumer-su |
...
Once the SU is fully configured, it must be packaged. This is easy to do because the project skeleton provides all the necessary project configuration and use of the Maven JBI plugin for you via the pom.xml
file. Simply run the following command while sitting in the my-consumer-su
directory:
No Formatcode |
---|
$ mvn install |
You will need to have Maven 2.0.4 or higher installed in order to run this command. This packages up the SU and places the build artifact in the target directory.
...
Notice that this SU archive contains a META-INF/jbi.xml
file. This was created by the Maven JBI plugin. Below is the pomjbi.xml
file for the project above:
Code Block | ||
---|---|---|
| ||
| ||
$ cat ./target/my-consumer-su-1.0-SNAPSHOT-installer/META-INF/jbi.xml <?xml version="1.0" encoding="UTF-8"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"> <services binding-component="false" xmlns:replaceMe="http://servicemix.apache.org/replaceMe"> <consumes service-name="replaceMe:withYourService" endpoint-name="soap"/> </services> </jbi> |
...
Once the SU is properly packaged, it must be wrapped in a JBI service assembly (SA) before it can be deployed to the JBI container. JBI SAs are described in What is a JBI SA and how do I create one?.
Additional Information
Have you walked through the Tutorials yet? This is a great place to start if you're new to JBI.