Alternative registry lookup of web services
First Claim
1. A computer implemented method in a data processing system to identify a Web service in a registry using a registry lookup naming and directory provider, the computer implemented method comprising:
- detecting a request from a service requester to identify the Web service in the registry;
responsive to detecting the request, determining if a first element is present in a registry file;
responsive to determining the first element is present in the registry file, locating a second element in the registry file based on the first element in the registry file;
locating an endpoint location of the Web service based on the second element in the registry file;
retrieving an instance of the Web service based on the endpoint location;
returning the instance of the Web service to the service requester;
responsive to determining that the first element is absent from the registry file, deferring identification of the Web service to a standard naming and directory provider and passing the request to the standard naming and directory provider;
locating an additional configuration file;
responsive to determining that the first element is absent from the registry file, determining whether the first element is present in the additional configuration file;
responsive to determining the first element is present in the additional configuration file, locating the endpoint location identified by the first element in the additional configuration file; and
returning the endpoint location to the service requester.
2 Assignments
0 Petitions
Accused Products
Abstract
An alternative registry lookup Java naming and directory interface (JNDI) provider is used to lookup a service endpoint in a registry of a Web service. The alternative registry lookup JNDI provider examines the new registry file for a service-ref-name element and determines if the element is present. If the element is present, the registry lookup JNDI provider retrieves location of the service endpoint using information in the new registry file. If the element is absent, lookup of the service endpoint is deferred to a standard JNDI provider, which determines the location of a service endpoint based on a Web Services Description Language (WSDL) file.
-
Citations
10 Claims
-
1. A computer implemented method in a data processing system to identify a Web service in a registry using a registry lookup naming and directory provider, the computer implemented method comprising:
-
detecting a request from a service requester to identify the Web service in the registry; responsive to detecting the request, determining if a first element is present in a registry file; responsive to determining the first element is present in the registry file, locating a second element in the registry file based on the first element in the registry file; locating an endpoint location of the Web service based on the second element in the registry file; retrieving an instance of the Web service based on the endpoint location; returning the instance of the Web service to the service requester; responsive to determining that the first element is absent from the registry file, deferring identification of the Web service to a standard naming and directory provider and passing the request to the standard naming and directory provider; locating an additional configuration file; responsive to determining that the first element is absent from the registry file, determining whether the first element is present in the additional configuration file; responsive to determining the first element is present in the additional configuration file, locating the endpoint location identified by the first element in the additional configuration file; and returning the endpoint location to the service requester. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
Specification