10.  Creating Web Services using e FixIT 

HTTP client

JSP page

JavaBean

M server

HTTP call

setService(...)

* set parameters

process()

RPC call

RPC result

serviceResult

HTTP result

Above is a sequence diagram of a simple e FixIT driven Web Service. The idea is that a web service is a 

component or a composition of components that responds to messages sent from a (HTTP) client. Remote 

Procedure Calls (RPCs) to the M server are made using the WRPCBroker component. The HTTP client 

can be an embedded HTTP component in an another application or a WWW browser, for example. 

10.1  Web Service example 

10.1.1  Example of a Web Service JSP page 

This is an example of a very simple Web Service JSP listing that really does not contain any useful 

functionality. The Web Service's JSP page formats the result into a simple XML document. It should also 

be noted that  this may 

not

 the most effective way to utilize WRPCBroker component in Web services 

connecting to a M server. Such services can be built in many ways and their efficiency varies on several 

variables, such as service utilization  rate  and how much resources (active broker connections to an M 

server in this case) can a Web service allocate. In this example, all the connections to the M server will use 

the same connection channel. See Java FixIT Javadoc documentation for more information about the class 

xfij.webserver.WebServiceBase

 for tuning connection settings. 

This JSP file is used in passing parameters from the client into the actual web service JavaBean component. 

<%@ page info="Web Service JSP Page"%> 

<%=wsBeanId.process()%> 

39