| Home >> All >> org >> apache >> axis >> [ wsdl Javadoc ] |
| • | org.apache.axis.wsdl.fromJava.* (3) | • | org.apache.axis.wsdl.gen.* (6) |
| • | org.apache.axis.wsdl.symbolTable.* (30) | • | org.apache.axis.wsdl.toJava.* (30) |
• org.apache.axis.wsdl: Javadoc index of package org.apache.axis.wsdl.
Package Samples:
• org.apache.axis.wsdl.fromJava
• org.apache.axis.wsdl.gen
• org.apache.axis.wsdl.symbolTable
• org.apache.axis.wsdl.toJava
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 ...
• 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 ...
• 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) ...
• 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 ...
• Generator: This is the interface for all writers. All writers, very simply, must support a write method. Writer and WriterFactory are part of the Writer framework. Folks who want to use the emitter to generate stuff from WSDL should do 3 things: 1. Write implementations of the Writer interface, one each for PortType, Binding, Service, and Type. These implementations generate the stuff for each of these WSDL types. 2. Write an implementation of the WriterFactory interface that returns instantiations of these Writer implementations as appropriate. 3. Implement a class with a main method (like Wsdl2java) that ...
• SymbolTable: This class represents a table of all of the top-level symbols from a set of WSDL Definitions and DOM Documents: XML types; WSDL messages, portTypes, bindings, and services. This symbolTable contains entries of the form where key is of type QName and value is of type Vector. The Vector's elements are all of the objects that have the given QName. This is necessary since names aren't unique among the WSDL types. message, portType, binding, service, could all have the same QName and are differentiated merely by type. SymbolTable contains type-specific getters to bypass the Vector layer: public PortTypeEntry ...
• GeneratorFactory: Generator and Generatoractory are part of the generator framework. Folks who want to use the emitter to generate stuff from WSDL should do 3 things: 1. Write implementations of the Generator interface, one each fo Message, PortType, Binding, Service, and Type. These implementations generate the stuff for each of these WSDL types. 2. Write an implementation of the GeneratorFactory interface that returns instantiations of these Generator implementations as appropriate. 3. Implement a class with a main method (like WSDL2Java) that instantiates an Emitter and passes it the GeneratorFactory implementation ...
• NamespaceSelector: This class is used within the context of a FactorySpec to express namespaces that should be either included and/or excluded from source code generation. The ability to include/exclude specific namespaces from wsdl2java generation allows certain namespaces to be mapped to custom bean classes, have wsdl-generated stubs/skeletons declared to pass those types, and not have the wsdl2java process generate classes which would conflict with the externally developed custom beans.
• SymTabEntry: SymTabEntry is the base class for all symbol table entries. It contains four things: - a QName - space for a Writer-specific name (for example, in Wsdl2java, this will be the Java name) - isReferenced flag indicating whether this entry is referenced by other entries - dynamicVars; a mechanism for Writers to add additional context information onto entries.
• CollectionType: This Type is for a QName that is a 'collection'. For example, We need a way to indicate in the symbol table that a foo is 'collection of bars', In such cases a collection type is added with the special QName [ , ]
• CollectionElement: This Element is for a QName that is a 'collection'. For example, We need a way to indicate in the symbol table that a foo is 'collection of bars', In such cases a collection element is added with the special QName [ , ]
• FaultInfo: Fault information object. This should probably really be FaultEntry and it should be a subclass of SymTabEntry, but faults aren't first-class objects in WSDL, so I'm not sure what the FaultEntry should contain and how it should be constructed, so for now leave it as a simple object.
• BindingEntry: This class represents a WSDL binding. It encompasses the WSDL4J Binding object so it can reside in the SymbolTable. It also adds a few bits of information that are a nuisance to get from the WSDL4J Binding object: binding type, binding style, input/output/fault body types.
• Types: Description: This class is used to recursively serializes a Java Class into an XML Schema representation. It has utility methods to create a schema node, assosiate namespaces to the various types
• PortTypeEntry: This class represents a WSDL portType. It encompasses the WSDL4J PortType object so it can reside in the SymbolTable. It also adds the parameter information, which is missing from the WSDL4J PortType object.
• DefinedElement: This Type is for a QName that is an element, these types are only emitted if referenced by a ref= or an element=. An element type can be defined inline or it can be defined via a ref/type attribute.
• Emitter: This class emits WSDL from Java classes. It is used by the ?WSDL Axis browser function and Java2WSDL commandline utility. See Java2WSDL and Java2WSDLFactory for more information.
• JavaFaultWriter: This is Wsdl2java's Fault Writer. It writes the .java file. NOTE: This only writes simple type faults, the JavaTypeWriter emits faults that are complex types.
• JavaBindingWriter: This is Wsdl2java's Binding Writer. It writes the following files, as appropriate: Stub.java, Skeleton.java, Impl.java.
• UndefinedElement: This represents a QName found in a reference but is not defined. If the type is later defined, the UndefinedType is replaced with a new Type
• UndefinedType: This represents a QName found in a reference but is not defined. If the type is later defined, the UndefinedType is replaced with a new Type
• JavaImplWriter: This is Wsdl2java's implementation template writer. It writes the Impl.java file which contains the Impl class.
• JavaServiceWriter: This is Wsdl2java's Service Writer. It writes the following files, as appropriate: .java, TestCase.java.
• JavaSkelWriter: This is Wsdl2java's skeleton writer. It writes the Skeleton.java file which contains the Skeleton class.
| Home | Contact Us | Privacy Policy | Terms of Service |