The components work with either ServiceMix 3 or 4, so the component sources will only be pointing to a single version to fulfill the API for compilation. We generally keep these pointing at ServiceMix 3 as a least common denominator so there is no need to worry about the SMX 3 dependencies you see. Likewise, the binaries in an SA should also work across SMX 3 or 4 versions. You can either point to trunk for each component or you can find the released code under the tags directory.
Thanks for the info. As you can tell, I'm new to SMX.
Can you point me to where I can get more info as how to develop my own Binding Component? I'm interested in to as this.
Also I compiled one of the components (servicemix-http), how to deploy it?
I simply copied it into the hot deploy directory, it does not work and telling me that
"Requirements not met for JBI artifact in bundle null (servicemix-http). Installation pending. org.apache.servicemix.jbi.dep."
So how to deploy it in SMX4?
Is it via the "ect/org.apache.servicemix.features.cfg" the only way?
Then, is there any script to "install" the component into the run-time?
Ok, figured that out... It is just that I'm too new to SMX
I was using *.installer.zip file to deploy before and it gives me problem.
Then, I switch to drop in *.jar into deploy dir, then thing starts to work.
Glad you got that figured out. Also, probably the best way to learn about developing a binding component is to look at the source for some of the more simple ServiceMix components such as servicemix-file, servicemix-http, etc.