Hi all, I have begin to implement several SU and SA and some questions through in my mind :) I have made some lookup on the webside and on internet but I haven't really found the complete answer.
Well, that's the questions : 1/ Existing service publication Currently, I have several existing services implemented with EJBs. I would like to "publish" theses services using ServiceMix. For exemple, is it a good way to implement like this : - SU using servicemix-http component (in consumer mode) : this SU listen client requests on HTTP/SOAP - SU using servicemix-jsr181 component : this SU is a proxy to my existing EJB - SU using servicemix-http component (in producer mode) : this SU feedback the service result to the client - SA which package SUs Is this implementation correct or should I use the lightweight mode (with a servicemix.xml file) ? In the case that my existing EJBs don't take "simple" method arguments, should I create a bean to encapsulate the EJB call (for exemple, I have EJBs that take ValueObject (VO) in arguments and not simple scalar types) ? If I have right understood, a SU can have only one target component, so it's not possible to define usage of servicemix-http and service-jsr181 components in the same SU xbean.xml. Correct ? 2/ Create service beans Currently, I have a database stored procedure which performs service. I would like to expose this stored procedure. I need to create a "frontend" bean. Is this implementation correct : - SU using servicemix-http component (in consumer mode) : this SU listen client requests on HTTP/SOAP - SU using servicemix-bean component : Spring implementation bean which call others Spring Beans (like Hibernate DAO) to call my stored procedure - SU using servicemix-jms component : this SU push the stored procedure result to a JMS queue Is this implementation correct ? Is it possible to use a Spring ApplicationContext XML like definition in xbean.xml file ? 3/ Agile services Currently, I create my SAs which define SUs. For exemple, I have provided consumer SU using servicemix-http component. This is correct this time, but for exemple, in the future, a new customer wouldn't call my service using HTTP/SOAP but using JMS. I can do it using servicemix-jms component based SU but I need to rebuild my SA with the new SU consumer. Is it possible to dynamically change an existing SA (by configuration, by JMX or by smx-arch) to avoid to provide a new SA ? 4/ Simplify the ServiceMix and business services delivery To simplify ServiceMix/Business Services delivery and installation to my customers, I would like to pre-package the ESB. I wonder two ways to do it : - I take a default ServiceMix tar.gz and add my SAs in the hot-deploy directory - I create a lightweight mode using servicemix.xml which define my services logic What's the best solution ? Thanks in advance for your feedback. Regards -- Jean-Baptiste Onofré (Nanthrax) BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net [EMAIL PROTECTED] PGP : 17D4F086
