The SOAP engine implementation used within the Globus Toolkit. See the Apache Axis website for details.

Axis client-side WSDD configuration file. It contains information about the type mappings, the transport and other handlers.

See Also Apache Axis, Web Services Deployment Descriptor (WSDD).

Java Naming and Directory Interface (JNDI) API are used to access a central transient container registry. The registry is mainly used for discovery of the ResourceHome implementations. However, the registry can also be used store and retrieve arbitrary information. The jndi-config.xml files are used to populate the registry. See the JNDI Tutorial for details.

See Also jndi-config.xml, ResourceHome.

It is a XML-based configuration file used to populate the container registry accessible via the JNDI API. See the JNDI details for more information.

See Also JNDI, ResourceHome, XML.

The GAR (Grid Archive) file is a single file which contains all the files and information that the container needs to deploy a service. See GAR details for more information.

A reusable Java component that implements one or more web service functions. A web service can be composed of one or more operation providers. See Operation Provider for more information.

The resources are managed and discovered via ResourceHome implementations. The ResourceHome implementations can also be responsible for creating new resources, performing operations on a set of resources at a time, etc. ResourceHomes are configured in JNDI and are associated with a particular web service.

See Also JNDI.

Axis server-side WSDD configuration file. It contains information about the services, the type mappings and various handlers.

See Also Apache Axis, Web Services Deployment Descriptor (WSDD).

SOAP provides a standard, extensible, composable framework for packaging and exchanging XML messages between a service provider and a service requester. SOAP is independent of the underlying transport protocol, but is most commonly carried on HTTP. See the SOAP specifications for details.

Axis XML-based configuration file.

See Also Apache Axis, client-config.wsdd, server-config.wsdd, XML.

The WS-Addressing specification defines transport-neutral mechanisms to address Web services and messages. Specifically, this specification defines XML elements to identify Web service endpoints and to secure end-to-end endpoint identification in messages. See the W3C WS Addressing Working Group for details.

The WS-Notification family of specifications define a pattern-based approach to allowing Web services to disseminate information to one another. This framework comprises mechanisms for basic notification (WS-Notification), topic-based notification (WS-Topics), and brokered notification (WS-BrokeredNotification). See the OASIS Web Services Notification (WSN) TC for details.

The WS Resource Framework (WSRF) specifications define a generic and open framework for modeling and accessing stateful resources using Web services. This framework comprises mechanisms to describe views on the state (WS-ResourceProperties), to support management of the state through properties associated with the Web service (WS-ResourceLifetime), to describe how these mechanisms are extensible to groups of Web services (WS-ServiceGroup), and to deal with faults (WS-BaseFaults). See the OASIS Web Services Notification (WSRF) TC for details.

WSDL is an XML document for describing Web services. Standardized binding conventions define how to use WSDL in conjunction with SOAP and other messaging substrates. WSDL interfaces can be compiled to generate proxy code that constructs messages and manages communications on behalf of the client application. The proxy automatically maps the XML message structures into native language objects that can be directly manipulated by the application. The proxy frees the developer from having to understand and manipulate XML. See the WSDL 1.1 specification for details.

See Also XML, SOAP.

The WS-I Basic Profile specification is a set of recommendations on how to use the different web services specifications such as SOAP, WSDL, etc. to maximize interoperability.

See Also WSDL, SOAP.

Extensible Markup Language (XML) is standard, flexible, and extensible data format. See the W3C XML site for details.

XPath is a language for finding information in an XML document. XPath is used to navigate through elements and attributes in an XML document. See the XPath specification for details.