| Home >> All |
Page 1 2
| • | javax.accessibility.* (27) | • | javax.activation.* (26) | • | javax.bluetooth.* (1) |
| • | javax.crypto.* (42) | • | javax.ejb.* (32) | • | javax.enterprise.* (42) |
| • | javax.faces.* (137) | • | javax.ide.* (256) | • | javax.imageio.* (51) |
| • | javax.jms.* (73) | • | javax.mail.* (119) | • | javax.management.* (220) |
| • | javax.microedition.* (49) | • | javax.naming.* (90) | • | javax.net.* (34) |
Package Samples:
• javax.ide.menu.spi: The menu registration classes that extension writers use to find information about actions and menus.
• javax.ide.extension.spi: The ide package is where all JSR 198 packages are rooted.
• javax.mail.event: Classes modelling a mail system.
• javax.mail.internet: Classes modelling a mail system.
• javax.mail.search: Classes modelling a mail system.
• javax.management.j2ee.statistics: JSR-77 Specification .
• javax.naming.directory
• javax.crypto.interfaces
• javax.imageio.event
• javax.net.ssl
• javax.bluetooth
• javax.accessibility
• javax.naming
• javax.naming.event
• javax.naming.ldap
• javax.naming.spi
• javax.ejb
• javax.ejb.spi
• javax.jms
• javax.management
Classes:
• VariableInfo: Information on the scripting variables that are created/modified by a tag (at run-time). This information is provided by TagExtraInfo classes and it is used by the translation phase of JSP. Scripting variables generated by a custom action have an associated scope of either AT_BEGIN, NESTED, or AT_END. The class name (VariableInfo.getClassName) in the returned objects is used to determine the types of the scripting variables. Note that because scripting variables are assigned their values from scoped attributes which cannot be of primitive types, "boxed" types such as java.lang.Integer ...
• TreeManager: The TreeManager serves as a FileT factory. Clients obtain FileTs by requesting a FileT from the manager and by creating empty FileTs through the manager. Clients change the writability of FileTs by opening and closing TreeTransactions. For the sake of transaction consistency, a FileT belongs to exactly one TreeManager for the lifetime of the FileT. The TreeManager owns a single lockable resource (which may be itself) which must, at the minumum, provide the functionality of a read-write lock. Each FileT is tied to a single lockable resource (which may be itself) which is defined by the owning IDE ...
• DocFlavor: DocFlavor provides a description of the format in which the print data will be supplied in a print job to the print service. A doc flavor consists of two parts: The MIME type (Multipurpose Internet Mail Extensions types as described in RFC 2045/2046) specifying the media format of the print data. The representation class name which is the fully qualified name of the class providing the print data to the print job. For example if the print data is supplied as a byte array the representation class name will be "[B" or for an input stream "java.io.InputStream" . The DocFlavor class is therefore used ...
• BodyTag: The BodyTag interface extends IterationTag by defining additional methods that let a tag handler manipulate the content of evaluating its body. It is the responsibility of the tag handler to manipulate the body content. For example the tag handler may take the body content, convert it into a String using the bodyContent.getString method and then use it. Or the tag handler may take the body content and write it out into its enclosing JspWriter using the bodyContent.writeOut method. A tag handler that implements BodyTag is treated as one that implements IterationTag, except that the doStartTag method ...
• AbstractButton: Provides an abstract implementation of common button behaviour, data model and look & feel. This class is supposed to serve as a base class for several kinds of buttons with similar but non-identical semantics: toggle buttons (radio buttons and checkboxes), simple push buttons, menu items, etc. Buttons have many properties, some of which are stored in this class while others are delegated to the button's model. The following properties are available: Property Stored in Bound? action button no actionCommand model no borderPainted button yes contentAreaFilled button yes disabledIcon button yes ...
• CipherSpi: This class represents the Service Provider Interface ( SPI ) for cryptographic ciphers. Providers of cryptographic ciphers must subclass this for every cipher they implement, implementing the abstract methods as appropriate, then provide an entry that points to the subclass in their implementation of java.security.Provider . CipherSpi objects are instantiated along with Cipher s when the Cipher.getInstance(java.lang.String) 55 methods are invoked. Particular ciphers are referenced by a transformation , which is a String consisting of the cipher's name or the ciper's name followed by a mode and ...
• JList: This class is a facade over three separate objects: ListModel , ListSelectionModel and javax.swing.plaf.ListUI . The facade represents a unified "list" concept, with independently replacable (possibly client-provided) models for its contents and its current selection. In addition, each element in the list is rendered via a strategy class ListCellRenderer . Lists have many properties, some of which are stored in this class while others are delegated to the list's model or selection. The following properties are available: Property Stored in Bound? accessibleContext list no anchorSelectionIndex selection ...
• 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 ...
• SaslClient: Performs SASL authentication as a client. A protocol library such as one for LDAP gets an instance of this class in order to perform authentication defined by a specific SASL mechanism. Invoking methods on the SaslClient instance process challenges and create responses according to the SASL mechanism implemented by the SaslClient . As the authentication proceeds, the instance encapsulates the state of a SASL client's authentication exchange. Here's an example of how an LDAP library might use a SaslClient . It first gets an instance of a SaslClient: SaslClient sc = Sasl.createSaslClient(mechanisms, ...
• AuthPermission: A permission controlling access to authentication service. The actions field of auth permission objects is ignored; the whole of the permission is defined by the target . The authentication permission targets recognized are: doAs Allows access to the Subject#doAs(javax.security.auth.Subject java.security.PrivilegedAction) methods. doAsPrivileged Allows access to the Subject.doAsPrivileged(javax.security.auth.Subject, java.security.PrivilegedAction, java.security.AccessControlContext) 55 methods. getSubject Allows access to the Subject associated with a thread. getSubjectFromDomainCombiner Allows ...
• JLayeredPane: A container that adds depth to the usual Container semantics. Each child component of a Layered Pane is placed within one of several layers. JLayeredPane defines a set of standard layers. The pre-defined sets are (in the order from button to top): DEFAULT_LAYER 55 The layer where most of the normal components are placed. This is the bottommost layer. PALETTE_LAYER 55 Palette windows are placed in this layer. MODAL_LAYER 55 The layer where internal modal dialog windows are placed. POPUP_LAYER 55 The layer for popup menus DRAG_LAYER 55 Components that are beeing dragged are temporarily placed in ...
• StateEdit: A helper class, making it easy to support undo and redo. The following example shows how to use this class. Foo foo; // class Foo implements StateEditable StateEdit edit; edit = new StateEdit(foo, "Name Change"); foo.setName("Jane Doe"); edit.end(); undoManager.addEdit(edit); If Foo ’s implementation of StateEditable considers the name as part of the editable state, the user can now choose “Undo Name Change” or “Redo Name Change” from the respective menu. No further undo support is needed from the application. The following explains what happens in the example. ...
• UndoManager: A manager for providing an application’s undo/redo functionality. Tyipcally, an application will create only one single instance of UndoManager. When the user performs an undoable action, for instance changing the color of an object from green to blue, the application registers an UndoableEdit object with the UndoManager . To implement the “undo” and “redo” menu commands, the application invokes the UndoManager’s undo() 55 and redo() 55 methods. The human-readable text of these menu commands is provided by getUndoPresentationName() 55 and getRedoPresentationName() ...
• Tag: The interface of a classic tag handler that does not want to manipulate its body. The Tag interface defines the basic protocol between a Tag handler and JSP page implementation class. It defines the life cycle and the methods to be invoked at start and end tag. Properties The Tag interface specifies the setter and getter methods for the core pageContext and parent properties. The JSP page implementation object invokes setPageContext and setParent, in that order, before invoking doStartTag() or doEndTag(). Methods There are two main actions: doStartTag and doEndTag. Once all appropriate properties ...
• EditorManager: The EditorManager manages the life cycle of Editor s. It is also the registry of information about what editors can be used with particular documents. Clients use this class to open an editor on a javax.ide.model.Document . When clients request to open an editor on a specific document, the editor manager performs the following tasks: 1. Create an instance of the requested editor type. If no type is specified, create an instance of the preferred editor associated with the target document. 2. Call the Editor.open(javax.ide.command.Context) 55 method passing the appropriate context. 3. Call the Editor.restore(java.util.prefs.Preferences) ...
• 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 ...
• JspWriter: The actions and template data in a JSP page is written using the JspWriter object that is referenced by the implicit variable out which is initialized automatically using methods in the PageContext object. This abstract class emulates some of the functionality found in the java.io.BufferedWriter and java.io.PrintWriter classes, however it differs in that it throws java.io.IOException from the print methods while PrintWriter does not. Buffering The initial JspWriter object is associated with the PrintWriter object of the ServletResponse in a way that depends on whether the page is or is not buffered. ...
• JAXBContext: The JAXBContext provides the JAXB users anchor to the implmentation and hos generated classes. A JAXBContext is used to obtain instances of Marshaller , Unmarshaller , and Validator . To obtain a JAXBContext, the application invokes JAXBContext context = JAXBContext.newInstance("com.mycompany:com.mycompany.xml"); The list of colon separated package names matches the list in the schemas used to generate classes. In other words: If you have a schema using package name "com.mycompany.xml", then this package name has to be part of the list. The JAXBContext class will scan the given list of packages ...
• MonitorNotification: A notification from one of the monitor services. The notification occurs only when the state is first entered. All monitor services produce the following notifications. OBSERVED_OBJECT_ERROR 55 when the MBean is not registered. OBSERVED_ATTRIBUTE_ERROR 55 when the MBean's attribute does not exist. OBSERVED_ATTRIBUTE_TYPE_ERROR 55 when the MBean's attribute is not of the correct type for the monitor or the derived gauge value. RUNTIME_ERROR 55 for any other error. The counter monitor produces the following notifications. THRESHOLD_ERROR 55 when one of the monitors threshold vaues is of an incorrect ...
• 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 ...
• PageContext: PageContext extends JspContext to provide useful context information for when JSP technology is used in a Servlet environment. A PageContext instance provides access to all the namespaces associated with a JSP page, provides access to several page attributes, as well as a layer above the implementation details. Implicit objects are added to the pageContext automatically. The PageContext class is an abstract class, designed to be extended to provide implementation dependent implementations thereof, by conformant JSP engine runtime environments. A PageContext instance is obtained by a JSP implementation ...
• JSlider: A visual component that allows selection of a value within a range by adjusting a thumb in a track. The values for the minimum, maximum, extent and value are stored in a DefaultBoundedRangeModel . A JSlider component has the following properties: Property Stored in Bound? extent model no inverted slider yes labelTable slider yes majorTickSpacing slider yes maximum model yes minimum model yes minorTickSpacing slider yes model slider yes orientation slider yes paintLabels slider yes paintTicks slider yes snapToTicks slider yes value model no valueIsAdjusting model no The various behavioural aspects ...
• CallbackHandler: An application implements a CallbackHandler and passes it to underlying security services so that they may interact with the application to retrieve specific authentication data, such as usernames and passwords, or to display certain information, such as error and warning messages. CallbackHandler s are implemented in an application-dependent fashion. For example, implementations for an application with a graphical user interface (GUI) may pop up windows to prompt for requested information or to display error messages. An implementation may also choose to obtain requested information from an alternate ...
• DocumentFactory: The DocumentFactory interface is responsible for creating intances of Document s. The type of Document that gets created depends on the java.net.URI that is passed into the findOrCreate(URI) 55 and findOrCreate(MetaClass, URI) 55 methods. The DocumentFactory makes use of registered Recognizer instances to determine what Document class corresponds to a particular java.net.URI . JSR-198 specifies a number of ways to recognize documents: 1. By recognizing characteristics of the URI , 2. For XML documents by recognizing certain markups, and 3. By allowing extension writers to have full control of how ...
| Home | Contact Us | Privacy Policy | Terms of Service |