Ercan

Why are you using a separate implementation for invoking real target service
as

    <bean id="realWebService" class="com.gadget.ws.proxy.RealWebServiceBean" 
                init-method="start" destroy-method="stop">
                
                <property name=&quot;url&quot; 
                        value=&quot;&lt;a
href=&quot;http://localhost:$&quot;>http://localhost:${real.port}/webservices/payment";
/>
        </bean>

I would advice on using the CXF framwork itself. It will take care of all
low level stuffs. And I feel nervous seeing the statement  <removeHeaders
pattern="CamelHttp*" /> . You sure u want that to be there?

Http 500 says internal error. As Jiang mentioned, maybe your soap envelop is
missing and you might be sending only the soap body contents. Hence, try
wrapping up your payload with soap envelop and give a try.

Cheers
Reji




-----
Reji Mathews
Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel & 
Jboss Fuse ESB | Mule ESB )
LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
Twitter - reji_mathews
--
View this message in context: 
http://camel.465427.n5.nabble.com/HTTP-operation-failed-invoking-statusCode-500-tp5766085p5766116.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to