Page History

You now have Smix built from source, and the Smix components in a Maven 2 repository. The built distribution of Smix will be in \[Smix_source_folder\]/apache-servicemix/target. There will be a source distribution that is like (exactly like?) the one which you downloaded, and the .zip, .tar.gzip binary distributions. Install the binary distribution following [these|http://servicemix.org/sm30ug/3-installation.html#3.Installation-UnixSourceInstallation] directions. Note those are for Unix, but you can follow the link and find directions for Windows. Once you have installed the binary Servicemix installation you are ready to do some testing.

The first thing to do now is install the [wsdl-first|http://servicemix.org/sm30ug/1-quick-start.html#1.Quickstart-Deployasampleapplication] service assembly (SA) which contains a few service units (SU's) ([See JBI specification document|https://sdlc6a.sun.com/ECom/EComActionServlet;jsessionid=728961EE41294F2FB2547B82D037F02E]). The end result is a XFire based SOAP service which is pretty simple. The actual code for the service is in the file \[Servicemix_binary_distribution_home\]/examples/wsdl-first/wsdl-first-jsr181-su/src/main/java/org/apache/servicemix/samples/wsdl_first/PersonImpl.java. Phew\! Take a look at the code, it is pretty simple. It uses an [annotation|http://java.sun.com/j2se/1.5.0/docs/guide/language/annotations.html] which describes the class as a [jsr181|http://dev2dev.bea.com/webservices/jwsm.html] web service. One interesting thing to note about this project is the use of an ant task inside the parent pom.xml. This taks uses XFire's WsGenTask to create Java objects used by the web service, as described in the WSDL file.

So let's get this up and running in our Smix container. [Start|http://servicemix.org/sm30ug/1-quick-start.html#1.Quickstart-Starttheserver] Smix, watch the output to make sure things start up correctly. You will need to open up a new console for the next step, since the Smix output is taking up the other. You will be able to watch this output to see what is going on in some of the following steps. Go back to \[Servicemix_binary_distribution_home\]. You need to copy the components needed by the wsdl-first SA from the /components folder to the /install folder. The ones you should copy are:

There is an easy way to do the following: copy the file \[Servicemix_binary_distribution_home\]/examples/wsdl-first/wsdl-first-sa-3.0-incubating-SNAPSHOT.zip into the /install folder. Watch the Smix console window making sure things go well. You can now open a browser and go [here|http://localhost:8192/PersonService/main.wsdl] to see the WSDL for the SOAP service.

 That was the easy way....but you want to learn about developing so let's do it the 'hard' way. First go to the \[Servicemix_binary_distribution_home\]/examples/wsdl-first folder and type mvn install. This example project is using a [Maven 2 plugin|http://servicemix.org/site/maven-jbi-plugin.html] for creating specific JBI components. If you look in the module pom.xml files you will see a special packaging type. After the mvn install completes there will be file called wsdl-first-sa-3.0-incubating-SNAPSHOT-installer in the wsdl-first-sa module's target folder. This is SA for the wsdl-first example project. Now we want to deploy this to our container. The Maven JBI plugin will take care of this for us\!\!\! Note we need to make a small change to the wsdl-first-sa module's pom.xml. The plugin will normally try to install all the shared libraries needed by the SA when running the Maven goal jbi:projectDeploy. This is sometimes useful. But often it causes problems because another SA in Smix is using the shared lib already. In this case the Maven goal will try to remove and redeploy the shared lib from Smix. This causes a problem and will make the SA deployment fail. So to tell the plugin to not do this make the following change in the pom.xml: