Date: Wed, 3 Nov 2004 09:39:10 -0300 (ART)
hello list,
Anne, thanks for your attention.
I have thought about you said and I have made another design.
Before I explain the design, you must know a few application requisites:
-- client module must generate an XML document that implements an XML schema (that defines an own protocol).
-- this XML document must be generated by the webservice requestor that must be installed in the client system.
-- the response is another XML document, but in this case, the XML document is signed by the service provider... and the client module must validate the signature...
"client module" is not very clear what it means but I suppose is located in the end user system who must trust the service certificate.
-- there are a few webservices, each one with his own protocol (xml schema) and each one in a different machine.
well, i have attached a GIF image with 3 possibles solutions.... I dont have this very clear ;) . Diagrams are self-commented.
Could you say me what is the better solution? or at least, what is a reasonable solution?
Again, thanks a lot!!!!
Sergio.
Anne Thomas Manes <anne_at_manes.net> wrote:
v\:* {behavior:url(#default#VML);}o\:* {behavior:url(#default#VML);}w\:* {behavior:url(#default#VML);}.shape {behavior:url(#default#VML);}st1\:*{behavior:url(#default#ieooui) }
The so-called web service “client” in this scenario is, in fact, the JSP/servlet. There’s no reason to use an applet to invoke the service. Most Java SOAP client environments are pretty heavy-weight for an applet. If you really want to use an applet to invoke the service, then I suggest using the Wingfoot SOAP client (see http://www.wingfoot.com).
SOAP messages must be sent to a SOAP server/node rather than routed through a servlet. (Note that a SOAP server runs as a servlet, but not within the servlet that’s communicating with the applet.) The SOAP engine processes the SOAP message and then invokes the appropriate class method to process the request. So there’s only one web service and a corresponding Java application.
Anne
---------------------------------
From: sergio lera [mailto:softlera_at_yahoo.com.ar]
Sent: Tuesday, November 02, 2004 1:07 PM
To: users_at_jax-rpc.dev.java.net
Subject: new webservice architecture
hello list,
Yesterdar I showed a web service design based on JSPs, servlets and webservices, but I forgot an important requisite: the end user (client) MUST contain the java classes that compose the webservice requestor. So, now my design has changed completely.
In the new design, client access a web server (client MUST use a browser to access the service) and load an HTML page with a java applet. The java applet downloads the java classes that compose the webservice requestor and uses the webservice requestor to build a SOAP message. Then, clients send the SOAP message to a servlet. The servlet gets the HTTP message and passes the SOAP message to a SOAP engine. The SOAP engine analizes the SOAP message (the request) and sends it to his corresponding webservice (I have supossed that there are 2 webservices).
--What do you think about this design?it has faults?is it possible to implement it?
--do you think that Jax-RPC can be used here like SOAP engine?
Thanks a lot!!!!
Sergio.
zZz-zZz-zZz-zZz-zZz-zZz-zZz-zZz
throw new Exception("SoftLera!!!");
zZz-zZz-zZz-zZz-zZz-zZz-zZz-zZz
---------------------------------
Ahora podés usar Yahoo! Messenger en tu Unifón, en cualquier momento y lugar.
Encontrá más información aquí.
zZz-zZz-zZz-zZz-zZz-zZz-zZz-zZz
throw new Exception("SoftLera!!!");
zZz-zZz-zZz-zZz-zZz-zZz-zZz-zZz
---------------------------------
Ahora podés usar Yahoo! Messenger en tu Unifón, en cualquier momento y lugar.
Encontrá más información aquí.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
(image/gif attachment: solutions.GIF)