To dynamically generate a web service from a component requires knowledge on the language and the platform of the component. There are various tools and technologies available to create web services. The component functionalities may be converted into a web service based on the language and features of the language in which the component appropriate tool or depends on the nature of the component and the A web technology must be used to generate a web service dynamically. Dynamic generation of web service is to be dynamically created for the component desired by the client. This is shown in Figure 4.

When the component is selected, the main web service can create a dynamic web service using the component DLL. Then the address or WSDL file of this newly created web service can be given back to the client. When the client is done with the method calls, it can either send message to the consumer web service or the dynamic web service to terminate the web service. Thus the web service is created, used and then deleted as and when required by the client.

This would take the load off the consumer web service.. Web services can be developed in any language and used by programs written in any language or platform. All the client needs is a valid WSDL file.

While the development and deployment of Web Services does not require an underlying technology platform, two different Web service architectureMicrosoft’s .NET and Sun Microsystems’ J2EE are competing head to head to become the platform of choice for Web Services developers. Although, Web Services technology is platform-neutral, each camp provides specific development tools and APIs. J2EE is and open standard, but there are several competing J2EE development environments including JBoss+Tomcat, BEA WebLogic, WebSphere, and Sybase EAServer. Over the years, the goal of achieving software interoperability across computer networks has become elusive.

Standards such as Common Object Request Broker Architecture (CORBA) and the Distributed Component Object Model (DCOM) have met with marginal success. With the strong support provided by most major market players, Web services may achieve what CORBA or DCOM could not. The XML/SOAP approach offers some significant advantages over CORBA and DCOM. Web services use documentation style messages that offer the flexibility and pervasiveness that CORBA and DCOM cannot provide.

Implementation

The implementation of dynamically deploying Java components on a web server has been effectively completed in this research using the features of Apache SOAP . The steps are shown in Figure 5. A deployment descriptor is created using Apache SOAP for the component to be converted into a web service. This is an XML file that describes the component functionality as a web service. The service is deployed on the web server using Apache SOAP.

It is the most advanced, standards-compliant development and deployment environment for creating and consuming secure Web services in C and C++ applications. WASP Server guaranteed to interoperate with a broad range of SOAP implementations, including Microsoft .NET, J2EE servers, Apache AXIS, and others. [7] The steps in the conversion of a UML component into a web service using the WASP toolkit is shown in Figure 6. A WSDL Compiler generates the stubs and skeletons are used in the creation of a web service as in Figure 7. The service is implemented using the WASP compiler and configured to be deployed on the web server.