| Home >> All >> org >> apache >> xml |
Page 1 2
| • | org.apache.xmlrpc.applet.* (5) | • | org.apache.xmlrpc.fesi.* (3) | • | org.apache.xmlrpc.secure.* (5) |
| • | org.apache.xmlrpc.util.* (2) |
Package Samples:
• org.apache.xmlrpc.fesi
• org.apache.xmlrpc.util
• org.apache.xmlrpc.applet
• org.apache.xmlrpc.secure
• org.apache.xmlrpc.secure.sunssl
Classes:
• RegularExpression: A regular expression matching engine using Non-deterministic Finite Automaton (NFA). This engine does not conform to the POSIX regular expression. How to use A. Standard way RegularExpression re = new RegularExpression( regex ); if (re.matches(text)) { ... } B. Capturing groups RegularExpression re = new RegularExpression( regex ); Match match = new Match(); if (re.matches(text, match)) { ... // You can refer captured texts with methods of the Match class. } Case-insensitive matching RegularExpression re = new RegularExpression( regex , "i"); if (re.matches(text) >= 0) { ...} Options You can specify ...
• SchemaType: Represents a schema type. SchemaType is the metadata "type" class for XmlObject , and it plays the analogous role for XmlObject that java.lang.Class plays for java.lang.Object . Every XML Bean class corresponds to a singleton SchemaType object obtainable by ClassName.type (e.g., XmlNonPositiveInteger.type 55 ), and every XML Bean instance has an actual SchemaType, obtainable by XmlObject.schemaType() 55 . The ClassName.type and schemaType() mechanisms are analogous to the ordinary Java ClassName.class and obj.getClass() mechanisms. All schema types are represented by a SchemaType, this includes ...
• SchemaTypeSystem: A finite set of XML Schema component definitions. Every SchemaComponent such as a SchemaType , SchemaGlobalElement , SchemaGlobalAttribute , SchemaModelGroup , SchemaAttributeGroup , or SchemaIdentityConstraint , is defined in exactly one SchemaTypeSystem. (See SchemaComponent.getTypeSystem() 55 .) A single SchemaTypeSystem can include definitions from any number of namespaces; one SchemaTypeSystem consists simply of a set of component definitions that were compiled together. Since every component is defined in a single SchemaTypeSystem, no SchemaTypeSystem other than XmlBeans.getBuiltinTypeSystem() ...
• XmlObject: Corresponds to the XML Schema xs:anyType , the base type for all XML Beans. Since all XML Schema types are translated into corresponding XML Bean classes, and all Schema type derivation corresponds to Java class inheritance, the fact that all Schema types derive from xs:anyType means that all XML Bean classes derive from XmlObject. On this base class you will find a number of common facilities that all XML Bean classes provide: Every XML Bean class has an inner Factory class for creating and parsing instances, including XmlObject. Use XmlObject.Factory itself to produce untyped XML trees or XML ...
• Catalog: Represents OASIS Open Catalog files. This class implements the semantics of OASIS Open Catalog files (defined by OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401) ). The primary purpose of the Catalog is to associate resources in the document with local system identifiers. Some entities (document types, XML entities, and notations) have names and all of them can have either public or system identifiers or both. (In XML, only a notation can have a public identifier without a system identifier, but the methods implemented in this class obey the Catalog semantics from the SGML days when ...
• XmlCursor: Represents a position between two logical tokens in an XML document. The tokens themselves are not exposed as objects, but their type and properties are discoverable through methods on the cursor. In particular, the general category of token is represented by a TokenType . You use an XmlCursor instance to navigate through and manipulate an XML instance document. Once you obtain an XML document, you can create a cursor to represent a specific place in the XML. Because you can use a cursor with or without a schema corresponding to the XML, cursors are an ideal way to handle XML without a schema. ...
• ConcurrentReaderHashMap: A version of Hashtable that supports mostly-concurrent reading, but exclusive writing. Because reads are not limited to periods without writes, a concurrent reader policy is weaker than a classic reader/output policy, but is generally faster and allows more concurrency. This class is a good choice especially for tables that are mainly created by one thread during the start-up phase of a program, and from then on, are mainly read (with perhaps occasional additions or removals) in many threads. If you also need concurrency among writes, consider instead using ConcurrentHashMap. Successful retrievals ...
• CoroutineManager: Support the coroutine design pattern. A coroutine set is a very simple cooperative non-preemptive multitasking model, where the switch from one task to another is performed via an explicit request. Coroutines interact according to the following rules: One coroutine in the set has control, which it retains until it either exits or resumes another coroutine. A coroutine is activated when it is resumed by some other coroutine for the first time. An active coroutine that gives up control by resuming another in the set retains its context -- including call stack and local variables -- so that if/when ...
• AttachmentPart: A single attachment to a SOAPMessage object. A SOAPMessage object may contain zero, one, or many AttachmentPart objects. Each AttachmentPart object consists of two parts, application-specific content and associated MIME headers. The MIME headers consists of name/value pairs that can be used to identify and describe the content. An AttachmentPart object must conform to certain standards. It must conform to MIME [RFC2045] standards It MUST contain content The header portion MUST include the following header: Content-Type This header identifies the type of data in the content of an AttachmentPart ...
• SOAPEnvelope: The container for the SOAPHeader and SOAPBody portions of a SOAPPart object. By default, a SOAPMessage object is created with a SOAPPart object that has a SOAPEnvelope object. The SOAPEnvelope object by default has an empty SOAPBody object and an empty SOAPHeader object. The SOAPBody object is required, and the SOAPHeader object, though optional, is used in the majority of cases. If the SOAPHeader object is not needed, it can be deleted, which is shown later. A client can access the SOAPHeader and SOAPBody objects by calling the methods SOAPEnvelope.getHeader and SOAPEnvelope.getBody . The following ...
• XmlCalendar: An XML Schema compatible subclass of GregorianCalendar . XmlCalendar modifies several key details in the behavior of GregorianCalendar to make it more useful when dealing with XML dates. It is easy to convert between XmlCalendar and GDate , or to parse or emit an XmlCalendar using a standard XML Schema lexical representation. To match XML Schema dates, this XmlCalendar is a fully proleptic Gregorian calendar by default, which means that Gregorian calendar rules are applied backwards in time as if they had always been in effect, actual historical circumstances concerning the observance of the 1582 ...
• SchemaTypeLoader: Represents a searchable set of XML Schema component definitions. SchemaTypeLoader is somewhat analogous to java.lang.ClassLoader , because it is responsible for finding SchemaComponent definitions by name, yet it is not responsible for being able to enumerate all the component definitons available. (If you wish to enumerate component definitions, see SchemaTypeSystem .) There are some ways in which SchemaTypeSystems are dissimilar from ClassLoaders, however. Since XML Schema has a number of instance-oriented typing mechanisms (such as wildcards) that do not exist in Java, a SchemaTypeLoader is ...
• MessageFactory: A factory for creating SOAPMessage objects. A JAXM client performs the following steps to create a message. Creates a MessageFactory object from a ProviderConnection object ( con in the following line of code). The String passed to the createMessageFactory method is the name of of a messaging profile, which must be the URL for the schema. MessageFactory mf = con.createMessageFactory(schemaURL); Calls the method createMessage on the MessageFactory object. All messages produced by this MessageFactory object will have the header information appropriate for the messaging profile that was specified ...
• DTM: DTM is an XML document model expressed as a table rather than an object tree. It attempts to provide an interface to a parse tree that has very little object creation. (DTM implementations may also support incremental construction of the model, but that's hidden from the DTM API.) Nodes in the DTM are identified by integer "handles". A handle must be unique within a process, and carries both node identification and document identification. It must be possible to compare two handles (and thus their nodes) for identity with "==". Namespace URLs, local-names, and expanded-names can all be represented ...
• SOAPMessage: The root class for all SOAP messages. As transmitted on the "wire", a SOAP message is an XML document or a MIME message whose first body part is an XML/SOAP document. A SOAPMessage object consists of a SOAP part and optionally one or more attachment parts. The SOAP part for a SOAPMessage object is a SOAPPart object, which contains information used for message routing and identification, and which can contain application-specific content. All data in the SOAP Part of a message must be in XML format. A new SOAPMessage object contains the following by default: A SOAPPart object A SOAPEnvelope object ...
• BaseMarkupSerializer: Base class for a serializer supporting both DOM and SAX pretty serializing of XML/HTML/XHTML documents. Derives classes perform the method-specific serializing, this class provides the common serializing mechanisms. The serializer must be initialized with the proper writer and output format before it can be used by calling setOutputCharStream(java.io.Writer) 55 or setOutputByteStream(java.io.OutputStream) 55 for the writer and setOutputFormat(org.apache.xml.serialize.OutputFormat) 55 for the output format. The serializer can be reused any number of times, but cannot be used concurrently by two ...
• CatalogManager: CatalogManager provides an interface to the catalog properties. Properties can come from two places: from system properties or from a CatalogManager.properties file. This class provides a transparent interface to both, with system properties preferred over property file values. The following table summarizes the properties: System Property CatalogManager.properties Property Description xml.catalog.ignoreMissing   If true, a missing CatalogManager.properties file or missing properties within that file will not generate warning messages. See also the ignoreMissingProperties method. xml.catalog.files ...
• XmlValidationError: The XmlValidationError class extends the XmlError XMLError class. The XML Validator contains extra attributes that can be used to construct the XML validation error programatically. To extract the validation error cast the errors to XmlValidationError instead of XmlError for example: xobj.validate(new XmlOptions().setErrorListener(errors)) for (Iterator it = errors.iterator(); it.hasNext(); ) { XmlError err = (XmlError)it.next()); if (err instanceof XmlValidationError) { XmlValidationError validationError = (XmlValidationError) err; } } Whenever an XmlValidationError is retrieved it will always ...
• XmlOptions: Used to supply options for loading, saving, and compiling, and validating. There are two styles for using XmlOptions: multiline setup, and single-line use. Here are two examples. First, multiline style: XmlOptions opts = new XmlOptions(); opts.setSavePrettyPrint(); opts.setSavePrettyPrintIndent(4); System.out.println(xobj.xmlText(opts)); The alternative is single-line usage: System.out.println(xobj.xmlText( new XmlOptions().setSavePrettyPrint().setSavePrettyPrintIndent(4))); Table showing where each option gets used. Note that: options available for newInstance methods will also apply for parse ...
• Serializer: Interface for a DOM serializer implementation, factory for DOM and SAX serializers, and static methods for serializing DOM documents. To serialize a document using SAX events, create a compatible serializer and pass it around as a org.xml.sax.DocumentHandler . If an I/O error occurs while serializing, it will be thrown by DocumentHandler.endDocument() > DocumentHandler.endDocument() 55 . The SAX serializer may also be used as org.xml.sax.DTDHandler , org.xml.sax.ext.DeclHandler and org.xml.sax.ext.LexicalHandler . To serialize a DOM document or DOM element, create a compatible serializer and call ...
• Name: A representation of an XML name. This interface provides methods for getting the local and namespace-qualified names and also for getting the prefix associated with the namespace for the name. It is also possible to get the URI of the namespace. The following is an example of a namespace declaration in an element. <wombat:GetLastTradePrice xmlns:wombat="http://www.wombat.org/trader"> ("xmlns" stands for "XML namespace".) The following shows what the methods in the Name interface will return. getQualifiedName will return "prefix:LocalName" = "WOMBAT:GetLastTradePrice" getURI will return "http://www.wombat.org/trader" ...
• HTMLSerializer: Implements an HTML/XHTML serializer supporting both DOM and SAX pretty serializing. HTML/XHTML mode is determined in the constructor. For usage instructions see Serializer . If an output stream is used, the encoding is taken from the output format (defaults to UTF-8 ). If a writer is used, make sure the writer uses the same encoding (if applies) as specified in the output format. The serializer supports both DOM and SAX. DOM serializing is done by calling BaseMarkupSerializer.serialize(org.w3c.dom.Element) 55 and SAX serializing is done by firing SAX events and using the serializer as a document ...
• QNameSet: This interface represents a lattice of finite and infinite sets of QNames. The lattice the minimal one that is closed under union, intersection, and inverse, and contains individual QNames as well as entire namespaces. Here is a summary of the two kinds of QNameSets: A QNameSet can cover a finite set of namespaces, additionally including a finite set of QNames outside those namespaces, and with the exception of a finite set of QNames excluded from those namespaes: excludedQNamesInIncludedURIs == the set of excluded QNames from coveredURIs namespaces excludedURIs == null includedURIs == the set ...
• SOAPPart: The container for the SOAP-specific portion of a SOAPMessage object. All messages are required to have a SOAP part, so when a SOAPMessage object is created, it will automatically have a SOAPPart object. A SOAPPart object is a MIME part and has the MIME headers Content-Id, Content-Location, and Content-Type. Because the value of Content-Type must be "text/xml", a SOAPPart object automatically has a MIME header of Content-Type with its value set to "text/xml". The value must be "text/xml" because content in the SOAP part of a message must be in XML format. Content that is not of type "text/xml" must ...
• XMLSerializer: Implements an XML serializer supporting both DOM and SAX pretty serializing. For usage instructions see Serializer . If an output stream is used, the encoding is taken from the output format (defaults to UTF-8 ). If a writer is used, make sure the writer uses the same encoding (if applies) as specified in the output format. The serializer supports both DOM and SAX. SAX serializing is done by firing SAX events and using the serializer as a document handler. DOM serializing is done by calling BaseMarkupSerializer.serialize(Document) 55 or by using DOM Level 3 org.w3c.dom.ls.DOMSerializer and serializing ...
| Home | Contact Us | Privacy Policy | Terms of Service |