Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:Swordfish Documentation: JAXWS-CLIENTS"
(New page: == Clarification for Swordfish JAX-WS client samples == '''Renat Zubairov wrote:''' ---- <ol> <li> Where to send what to see that current way of deploying JAX-WS clients is working.</li...) |
(→Clarification for Swordfish JAX-WS client samples) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
== Clarification for Swordfish JAX-WS client samples == | == Clarification for Swordfish JAX-WS client samples == | ||
| Line 7: | Line 6: | ||
<ol> | <ol> | ||
<li> Where to send what to see that current way of deploying JAX-WS clients is working.</li> | <li> Where to send what to see that current way of deploying JAX-WS clients is working.</li> | ||
| − | <li> How to reconfigure and what to see WSDL generated form the service as it happening with pure SMX4<li> | + | <li> How to reconfigure and what to see WSDL generated form the service as it happening with pure SMX4</li> |
</ol> | </ol> | ||
| + | |||
| + | '''Volodymyr Zhabiuk answered:''' | ||
| + | |||
| + | org.eclipse.swordfish.samples.http project contains BookingServiceClient class, that sends request to jaxws client deployed inside the Swordfish env. | ||
| + | This project also contains client.html, that may send soap requests via browser<BR> | ||
| + | |||
| + | ---- | ||
| + | <BR> | ||
| + | Regarding "''How to reconfigure and what to see WSDL generated form the service as it happening with pure SMX4?''"<BR> | ||
| + | |||
| + | if the cxf endpoint is deployed into the nmr, we have no ability to see the autogenerated wsdl for the service | ||
| + | |||
| + | We can only provide the wsdl in the declaration of a http consumer endpoint | ||
| + | |||
| + | <http:endpoint service="test:MyProviderService" | ||
| + | endpoint="myProvider" | ||
| + | role="provider" | ||
| + | locationURI="http://localhost:8192/Service/" | ||
| + | wsdlResource="classpath:provider.wsdl" /> | ||
| + | Taken from [http://servicemix.apache.org/servicemix-http.html http://servicemix.apache.org/servicemix-http.html] | ||
| + | |||
| + | |||
| + | In this example [http://servicemix.apache.org/SMX4/cxf-examples.html http://servicemix.apache.org/SMX4/cxf-examples.html] The cxf endpoint is deployed into the http osgi service | ||
| + | |||
| + | It has nothing to do with the ServiceMix NMR | ||
Latest revision as of 09:24, 18 March 2009
Clarification for Swordfish JAX-WS client samples
Renat Zubairov wrote:
- Where to send what to see that current way of deploying JAX-WS clients is working.
- How to reconfigure and what to see WSDL generated form the service as it happening with pure SMX4
Volodymyr Zhabiuk answered:
org.eclipse.swordfish.samples.http project contains BookingServiceClient class, that sends request to jaxws client deployed inside the Swordfish env.
This project also contains client.html, that may send soap requests via browser
Regarding "How to reconfigure and what to see WSDL generated form the service as it happening with pure SMX4?"
if the cxf endpoint is deployed into the nmr, we have no ability to see the autogenerated wsdl for the service
We can only provide the wsdl in the declaration of a http consumer endpoint
<http:endpoint service="test:MyProviderService"
endpoint="myProvider"
role="provider"
locationURI="http://localhost:8192/Service/"
wsdlResource="classpath:provider.wsdl" />
Taken from http://servicemix.apache.org/servicemix-http.html
In this example http://servicemix.apache.org/SMX4/cxf-examples.html The cxf endpoint is deployed into the http osgi service
It has nothing to do with the ServiceMix NMR