Reji,
I followed the report incident tutorial and that was the reason. I also
thought to redesign this by using cxf endpoints. After i faced with the
mentioned error, İ thought that was better idea. Additionally, this will
bring me possibility to use placeholders for this endpoint declaration as
well so i might generate cxf web services automatically. Thank you both,
this hints reminded me for the design review and saved my hours.
Best regards
Ercan

21 Nisan 2015 Salı tarihinde, contactreji [via Camel] <
[email protected]> yazdı:

> 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="url"
>                         value="<a href="<a href="http://localhost:
> $&quot;">http://localhost:$";><a href="http://localhost:
> $">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
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/HTTP-operation-failed-invoking-statusCode-500-tp5766085p5766116.html
>  To unsubscribe from HTTP operation failed invoking statusCode: 500, click
> here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5766085&code=ZXJjYW4uY2FubGllckBnbWFpbC5jb218NTc2NjA4NXwxNjM0MzU3MDUy>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


-- 
Ercan CANLIER




--
View this message in context: 
http://camel.465427.n5.nabble.com/HTTP-operation-failed-invoking-statusCode-500-tp5766085p5766121.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to