Re: jsp client for axis2 webservice
cod3nam3 <shakhnovskiy.i...@googlemail.com> wrote:
Andrew Thompson wrote:
...decrease your chances of getting meaningful
replies by multi-posting?
Please refrain from multi-posting.
Cross-posting (X-post), as I have done, is
always preferable.
(N.B. X-post to c.l.j.programmer/help,
with follow-ups set to c.l.j.help only)
cod3nam3 <shakhnovskiy.i...@googlemail.com> wrote:
... write a jsp [sic] client for an axis2 web service.
The web service is already up and running, so the wsdl [sic] is already
created by axis2 automatically. I still don't know how to create a jsp [sic]
client, which would just call a axis2 web service function. I would
really appreciate ur [sic] help.
The client has nothing to do with Axis, so you can ignore Chris ( Val )'s rant
entirely.
What exactly do you mean by a "JSP client"? A SOAP-based web service is not
for human consumption; it uses automatic exchanges. What you need is to have
your JSP call some logic, presumably in the web application to which it POSTs,
which logic in turn generates the XML / SOAP message to the web service and
parses the response.
The flow is:
(client-side)
web-page submit
-> (server-side)
controller servlet receives request
-> controller servlet passes request data to service logic
-> service logic parses the request
-> adds data to web service client, logic
(still on the server side of the web app, though)
-> sends message to web service
-> retrieves response from web service
-> parses response back into web app object model
(still server side)
-> forwards to new view JSP
-> web-app container generates new view JSP
-> server sends web page to client for display
(now we're back on the client side)
The web-service client on the web-app server side can be generated by a
variety of tools directly from the WSDL. See WSDL2Java, for example.
--
Lew