-
1. Re: SOAP provider
tfennelly Sep 12, 2007 10:28 AM (in response to rukus)What have you read?
What do you not understand?
Have you tried the any of the quickstarts? -
2. Re: SOAP provider
rukus Sep 12, 2007 10:50 AM (in response to rukus)"tfennelly" wrote:
What have you read?
What do you not understand?
Have you tried the any of the quickstarts?
Read:
How to define custom provider? (and JCA-adapters)
ProgrammersGuide.pdf
AdministrationGuide.pdf
Quickstarts:
webservice_*
Not understand:
Is SOAP provider already implemented? (if no: how i can implement it? or i simply need to define custom WS and in it's body put messages to ESB? ) -
3. Re: SOAP provider
tfennelly Sep 12, 2007 11:02 AM (in response to rukus)Please check here and let us know if this info is not helping you (and how it's not helping - more details of your usecase etc). This same info is available in the programmers guide.
-
4. Re: SOAP provider
burrsutter Sep 12, 2007 11:40 AM (in response to rukus)quickstart webservice_producer provides an easy to understand example of how to mediate a web service endpoint via the ESB.
Now, you might indicate that this example isn't easy enough to understand and we'll try to correct it. :-) Can you review that example and then ask specific questions?
Also, download the jbossesb-server edition as that has everything preconfigured and ready to run.
Burr -
5. Re: SOAP provider
rukus Sep 13, 2007 7:41 AM (in response to rukus)"burrsutter" wrote:
quickstart webservice_producer provides an easy to understand example of how to mediate a web service endpoint via the ESB.
Now, you might indicate that this example isn't easy enough to understand and we'll try to correct it. :-) Can you review that example and then ask specific questions?
Also, download the jbossesb-server edition as that has everything preconfigured and ready to run.
Burr
Thanks for your answer
I looked at this example and i think this is not my case: I need to make _external_ call (from some self-made application) to webservice and parameters passed to web service then puts to ESB queue -
6. Re: SOAP provider
burrsutter Sep 13, 2007 7:50 AM (in response to rukus)In that case the quickstart native_client illustrates this. It shows a plain 181 WS that in turn uses the ServiceInvoker to natively interact with a JMS-based ESB service.
There is no client code in that quickstart and I believe the readme.txt still suggests soapui for the testing.
So you have the following:
Some WS Client (e.g. VB) -> WS Service -> ESB Service
the native_client assumes you are running the WS on the App Server/ESB Server. Is that the case? -
7. Re: SOAP provider
rukus Sep 13, 2007 7:55 AM (in response to rukus)there is sequence diagram
[img]http://i.piccy.kiev.ua/i/a3/e6/fd4a9733d8805b9ddc8963086bd7.jpeg[/img] -
8. Re: SOAP provider
rukus Sep 13, 2007 8:02 AM (in response to rukus)"burrsutter" wrote:
In that case the quickstart native_client illustrates this. It shows a plain 181 WS that in turn uses the ServiceInvoker to natively interact with a JMS-based ESB service.
There is no client code in that quickstart and I believe the readme.txt still suggests soapui for the testing.
So you have the following:
Some WS Client (e.g. VB) -> WS Service -> ESB Service
the native_client assumes you are running the WS on the App Server/ESB Server. Is that the case?
yes - you understand right - thanks