Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

Page 1   2   3  
org.apache.axis.attachments.* (21)org.apache.axis.client.* (14)org.apache.axis.collections.* (2)
org.apache.axis.components.* (49)org.apache.axis.configuration.* (12)org.apache.axis.constants.* (4)
org.apache.axis.deployment.* (36)org.apache.axis.description.* (9)org.apache.axis.encoding.* (124)
org.apache.axis.enum.* (4)

org.apache.axis: Javadoc index of package org.apache.axis.


Package Samples:

org.apache.axis.attachments
org.apache.axis.client
org.apache.axis.client.async
org.apache.axis.collections
org.apache.axis.components.compiler
org.apache.axis.components.encoding
org.apache.axis.components.image
org.apache.axis.components.jms
org.apache.axis.components.logger
org.apache.axis.components.net
org.apache.axis.components.script
org.apache.axis.components.threadpool
org.apache.axis.components.uuid
org.apache.axis.configuration
org.apache.axis.deployment.wsdd.providers
org.apache.axis.deployment.wsdd
org.apache.axis.description
org.apache.axis.encoding
org.apache.axis.encoding.ser
org.apache.axis.encoding.ser.castor

Classes:

JavaClassWriter: Emitter knows about WSDL writers, one each for PortType, Binding, Service, Definition, Type. But for some of these WSDL types, Wsdl2java generates multiple files. Each of these files has a corresponding writer that extends JavaWriter. So the Java WSDL writers (JavaPortTypeWriter, JavaBindingWriter, etc.) each calls a file writer (JavaStubWriter, JavaSkelWriter, etc.) for each file that that WSDL generates. For example, when Emitter calls JavaWriterFactory for a Binding Writer, it returns a JavaBindingWriter. JavaBindingWriter, in turn, contains a JavaStubWriter, JavaSkelWriter, and JavaImplWriter ...
TypeMappingRegistryImpl: The TypeMappingRegistry keeps track of the individual TypeMappings. The TypeMappingRegistry for axis contains a default type mapping that is set for either SOAP 1.1 or SOAP 1.2 The default type mapping is a singleton used for the entire runtime and should not have anything new registered in it. Instead the new TypeMappings for the deploy and service are made in a separate TypeMapping which is identified by the soap encoding. These new TypeMappings delegate back to the default type mapping when information is not found. So logically we have: TMR | | | +---------------> DefaultTM | ^ | | +----> TM ...
JavaWriter: Emitter knows about WSDL writers, one each for PortType, Binding, Service, Definition, Type. But for some of these WSDL types, Wsdl2java generates multiple files. Each of these files has a corresponding writer that extends JavaWriter. So the Java WSDL writers (JavaPortTypeWriter, JavaBindingWriter, etc.) each calls a file writer (JavaStubWriter, JavaSkelWriter, etc.) for each file that that WSDL generates. For example, when Emitter calls JavaWriterFactory for a Binding Writer, it returns a JavaBindingWriter. JavaBindingWriter, in turn, contains a JavaStubWriter, JavaSkelWriter, and JavaImplWriter ...
DimeDelimitedInputStream: This class takes the input stream and turns it multiple streams. DIME version 0 format 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --- | VERSION |B|E|C| TYPE_T| OPT_T | OPTIONS_LENGTH | A +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ID_LENGTH | TYPE_LENGTH | Always present 12 bytes +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ even on chunked data. | DATA_LENGTH | V +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --- | / / OPTIONS + PADDING / ...
TypeEntry: This class represents a wsdl types entry that is supported by the WSDL2Java emitter. A TypeEntry has a QName representing its XML name and a name, which in the WSDL2Java back end is its full java name. The TypeEntry may also have a Node, which locates the definition of the emit type in the xml. A TypeEntry object extends SymTabEntry and is built by the SymbolTable class for each supported root complexType, simpleType, and elements that are defined or encountered. SymTabEntry | TypeEntry / \ Type Element | | (BaseType, (DefinedElement, CollectionType CollectionElement, DefinedType, UndefinedElement) ...
SimpleSessionHandler: This handler uses SOAP headers to do simple session management. Essentially, you install it on both the request and response chains of your service, on both the client and the server side. ON THE SERVER: The REQUEST is checked for a session ID header. If present, we look up the correct SimpleSession. If not, we create a new session. In either case, we install the session into the MessageContext, and put its ID in the SESSION_ID property. The RESPONSE gets a session ID header tacked on, assuming we found a SESSION_ID property in the MessageContext. ON THE CLIENT: The RESPONSE messages are checked ...
RB: CURRENTLY NOT USED KEEPING FOR REFERENCE 9/19/2002 Wrapper class for resource bundles. Property files are used to store resource strings, which are the only types of resources available. Property files can inherit properties from other files so that a base property file can be used and a small number of properties can be over-ridden by another property file. For example you may create an english version of a resource file named "resource.properties". You then decide that the British English version of all of the properties except one are the same, so there is no need to redefine all of the properties ...
URI: Axis Note: This class was 'borrowed' from Xerces 2: org.apache.xerces.util.URI.java, version 1.22 A class to represent a Uniform Resource Identifier (URI). This class is designed to handle the parsing of URIs and provide access to the various components (scheme, host, port, userinfo, path, query string and fragment) that may constitute a URI. Parsing of a URI specification is done according to the URI syntax described in RFC 2396 , and amended by RFC 2732 . Every absolute URI consists of a scheme, followed by a colon (':'), followed by a scheme-specific part. For URIs that follow the "generic URI" ...
Style: Description of the different styles style=rpc, use=encoded First element of the SOAP body is the operation. The operation contains elements describing the parameters, which are serialized as encoded (possibly multi-ref) <soap:body> <operation> <arg1>...</arg1> <arg2>...</arg2> </operation> style=RPC, use=literal First element of the SOAP body is the operation. The operation contains elements describing the parameters, which are serialized as encoded (no multi-ref)\ <soap:body> <operation> <arg1>...</arg1> <arg2>...</arg2> ...
Wsdl2javaAntTask: Create Java classes from local or remote WSDL. Mappings from namespaces to packages can be provided as nested <mapping> elements. Proxy settings are taken from the java runtime settings of http.ProxyHost, http.ProxyPort, etc. The Ant task <setProxy> can set these. As well as the nested mapping elements, this task uses the file NStoPkg.properties in the project base directory for namespace mapping This task does no dependency checking; files are generated whether they need to be or not. The exception to this is the Impl class, which is not overwritten if it exists. This is a safety measure. ...
Call: Axis' JAXRPC Dynamic Invocation Interface implementation of the Call interface. This class should be used to actually invoke the Web Service. It can be prefilled by a WSDL document (on the constructor to the Service object) or you can fill in the data yourself. Standard properties defined by in JAX-RPC's javax..xml.rpc.Call interface: USERNAME_PROPERTY - User name for authentication PASSWORD_PROPERTY - Password for authentication SESSION_PROPERTY - Participate in a session with the endpoint? OPERATION_STYLE_PROPERTY - "rpc" or "document" SOAPACTION_USE_PROPERTY - Should SOAPAction be used? SOAPACTION_URI_PROPERTY ...
AxisProperties: Configuration properties for AXIS. Manage configuration properties according to a secure scheme similar to that used by classloaders: ClassLoader s are organized in a tree hierarchy. each ClassLoader has a reference to a parent ClassLoader . the root of the tree is the bootstrap ClassLoader er. the youngest decendent is the thread context class loader. properties are bound to a ClassLoader instance non-default properties bound to a parent ClassLoader instance take precedence over all properties of the same name bound to any decendent. Just to confuse the issue, this is the default case. default ...
ProjectResourceBundle: Wrapper class for resource bundles. Property files are used to store resource strings, which are the only types of resources available. Property files can inherit properties from other files so that a base property file can be used and a small number of properties can be over-ridden by another property file. For example you may create an english version of a resource file named "resource.properties". You then decide that the British English version of all of the properties except one are the same, so there is no need to redefine all of the properties in "resource_en_GB", just the one that is different. ...
ForeachTask: Call a target foreach entry in a set of parameters based on a fileset. For Axis development; there is no support or stability associated with this task <target name="target1"> <foreach target="target2"> <param name="param1"> <fileset refid="fset1"/> </param> <param name="param2"> <item value="jar" /> <item value="zip" /> </param> </foreach> </target> <target name="target2"> <echo message="prop is ${param1}.${param2}" /> </target> ...
ByteArrayOutputStream: This class implements an output stream in which the data is written into a byte array. The buffer automatically grows as data is written to it. The data can be retrieved using toByteArray() and toString() . Closing a ByteArrayOutputStream has no effect. The methods in this class can be called after the stream has been closed without generating an IOException . This is an alternative implementation of the java.io.ByteArrayOutputStream class. The original implementation only allocates 32 bytes at the beginning. As this class is designed for heavy duty it starts at 1024 bytes. In contrast to the original ...
SequencedHashMap: A map of objects whose mapping entries are sequenced based on the order in which they were added. This data structure has fast O(1) search time, deletion time, and insertion time. Although this map is sequenced, it cannot implement java.util.List because of incompatible interface definitions. The remove methods in List and Map have different return values (see: List.remove(Object) > List.remove(Object) 55 and Map.remove(Object) > Map.remove(Object) 55 ). This class is not thread safe. When a thread safe implementation is required, use Collections.synchronizedMap(Map) > Collections.synchronizedMap(Map) ...
JavaBuildFileWriter: This is Wsdl2java's build file Writer. It writes the build.xml file. The build.xml file is a ant build file. After run the WSDL2Java and filling the implementation the user just have to cd to the out dir and type and "ant" (of course you must have ant installed). Then the ant will genarate a jar file which named after the wsdl file you used for WSDL2Java. (named after wsdl file ??? I do not get anything better .. the wsdl file may have more than one service ect ... so we can use them.) This build file work on the where it is created ... User can not move the genarated code to another mechine and ...
TypeMappingImpl: This is the implementation of the axis TypeMapping interface (which extends the JAX-RPC TypeMapping interface). A TypeMapping is obtained from the singleton TypeMappingRegistry using the namespace of the webservice. The TypeMapping contains the tuples {Java type, SerializerFactory, DeserializerFactory, Type QName) So if you have a Web Service with the namespace "XYZ", you call the TypeMappingRegistry.getTypeMapping("XYZ"). The wsdl in your web service will use a number of types. The tuple information for each of these will be accessed via the TypeMapping. Because every web service uses the soap, ...
NSStack: The abstraction this class provides is a push down stack of variable length frames of prefix to namespace mappings. Used for keeping track of what namespaces are active at any given point as an XML document is traversed or produced. From a performance point of view, this data will both be modified frequently (at a minimum, there will be one push and pop per XML element processed), and scanned frequently (many of the "good" mappings will be at the bottom of the stack). The one saving grace is that the expected maximum cardinalities of the number of frames and the number of total mappings is only ...
DefaultTypeMappingImpl: This is the implementation of the axis Default TypeMapping (which extends the JAX-RPC TypeMapping interface) for SOAP 1.1. A TypeMapping contains tuples as follows: {Java type, SerializerFactory, DeserializerFactory, Type QName) In other words, it serves to map Java types to and from XML types using particular Serializers/Deserializers. Each TypeMapping is associated with one or more encodingStyle URIs. The wsdl in your web service will use a number of types. The tuple information for each of these will be accessed via the TypeMapping. This TypeMapping is the "default" one, which includes all the ...
SOAPMonitorService: This is a SOAP Monitor Service class. During the HTTP server startup, the servlet init method is invoked. This allows the code to open a server socket that will be used to communicate with running applets. When an HTTP GET request is received, the servlet dynamically produces an HTML document to load the SOAP monitor applet and supply the port number being used by the server socket (so the applet will know how to connect back to the server). Each time a socket connection is established, a new thread is created to handle communications from the applet. The publishMethod routine is invoked by the ...
Deserializer: This interface describes the AXIS Deserializer. A compliant implementiation must extend either the AXIS SoapHandler (org.apache.axis.message.SOAPHandler) or the AXIS DeserializerImpl (org.apache.axis.encoding.DeserializerImpl) The DeserializerImpl provides a lot of the default behavior including the support for id/href. So you may want to try extending it as opposed to extending SoapHandler. An Axis compliant Deserializer must provide one or more of the following methods: public <constructor>(Class javaType, QName xmlType) public <constructo>() This will allow for construction of generic ...
MessageContext: A MessageContext is the Axis implementation of the javax SOAPMessageContext class, and is core to message processing in handlers and other parts of the system. This class also contains constants for accessing some well-known properties. Using a hierarchical namespace is strongly suggested in order to lower the chance for conflicts. (These constants should be viewed as an explicit list of well known and widely used context keys, there's nothing wrong with directly using the key strings. This is the reason for the hierarchical constant namespace. Actually I think we might just list the keys in the ...
KeyedBuffer: A KeyedBuffer is a low level hybrid FIFO Queue and Keyed map Each MessageExchange implementation will create at least two KeyedBuffer's, one for messages being sent, and another for messages that have been received. KeyedBuffers differ from traditional FIFO Queues in that elements put in are keyed and can be taken out of order. Different implementations may allow for variations on how the KeyedBuffer model is implemented. For instance, the code will ship with a NonPersistentKeyedBuffer that will store all contained objects in memory. The fact that everything is stored in memory means that the buffer ...
LRUMap: An implementation of a Map which has a maximum size and uses a Least Recently Used algorithm to remove items from the Map when the maximum size is reached and new items are added. A synchronized version can be obtained with: Collections.synchronizedMap( theMapToSynchronize ) If it will be accessed by multiple threads, you _must_ synchronize access to this Map. Even concurrent get(Object) operations produce indeterminate behaviour. Unlike the Collections 1.0 version, this version of LRUMap does use a true LRU algorithm. The keys for all gets and puts are moved to the front of the list. LRUMap is ...

Home | Contact Us | Privacy Policy | Terms of Service