On 7/25/07, smx_ <[EMAIL PROTECTED]> wrote:
services have to use servicemix to communicate with each other and with client app.
If you need the multiple services to talk to one another within the scope of a single request and you'd like to use ServiceMix, then it sounds to me like you're starting to touch upon requirements for some kind of orchestration. This can be handled in many ways including POJOs using the servicemix-bean component, scripting using the servicemix-script component, Drools rules using the servicemix-drools component, BPEL using the Apache Ode service engine (http://incubator.apache.org/ode/user-guide.html#UserGuide-InJBI), etc. But again, what are you trying to achieve that the Tomcat-only solution does not currently handle? I.e., what features of ServiceMix are of interest to you within your architecture? The other option, of course, is to develp the web services to be run from inside the ServiceMix ESB. This can be accomplished using the servicemix-jsr181 component using either a contract-first paradigm where the WSDL is developed first or an annotated POJOs paradigm where Java 1.5 annotations from the JSR181 spec are used. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/
