Easy response to ws-security specification interoperability challenges, part 4th

Source: Internet
Author: User
Tags requires web services

Easily respond to ws-security specification interoperability challenges, Part 4 Add Java 1.3 provider endpoints to Java EE 1.4 Web service Services

Introduction

This article describes how to implement a new provider endpoint resolution for Ws-security specification level interoperability issues. This approach requires that the Java 1.4 Provider application be packaged with two Web service endpoints: One for Java EE 1.3 Users and another for Java EE 1.4 users. Implementing this workaround is a basic programming and packaging effort that requires no other middleware infrastructure. This approach can be extended well when there are a large number of WEB service consumer applications.

After adding a new provider endpoint to a Web service application, any number of Java EE 1.3 Web service consumer applications can use it. Important: This method is best suited for situations where a WEB service implementation class is a simple JavaBeans or Enterprise JavaBeans (EJB). If the WEB service implementation logic is contained in a Servlet, serviced component Architecture (Service Component Architecture,sca) component, or an enterprise service bus (Enterprise services Bus,esb) Mediation module, It may be more difficult to create a Servlet 2.2 (Java EE 1.3) Web project and package it with a Web service provider application.

Although this workaround introduces another WEB service endpoint that must be protected and managed by the operations team, the work required to implement this method is primarily application development. In addition to application developers, this approach requires the involvement of testers and deployment personnel.

This article assumes that the application developers who implement this approach have basic Java EE and Web service development skills.

This article will use a fully implemented example (available for deployment in your environment) detailing how to implement the new provider endpoint method. This method is described in detail in the solution overview, and the Build Solution section describes the implementation tasks, explaining how the sample application was developed, and using the sample application section to describe how to customize and run the sample application in a run-time environment.

Solution Overview

Figure 1 shows a detailed run-time view of the new provider endpoint resolution. The Java EE 1.3 client application communicates with the Java EE 1.3 Web service using Web services and the Ws-security Draft 13 specification. The Java EE 1.4 client application communicates with the Java EE 1.4 Web service using Web services and the Ws-security V1.0 specification. The Web service endpoint application then instantiates the Java 1.4 Web service class that is included in the shared library, and the latter will call Rmi/iiop on the back-end EJB.

In general, we assume that you are trying to add a new Java EE 1.3 client and provider endpoint to existing Java EE 1.4. The Java EE 1.4 Provider application includes an EJB that contains business logic. In Figure 1, the beige box represents the existing Java EE 1.4 component, and the pink box represents the new component, and this article explains how to create these new components and integrate them with the Java EE 1.4 Provider application EAR file.

Figure 1. New provider Endpoint Solution component

Can't you see the picture clearly? Please click here to view the original image (larger).

Table 1 shows the tasks and products that are required to create this solution.

Table 1. Tasks and products required to create the solution

tasks environment responsible for the role
1. Create Java EE 1.3 Web service endpoints and shared libraries ibm®rat Ional®application Developer application developer
2. Modify Java EE 1.3 Web service endpoint. rational application Developer application Developer
3. Connect shared libraries to Java EE 1.3 and Java EE 1.4 Web service Endpoints. rational application Developer application Developer
4. Connect back-end EJBS to shared libraries, Java EE 1.3, and Java EE 1.4 Web service Endpoints. rational application DeveloPer application developer
5. The guest The household application is integrated with the Java EE 1.3 Web service client. rational application Developer application Developer
6. Add security. rational application Developer application Developer
7. Deploy the solution and unit tests on the runtime environment. IBM websphere®application Server

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.