| Home >> All >> org >> apache >> [ ws Javadoc ] |
Page 1 2
| • | org.apache.ws.addressing.* (4) | • | org.apache.ws.echosample.* (4) | • | org.apache.ws.eventing.* (23) |
| • | org.apache.ws.jaxme.* (733) | • | org.apache.ws.mows.* (8) | • | org.apache.ws.muws.* (44) |
| • | org.apache.ws.notification.* (71) | • | org.apache.ws.pubsub.* (20) | • | org.apache.ws.resource.* (229) |
| • | org.apache.ws.util.* (78) |
• org.apache.ws: Javadoc index of package org.apache.ws.
Package Samples:
• org.apache.ws.jaxme.xs.xml.impl: Contains schema object model type interfaces for JaxMeXS : the JaxMe parser for XML Schema.
• org.apache.ws.jaxme.js.util: This package contains the JaxMeJS java source generation framework.
• org.apache.ws.jaxme.xs.xml: Contains JaxMeXS : the JaxMe parser for XML Schema.
• org.apache.ws.jaxme.util: Base package for the JaxMe Java-XML binder .
• org.apache.ws.jaxme.xs.parser.impl: Adapters from xml parser mechanisms to the generic schema construction framework.
• org.apache.ws.jaxme.pm.ino.api4j: Specialization of the JaxMe persistence framework for the Tamino datastore.
• org.apache.ws.jaxme.xs.jaxb.impl: Specialization of the JaxMeXS parser for XML Schema for the needs of JAXB.
• org.apache.ws.jaxme.generator.util: This package contains JaxMe specific source generators.
• org.apache.ws.jaxme.generator.sg.impl.ccsg: Contains JAXB source generation model implementation.
• org.apache.ws.jaxme.sqls.oracle: Contains the generic framework for SQL generators.
• org.apache.ws.jaxme.generator.sg.impl: Contains JAXB source generation model interfaces.
• org.apache.ws.jaxme.examples.misc.address
• org.apache.ws.jaxme.generator.impl
• org.apache.ws.jaxme.generator.sg
• org.apache.ws.jaxme.generator.types
• org.apache.ws.jaxme.generator
• org.apache.ws.jaxme.impl
• org.apache.ws.jaxme.junit
• org.apache.ws.jaxme
• org.apache.ws.jaxme.js.impl
Classes:
• XJCTask: An Ant task for running JaxMe, designed to be JAXB compatible. This task supports the following attributes: Name Description Required/Default schema Name of a schema file being compiled This or nested <schema> elements are required binding An external binding file being applied to the schema file No force Setting this option to true forces the up-to-date check to fail. This option is mainly useful while working on the JaxMe generator. For JaxMe users, which only change schema files, this option isn't of much use. It is designed for JaxMe developers. No, false package Specifies the generated ...
• XsESchema: Implementation of xs:schema. Follows this specification: <xs:element name="schema" id="schema"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-schema"/> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="xs:openAttrs"> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="xs:include"/> <xs:element ref="xs:import"/> <xs:element ref="xs:redefine"/> <xs:element ref="xs:annotation"/> </xs:choice> <xs:sequence minOccurs="0" maxOccurs="unbounded"> ...
• XsESchemaImpl: Implementation of xs:schema. Follows this specification: <xs:element name="schema" id="schema"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-schema"/> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="xs:openAttrs"> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="xs:include"/> <xs:element ref="xs:import"/> <xs:element ref="xs:redefine"/> <xs:element ref="xs:annotation"/> </xs:choice> <xs:sequence minOccurs="0" maxOccurs="unbounded"> ...
• XsTComplexType: Interface of a complex type, to be shared by XsTLocalComplexType and XsTComplexType . Follows this specification: <xs:complexType name="complexType" abstract="true"> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:group ref="xs:complexTypeModel"/> <xs:attribute name="name" type="xs:NCName"> <xs:annotation> <xs:documentation> Will be restricted to required or forbidden </xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="mixed" type="xs:boolean" use="optional" default="false"> <xs:annotation> <xs:documentation> ...
• XsTComplexTypeImpl: Base implementation of a complex type, to be shared by org.apache.ws.jaxme.xs.xml.XsTLocalComplexType and org.apache.ws.jaxme.xs.xml.XsTComplexType . Follows this specification: <xs:complexType name="complexType" abstract="true"> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:group ref="xs:complexTypeModel"/> <xs:attribute name="name" type="xs:NCName"> <xs:annotation> <xs:documentation> Will be restricted to required or forbidden </xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="mixed" type="xs:boolean" ...
• Generator: The Generator is a frontend for working with the SchemaReaders, SourceWriters and whatever else. Usage: Generates java source definitions from various inputs: generate(java.net.URL) 55 generate(java.io.File) 55 generate(org.xml.sax.InputSource) 55 The inputs are interpreted into schema definitions by the SchemaReader set by calling setSchemaReader(org.apache.ws.jaxme.generator.SchemaReader) 55 . Other properties give fine grained control over various aspects of the file generation: setForcingOverwrite(boolean) 55 setSettingReadOnly(boolean) 55 setTargetDirectory(java.io.File) 55 and the processing ...
• XsGAllModel: Interface of xs:allModel , as specified by the following: <xs:group name="allModel"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:element name="element" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:annotation> <xs:documentation>restricted max/min</xs:documentation> </xs:annotation> <xs:complexContent> <xs:restriction base="xs:localElement"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:choice minOccurs="0"> <xs:element name="simpleType" type="xs:localSimpleType"/> ...
• XsGAllModelImpl: Implementation of xs:allModel , as specified by the following: <xs:group name="allModel"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:element name="element" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:annotation> <xs:documentation>restricted max/min</xs:documentation> </xs:annotation> <xs:complexContent> <xs:restriction base="xs:localElement"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:choice minOccurs="0"> <xs:element name="simpleType" type="xs:localSimpleType"/> ...
• AbstractResourceHome: LOG-DONE An implementation of the ResourceHome interface. This implementation was designed to work with resources that implement the PersistenceCallback interface as well as memory resident resources. If the resource class implements the PersistenceCallback interface SoftReference s will be used to recycle resource objects. The resource class implementation is responsible for saving its state to disk. This implementation will not call PersistenceCallback.store() 55 . The resource implementation must have a default constructor. Configuration options: sweeperDelay - configures how often the resource ...
• JavaSourceFactory: Factory for generating JavaSource objects. The factory properties: setOverwriteForced(boolean) 55 setSettingReadOnly(boolean) 55 are used for finely grained controlled over the generated source files. Methods are provided to access abstract descriptions of the files to be created: getTextFiles() 55 and getTextFile(java.lang.String, java.lang.String) 55 getJavaSources() 55 and getJavaSource(org.apache.ws.jaxme.js.JavaQName) 55 Concrete files (source and otherwise) are created by calling the following construction methods: newJavaSource(JavaQName) 55 , newJavaSource(JavaQName, String) 55 and newJavaSource(JavaQName, ...
• 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, ...
• XsERestriction: Implementation of xs:restriction , following this specification: <xs:element name="restriction" id="restriction"> <xs:complexType> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-restriction"> base attribute and simpleType child are mutually exclusive, but one or other is required </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:group ref="xs:simpleRestrictionModel"/> <xs:attribute name="base" type="xs:QName" use="optional"/> </xs:extension> </xs:complexContent> ...
• XsERestrictionImpl: Implementation of xs:restriction , following this specification: <xs:element name="restriction" id="restriction"> <xs:complexType> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-restriction"> base attribute and simpleType child are mutually exclusive, but one or other is required </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:group ref="xs:simpleRestrictionModel"/> <xs:attribute name="base" type="xs:QName" use="optional"/> </xs:extension> </xs:complexContent> ...
• XsESelector: Interface of the xs:selector element, specified by the following: A subset of XPath expressions for use in selectors A utility type, not for public use The following pattern is intended to allow XPath expressions per the following EBNF: Selector ::= Path ( '|' Path )* Path ::= ('.//')? Step ( '/' Step )* Step ::= '.' | NameTest NameTest ::= QName | '*' | NCName ':' '*' child:: is also allowed
• XsESelectorImpl: Interface of the xs:selector element, specified by the following: A subset of XPath expressions for use in selectors A utility type, not for public use The following pattern is intended to allow XPath expressions per the following EBNF: Selector ::= Path ( '|' Path )* Path ::= ('.//')? Step ( '/' Step )* Step ::= '.' | NameTest NameTest ::= QName | '*' | NCName ':' '*' child:: is also allowed
• XsTElementImpl: Implementation of the xs:element type, as specified by the following: <xs:complexType name="element" abstract="true"> <xs:annotation> <xs:documentation> The element element can be used either at the top level to define an element-type binding globally, or within a content model to either reference a globally-defined element or type or declare an element-type binding locally. The ref form is not allowed at the top level. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:sequence> <xs:choice minOccurs="0"> ...
• 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 ...
• XsEField: Interface of the xs:field element, with the following specification: A subset of XPath expressions for use in fields A utility type, not for public use The following pattern is intended to allow XPath expressions per the same EBNF as for selector, with the following change: Path ::= ('.//')? ( Step '/' )* ( Step | '@' NameTest )
• XsEFieldImpl: Interface of the xs:field element, with the following specification: A subset of XPath expressions for use in fields A utility type, not for public use The following pattern is intended to allow XPath expressions per the same EBNF as for selector, with the following change: Path ::= ('.//')? ( Step '/' )* ( Step | '@' NameTest )
• XsTElement: Implementation of the xs:element type, as specified by the following: The element element can be used either at the top level to define an element-type binding globally, or within a content model to either reference a globally-defined element or type or declare an element-type binding locally. The ref form is not allowed at the top level.
• XsTNamedGroupImpl: Implementation of a named top-level group, with the following specification: <xs:complexType name="namedGroup"> <xs:annotation> <xs:documentation> Should derive this from realGroup, but too complicated for now </xs:documentation> </xs:annotation> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:choice minOccurs="1" maxOccurs="1"> <xs:element name="all"> <xs:complexType> <xs:complexContent> <xs:restriction base="xs:all"> <xs:group ref="xs:allModel"/> <xs:attribute name="minOccurs" use="prohibited"/> ...
• XsTNamedGroup: Interface of a named top-level group, with the following specification: <xs:complexType name="namedGroup"> <xs:annotation> <xs:documentation> Should derive this from realGroup, but too complicated for now </xs:documentation> </xs:annotation> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:choice minOccurs="1" maxOccurs="1"> <xs:element name="all"> <xs:complexType> <xs:complexContent> <xs:restriction base="xs:all"> <xs:group ref="xs:allModel"/> <xs:attribute name="minOccurs" use="prohibited"/> <xs:attribute ...
• 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 ...
• TableSpace: Interface of a DB2 TableSpace. An object of this kind is used to create a CREATE TABLESPACE ... statement. A TableSpace can be associated to a BufferPool . If it is, it inherits certain settings from the BufferPool , in particular the pageSize 55 . A tablespace needs to know where data is stored physically. DB2 distinguishes between two possible data locations: System managed (Files handled by the operating system) and Database managed (Files handled by the database or Devices). In the latter case the database will preallocate space for the files or devices, giving a slightly faster operation. ...
• XsGSimpleRestrictionModel: Interface of xs:simpleRestrictionModel , following this specification: <xs:group name="simpleRestrictionModel"> <xs:sequence> <xs:element name="simpleType" type="xs:localSimpleType" minOccurs="0"/> <xs:group ref="xs:facets" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:group> <xs:group name="facets"> <xs:annotation> <xs:documentation> We should use a substitution group for facets, but that's ruled out because it would allow users to add their own, which we're not ready for yet. </xs:documentation> </xs:annotation> <xs:choice> ...
| Home | Contact Us | Privacy Policy | Terms of Service |