Summary

Geronimo provides rich support for the creation and deployment of Web services. The built-in J2EE 1.4 support for JAX-RPC-based Web services allows Web services to be coded in pure Java without XML parsing code. This simplifies the creation of Web services and Web service clients to be hosted in Geronimo.

Web services in Geronimo can be the following:

• A Web-tier servlet that implements the service logic and exposed by Geronimo as Web service

• A business-tier EJB that is exposed as a Web service by Geronimo

In either case, Geronimo will generate the required tie classes and serializer classes dynamically. You will need to supply the following:

1. The JAX-RPC SEI that the service logic (or EJB) implements

2. The WSDL description of the Web service endpoint

3. A JAX-RPC mapping file that describes mapping of WSDL elements

In most cases, these files can be generated directly using tooling such as the SUN JWSDP. Geronimo tooling currently does not generate these files.

Exposure of EJB as CORBA component is also supported by the Geronimo server. No change in the actual EJB coding is required. You can simply create a custom deployment plan with the following:

• <tss-link> element to select the level of CSIv2 server-side security you want

• Create a dependency on the geronimo/j2ee-corba/1.1/car module

The Geronimo application container can be configured to host CORBA clients that access CORBA components via RMI-IIOP. You have configured such a client for the EJB CORBA implementation in this chapter.

Security, such as CORBA’s CSIv2, is a very important pervasive aspect in modern server systems. Geronimo has robust J2EE 1.4 compatible security support built into its architecture. Chapter 15 takes an in-depth look at Geronimo security.