Overview of WebLogic Web Services Architecture

Here is what happens when a client application invokes this type of WebLogic Web Service operation:
-The client application sends a SOAP message request to WebLogic Server over HTTP. Based on the URI in the request, WebLogic Server identifies the Web Service being invoked.
-The Web Service reads the SOAP message request and identifies the operation that it needs to run. The operation corresponds to a method of a stateless session EJB or a Java class, to be invoked in a later step.
-The Web Service converts the operation's parameters in the SOAP message from their XML representation to their Java representation using the appropriate deserializer class. The deserializer class is either one provided by WebLogic Server for built-in data types or a user-created one for non-built-in data types.
-The Web Service invokes the appropriate back-end component method, passing it the Java parameters.
-The Web Service converts the method's return value from Java to XML using the appropriate serializer class, and packages it into a SOAP message response.
-The Web Service sends the SOAP message response back to the client application that invoked the Web Service.