| Home >> All >> org >> apache >> [ wsif Javadoc ] |
• org.apache.wsif: Javadoc index of package org.apache.wsif.
Package Samples:
• org.apache.wsif.providers.jca.toolplugin.myeis.myeis
• org.apache.wsif.base
• org.apache.wsif.compiler.schema.tools
• org.apache.wsif.compiler.schema
• org.apache.wsif.compiler.util
• org.apache.wsif.format.jms
• org.apache.wsif.format
• org.apache.wsif.logging
• org.apache.wsif.naming
• org.apache.wsif.providers.ejb
• org.apache.wsif.providers.java
• org.apache.wsif.providers.jca.toolplugin
• org.apache.wsif.providers.jca
• org.apache.wsif.providers.jms
• org.apache.wsif.providers.soap.apacheaxis
• org.apache.wsif.providers.soap.apachesoap
• org.apache.wsif.providers.soap.soaprmi
• org.apache.wsif.providers
• org.apache.wsif.schema
• org.apache.wsif.spi
Classes:
• WSIFMessage: A WSIFMessage is a an interface representing a WSDL Message. In WSDL, a Message describes the abstract type of the input or output to an operation. This is the corresponding WSIF class which represents in memory the actual input or output of an operation. A WSIFMessage is a container for a set of named parts. The WSIFMessage interface separates the actual representation of the data from the abstract type defined by WSDL. WSIFMessage implementations are free to represent the actual part data in any way that is convenient to them. This could be a simple HashMap as in the WSIFDefaultMessage implementation, ...
• WSIFDynamicProvider_Java: Java specific provider of dynamic WSDL invocations. The WSIF Java Provider allows WSIF to invoke Java classes and JavaBeans. This is designed to allow customers in a 'thin-client' environment such as a JVM or Tomcat test runtime to define 'shortcuts' to local Java code. The Java binding exploits the format binding for type mapping. The format binding allows WSDL to define the mapping between XML Schema types and Java types. The Java provider requires the targeted Java classes to be in the classpath of the client. The Java method is invoked synchronously, in-process, in-thread, with the current ...
• WSIFPluggableProviders: Utility methods for pluggable provider support. A WSIF provider is a class that implements the org.apache.wsif.spi.Provider interface. A Provider is the logic that supports any particular WSDL binding extension. WSIF providers are packaged in JAR files, and use the J2SE 1.3 JAR file extensions to support service providers. A WSIF Provider JAR will contain the following file: META-INF/services/com.ibm.wsif.spi.WSIFProvider This file will contain a list of the class names of the Provider classes in the JAR (which must implement com.ibm.wsif.spi.WSIFProvider). When the first request for a provider ...
• WSIFDynamicProvider_SoapRMI: SoapRMI provider of dynamic WSDL invocations. Limitations of this SoapRMI dynamic port provider (relative to WSDL 1.1 SOAP binding): only rpc style is supported (not document) only HTTP transport is supported only soap:body use 'encoded' is supported (not literal) soap:header is not allowed soap:fault is ignored only first encodingStyle is used from input soap:body (when the space separated list of encoding styles is provided) output soap:body namespaceURI and encodingStyles are ignored first part from output soap:body is used as return value fault processing is not yet implemented - SOAP faults ...
• Trc: Trc provides trace support for WSIF and is a wrapper around commons-logging. It adds value to commons-logging by providing entry/exit/exception trace; never throwing an exception back even if asked to trace something really stupid; and tracing references to large WSDL objects, unless specifically asked to trace out the entire object. Trc also provides brief() methods (called from deep() methods) which trace out WSDL objects (and others) in a consistent and helpful way. The goals of Trc are to not impact performance if trace is off; to provide a rich and easy-to-use API for WSIF; to enable creation ...
• WSIFObjectInputStream: Class FObjectInputStream overloads the class ObjectInputStream to solve the bug reported under BugID 4171142 . If an object contains primitiv data types and you try to serialize/deserialize it than you will get an ClassNotFoundException for the primitiv data type. Reason for this exception is that the ObjectInputStream try to resolve the data type from java.lang.<primitiv> which does not work. The solution for the problem is to override the method resolveClass and to bypass the resolution for primitiv data types.
• WSIFService: A WSIFService is a factory via which WSIFPorts are retrieved. This follows the J2EE design pattern of accessing resources (WSIFPorts, in this case) via a factory which is retrieved from the context in which the application is running. When WSIF is hosted in an app server, the container can manage service invocation details by providing a factory implementation that follows the app servers wishes and guidelines. The factory is assumed to be for a specific portType; i.e., the factory knows how to factor WSIFPorts for a given portType. As such the getPort() methods do not take portType arguments.
• WSIFClientProxy: WSIFClientProxy is a dynamic proxy (or stub) used by the WSIFServiceImpl when the application is using the stubs to invoke the web service. A WSIFClientProxy is created using the static newInstance method. A WSIFClientProxy dynamically implements exactly one interface passed by the application. This class invokes the web service using the WSIFOperation and WSIFPort interfaces and so is independent of any provider implementation. Operation overloading is supported.
• JMS2HTTPBridge: This class implements a JMS to HTTP bridge. That is it takes SOAP messages off of a JMS queue and posts them using HTTP. The SOAP message in the HTTP response is put on a JMS reply queue. This class contains a main method which takes as parameters all the JMS and HTTP information needed. This bridge can be cold or warm started. Cold starting wipes messages off queues on startup, whereas warm starting does not.
• WSIFJMSProperties: WSIFJMSProperties is a HashMap of jms properties. The WSIFJMSProperties can either be IN or OUT. If IN, the properties can only set on a QueueSender. If OUT, the properties can only be got from a message. Reflection is used to set and get the properties in JMS. Using reflection avoids having a table of properties that would have to updated for different JMS implementations and different versions of JMS.
• WSIFPort: A WSIFPort represents the handle by which the operations from the of the of this WSIFPort can be executed. This is an interface which must implemented by specific implementations for the ports. That is, the actual logic is dependent on the binding associated with this port. An interface is used to enable dynamic implementation generation using JDK1.3 dynamic proxy stuff.
• WSIFOperation: A WSIFOperation is a handle on a particular operation of a portType that can be used to invoke web service methods. This interface is implemented by each provider. A WSIFOperation can be created using WSIFPort.createOperation(String) 55 .
• WSIFInterceptor: An interceptor gets the opportunity to pre- or post-process a service request or response, respectively, that's travelling through the WSIF. The interceptor also gets the opportunity to inform WSIF that the service is to be denied; i.e., that the service request (or response) should not be processed further.
• WSIFCorrelationServiceLocator: WSIFCorrelationServiceLocator is a helper class for locating the WSIFCorrelationService. This may either be the WSIF provided WSIFDefaultCorrelationService, or, when running in a managed container the container may provide its own implementation which this will locate by doing a JNDI lookup.
• Import: This class is a default implementation proxy for the Operations of the Import Service. Tooling environments can extend this class and customize its behaviour. It is provided as a default implementation of how to invoke the various operations that are defined in the Import Service archictecture.
• PortTypeArray: The PortTypeArray is the return type, provided by the EIS, in response to the getPortTypes operation of the Import Service. It represents the set of WSDL PortTypes that are available in response to the query string passed into the getPortTypes operation.
• OperationSelection: The OperationSelection class is the representation of a selected Operation that is passed to the getDefinition operation of the ImportService. Tool environments are responsible for constructing instances of this object and passing them to the Import service.
• PortTypeSelection: The PortTypeSelection class is the representation of a selected PortType that is passed to the getDefinition operation of the ImportService. Tool environments are responsible for constructing instances of this object and passing them to the Import service.
• WSIFServiceObjectFactory: This is an object factory which creates: instances of WSIFService from a javax.naming.Reference object representing the service. instances of a service stub object from a javax.naming.Reference object representing the service .
• Parser: A class used for parsing the schema(s) defined in a Definition object. It does not provide full schema parsing. Its main purpose is to help in determining a list off all the types that are defined in schemas either inline in the wsdl document or imported xsd files.
• WSIFFormatHandler_JCA: An interface extending WSIF Format Handler with the Connector Architecture's specific methods from the Streamable interface and a setter for the InteractionSpec field which can be used by a resource adapter, when it is required, to support unmarshalling.
• MIMEHelper: The sole purpose of this class is to collect all the code that uses attachement classes outside of the WSIFOperation_ApacheAxis class so that there is not a runtime requirement on activation.jar and mail.jar unless attachements are actually being used.
• ImportDefinition: This class represents the type returned from the getDefinition operation. The ImportDefinition class contains the WSDL definition of the imported service, along with all necessary XSD types and additional binary resources that are required.
• WSIFJMSFinder: Finds JMS objects. Classes that extend WSIFJMSFinder find the factory and queues either by going directly to an implementation of JMS or by looking them up in JNDI, or by some other means. A WSIFJMSDestination can then be constructed from this finder.
• FormatHandlerGenerator: This interface allows Resource Adapter to provide a code generation contribution to the tool environment. The tooling delegates to the implementation of this interface the generation of all format handlers for the particular encoding and style.
| Home | Contact Us | Privacy Policy | Terms of Service |