Attributes as defined in PKCS#6. The ASN.1 definition of this structure is
Instances can be initialized with a {@link OIDRegistry OIDRegistry} that isused to resolve attribute value types. The type of value of a PKCS#6 Content Type Attribute is for instanceAttributes ::= SET OF Attribute
OBJECT IDENTIFIER. The OID of this attribute is { pkcs-9 3}. The OID identifies both the attribute and the attribute value's type. Please note that when a registry is specified, exceptions are thrown if an attribute is encountered whose type cannot be resolved by that registry or any of the global registries. @author Volker Roth @version "$Id: Attributes.java,v 1.2 2000/12/06 17:47:33 vroth Exp $"
The Attributes interface is essentially a version of the org.xml.sax.Attributes interface modified to use the JAX-WS QName class.
Although namespace declarations can appear in the attribute list, the actual values of the local name and URI properties are implementation-specific.
Applications that need to iterate through all the attributes can use the {@link #isNamespaceDeclaration} method to identify namespace declarationsand skip them.
Also, the URI property of an attribute will never be null. The value "" (empty string) is used for the URI of non-qualified attributes.
@author WS Development TeamThe Attributes interface is essentially a version of the org.xml.sax.Attributes interface modified to use the JAX-WS QName class.
Although namespace declarations can appear in the attribute list, the actual values of the local name and URI properties are implementation-specific.
Applications that need to iterate through all the attributes can use the {@link #isNamespaceDeclaration} method to identify namespace declarationsand skip them.
Also, the URI property of an attribute will never be null. The value "" (empty string) is used for the URI of non-qualified attributes.
@author WS Development TeamThis interface defines the methods that are implemented by a collection of a particular directory entry's attributes.
A directory entry can have zero or more attributes comprising its attributes collection. The attributes are unordered within the collection. The attributes can be identified by name. The names of attributes are either case sensitive or case insensitive as indicated by the isCaseIgnored method. Method names refer to attribute ID (identity) rather than name, for brevity.
The attribute collection is created when the directory entry is created.
This interface represents a list of XML attributes.
It is a more efficient version of org.xml.sax.Attributes with {@link CharArray CharArray}/ {@link CharSequence CharSequence} instead of the String to avoid forcing dynamic object allocations.
Normalize the case of a String key to lower case making the collection case insensitive.
String property converted into a specific type. The {@link #get(Key)}, {@link #put(Key,Object)} and {@link #remove(Key)} methods converts Stringvalues to/from the instances of the class specified by {@link Key#type}.
@author Nick Scavelli
@author Stian Thorgersen
This interface extends a map to provide convenient method for dealing with attribute values in a type safe manner when the interface client knows the type of an attribute and wants to deal with it accordingly.
@author Julien Viet @version $Revision$AttributeRow that one can find in the AttributesAPI. Cast this class to AttributeRow to profit from all features. In few words, attribute values can be get with the column index or id. @author Mathieu Bastian
The purpose of using this interface is to decouple Spring code from any specific attributes implementation. Even once JSR-175 is available, there is still value in such a facade interface, as it allows for hierarchical attribute sources: for example, an XML file or properties file might override some attributes defined in source-level metadata with JSR-175 or another framework. @author Mark Pollack @author Rod Johnson @since 30.09.2003 @see org.springframework.metadata.commons.CommonsAttributes
This interface allows access to a list of attributes in three different ways:
The list will not contain attributes that were declared #IMPLIED but not specified in the start tag. It will also not contain attributes used as Namespace declarations (xmlns*) unless the http://xml.org/sax/features/namespace-prefixes feature is set to true (it is false by default). Because SAX2 conforms to the original "Namespaces in XML" recommendation, it normally does not give namespace declaration attributes a namespace URI.
Some SAX2 parsers may support using an optional feature flag (http://xml.org/sax/features/xmlns-uris) to request that those attributes be given URIs, conforming to a later backwards-incompatible revision of that recommendation. (The attribute's "local name" will be the prefix, or "xmlns" when defining a default element namespace.) For portability, handler code should always resolve that conflict, rather than requiring parsers that can change the setting of that feature flag.
If the namespace-prefixes feature (see above) is false, access by qualified name may not be available; if the http://xml.org/sax/features/namespaces feature is false, access by Namespace-qualified names may not be available.
This interface replaces the now-deprecated SAX1 {@link org.xml.sax.AttributeList AttributeList} interface, which does not contain Namespace support. In addition to Namespace support, it adds the getIndex methods (below).
The order of attributes in the list is unspecified, and will vary from implementation to implementation.
@since SAX 2.0 @author David Megginson @version 2.0.1 (sax2r2) @see org.xml.sax.helpers.AttributesImpl @see org.xml.sax.ext.DeclHandler#attributeDecl | |
| |
| |
| |
| |
| |
| |
| |
| |
| |