THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 'company repository' = a remote Maven 2 repository used within your company to hold dependencies/artifacts.
Wiki Markup Wiki Markup
Note: I am using apache-servicemix-3.0-incubating-20060907.104512-15-src.tar.gz for the following tutorial. If you do not use this snapshot release I cannot guarantee the following will work.
...
| Info | ||||||
|---|---|---|---|---|---|---|
| unmigrated-wiki-markup||||||
If you want to deploy those dependencies to a company repository then keep reading. I can only give information on doing this for Maven 2 as I did not try this for Maven 1. First go into the top level project pom.xml with you favorite editor. This will be in the \ [Smix_source_folder\]/src folder. You are going to first edit out the references to Maven 1. Search for 'm1', or in another case I searched for 'maven-one'. There was a property and a plug in section I deleted (maybe some other sections also). I think the plug in is the important one to delete/coment out. Next edit the 'distributionManagement' section. Put the relevent information for you company repository here. If you are working with a SNAPSHOT release then you will need to put your snapshot repository information in here. You should now be able to 'mvn -Dmaven.test.skip=true deploy' and the dependencies will upload to the remote repository you defined. This is a good thing when people you are working with will need the Smix component dependencies. If others will be working on a Smix project you create it will also come in handy, as they will not have to chase down dependencies. THANKS MAVEN!!! I think there are other benefits too, such as faster fetching since the dependencies are more local (physically). |
Next up install the compiled binary Servicemix...
...
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 the source installation instructions for [Windows|3. Installation#Windows Source Installation] respectively [Unix|3. Installation#Unix Source Installation]. Once you have installed the binary Servicemix installation you are ready to do some testing.
wsdl-first
Wiki Markup
| Info | ||||
|---|---|---|---|---|
| ||||
This example is a good starting place if you are interested in creating a SOAP service in Smix. After reviewing the full code you should have a grasp on creating a simple POJO web service. |
...
So let's get this up and running in our Smix container. [Start|1. Quick start#Start the server] 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:
- servicemix-http-3.0-incubating-SNAPSHOT-installer.zip
- servicemix-shared-3.0-incubating-SNAPSHOT-installer.zip
- servicemix-jsr181-3.0-incubating-SNAPSHOT-installer.zip
With each copied component will come messages from Smix in the console output window. Watch these to make sure things properly install. If any problems crop up, try to copy the component again. I have received a zip related exception before. I did the copy a second time and the problem didn't show itself a second time.unmigrated-wiki-markup
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.
Wiki Markup
| No Format |
|---|
<build>
<plugins>
<plugin>
<groupId>org.apache.servicemix.tooling</groupId>
<artifactId>jbi-maven-plugin</artifactId>
<extensions>true</extensions>
</plugin>
</plugins>
</build>
|
...
That little config change will prevent some headaches later.unmigrated-wiki-markuplater.
You are ready to rock. Change directory to the wsdl-first-sa module. Type 'mvn jbi:projectDeploy'. You can watch the Smix console for information on the deployment.!wsdl-first-install.jpg|align=center!
Betting that all went well you should be ready to test out the web service you deployed into Smix. Lucky for you a nice little web app has been packaged with the application. In your web browser open the file \deployment.
Betting that all went well you should be ready to test out the web service you deployed into Smix. Lucky for you a nice little web app has been packaged with the application. In your web browser open the file [Servicemix_binary_distribution_home\]/examples/wsdl-first/client.html. This static .html page contains a javascript which will try to contact the web service on your local machine. To make it work simply click the 'send' button. If your browser issues any warning make sure you allow the javascript to do what it needs to do. In Firefox I have to 'allow' what it calls an unsafe operation. The results of clicking the 'send' button will be a SOAP response posted into the right hand text area.
Temporary excursion into monitoring
...