Hi, Can someone tell me why in the following example (http://cwiki.apache.org/CAMEL/better-jms-transport-for-cxf-webservice-using-apache-camel.html) the tags <endpoint>
<endpoint xmlns="http://cxf.apache.org/jaxws" xmlns:customer="http://customerservice.example.com/" id="CustomerService" address="camel://direct:CustomerService" serviceName="customer:CustomerServiceService" endpointName="customer:CustomerServiceEndpoint" implementor="com.example.customerservice.impl.CustomerServiceImpl"> <features> <!-- Enables logging of SOAP messages. --> <logging xmlns="http://cxf.apache.org/core" /> </features> </endpoint> and <client> <client id="CustomerService" xmlns="http://cxf.apache.org/jaxws" xmlns:customer="http://customerservice.example.com/" serviceName="customer:CustomerServiceService" endpointName="customer:CustomerServiceEndpoint" address="camel://direct:CustomerService" serviceClass="com.example.customerservice.CustomerService"> <features> <!-- Enables logging of SOAP messages. --> <!-- <logging xmlns="http://cxf.apache.org/core" /> --> </features> </client> have been used respectively in the config files : - server-applicationContext.xml - client-applicationContext.xml instead of <camel:destination> or <camel:conduit> using the following syntax : <camel:destination name="{http://widgets/widgetvendor.net}widgetSOAPPort.http-destination> <camelContext id="context" xmlns="http://activemq.apache.org/camel/schema/spring"> <route> ... </route> </camelContext> </camel:destination> Charles Moulliard ----- Enterprise Architect Xpectis 12, route d'Esch L-1470 Luxembourg Phone +352 25 10 70 470 Mobile +352 621 45 36 22 e-mail : [EMAIL PROTECTED] web site : www.xpectis.com www.xpectis.com My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://www.nabble.com/Explanation-requested-for-example-%3Ahttp%3A--cwiki.apache.org-CAMEL-better-jms-transport-for-cxf-webservice-using-apache-camel.html-tp19672240s22882p19672240.html Sent from the Camel - Users mailing list archive at Nabble.com.