Hi raul, first of all thanks for ur response to my post. And after going
through your response it helped for looking into so many things.

And i am trying to create sample prototype looks like:
     
      Application X ----> Http SU ----> Camel - SU ----> Application Y

Here are my xbean.xml file for Http SU:

<beans xmlns:http="http://servicemix.apache.org/http/1.0";
       xmlns:hello="/home/sreddy/servicemix-sample-examples/sample-camel">

  <http:endpoint service="hello:Myendpoint"
                 endpoint="soap"
                 role="consumer" 
                 locationURI="http://localhost:8192/Myexample";
                 defaultMep="http://www.w3.org/2004/08/wsdl/in-only";
                 soap="true" />             
</beans>

Note : xmlns:hello="/home/sreddy/servicemix-sample-examples/sample-camel"
can i mention in this way? 

 
camel-context.xml file for Camel-SU:

<beans xmlns="http://www.springframework.org/schema/beans";
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
       xsi:schemaLocation="
       http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
       http://activemq.apache.org/camel/schema/spring
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd
    ">
  <camelContext id="camel" 
                                
xmlns="http://activemq.apache.org/camel/schema/spring";>
    <route>
      <from uri="jbi:Myendpoint"/>
      <to uri="jbi:service:http://localhost:8080/webapp/control/myService"/>
    </route>
    </camelContext>
</beans>

I don't know where actually i am making some thing wrong because compilation
process is doing fine.But while loading this camel.zip file to hotdeploy,
then actually giving problems.

output:

      <loc-message>org.apache.camel.RuntimeCamelException:
java.lang.IllegalArgumentException: Expected syntax
jbi:endpoint:[serviceNamespace][sep][serviceName][sep][endpointName] or
jbi:service:[serviceNamespace][sep][serviceName or jbi:name:[endpointName]
but was given: Myendpoint</loc-message>
                                       
<stack-trace><![CDATA[org.apache.xbean.kernel.ServiceRegistrationException:
org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
Expected syntax
jbi:endpoint:[serviceNamespace][sep][serviceName][sep][endpointName] or
jbi:service:[serviceNamespace][sep][serviceName or jbi:name:[endpointName]
but was given: Myendpoint
        at
org.apache.xbean.kernel.standard.ServiceManagerRegistry.registerService(ServiceManagerRegistry.java:424)
        at
org.apache.xbean.kernel.standard.StandardKernel.registerService(StandardKernel.java:220)
        at
org.apache.xbean.server.spring.loader.SpringLoader.load(SpringLoader.java:152)
        at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:83)
        at
org.apache.servicemix.camel.CamelSpringDeployer.deploy(CamelSpringDeployer.java:79)
        at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
        at
org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
        at
org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentService.java:508)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:350)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:253)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:60)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)


Looking forward for your response......

Regards,
Sandeep.



raulvk wrote:
> 
> Sandeep,
> 
> You should read the documentation on the servicemix-camel component
> (service engine). You can implement content-based routing (if that's
> what you are after) through XML by creating a camel service unit that
> goes packaged up within a service assembly (possibly along with the
> service units that define the interfaces with applications x, y and z).
> 
> Also, you should check out the Camel example provided with the binary
> distribution of ServiceMix.
> 
> Hope that helps to get you started.
> 
> Raul.
> 
> 
> -----Mensaje original-----
> De: sandeep reddy [mailto:[EMAIL PROTECTED] 
> Enviado el: jueves, 17 de abril de 2008 15:13
> Para: [email protected]
> Asunto: Re: How servicemix supports routing mechanisam
> 
> 
> HI ,
> 
>     Is that some thing it is in big scope where i asked or else making
> question went something in wrong format ? So , that i would be making
> question much clear.
> 
> Sandeep.
> 
> 
> sandeep reddy wrote:
>> 
>> Hi everyone,
>>   
>>        Just i started working with servicemix and trying to understand
> the
>> concepts.And i am trying to implement a sample prototype :
>> 
>>              Situvation: Basically I am having 3 applications (x,y,z).
> x
>> application sends a message to servicemix and here servicemix wants to
>> decide to which application (and this application is resided at
> different
>> system) should the message needs to be route dynamically.
>> 
>>         And i want to achieve the above situation using xbean.xml (
> means
>> using SU and SA). And not with using static configuration file
>> (servicemix.xml file).
>> 
>>       Any help for my above situation is greatly appreciated .
>> 
>> Thanks in advance,
>> Sandeep.  
>> 
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/How-servicemix-supports-routing-mechanisam-tp16720
> 987p16744029.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
> 
> 
> 
> ------------------------------------------------------------------
> This e-mail and the documents attached are confidential and intended
> solely
> for the addressee; it may also be privileged. If you receive this e-mail
> in error, please notify the sender immediately and destroy it.
> As its integrity cannot be secured on the Internet, the Atos Origin group
> liability cannot be triggered for the message content. Although the
> sender endeavours to maintain a computer virus-free network, the sender
> does
> not warrant that this transmission is virus-free and will not be liable
> for
> any damages resulting from any virus transmitted.
> 
> Este mensaje y los ficheros adjuntos pueden contener informacion
> confidencial destinada solamente a la(s) persona(s) mencionadas
> anteriormente. Pueden estar protegidos por secreto profesional Si usted
> recibe este correo electronico por error, gracias de informar
> inmediatamente
> al remitente y destruir el mensaje.
> Al no estar asegurada la integridad de este mensaje sobre la red, Atos
> Origin no se hace responsable por su contenido. Su contenido no constituye
> ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita
> por
> ambas partes.
> Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
> no puede garantizar nada al respecto y no sera responsable de cualesquiera
> danos que puedan resultar de una transmision de virus
> ------------------------------------------------------------------
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-servicemix-supports-routing-mechanisam-tp16720987p16823802.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to