| Home >> All >> de >> danet >> an >> [ util Javadoc ] |
• de.danet.an.util: Javadoc index of package de.danet.an.util.
Package Samples:
• de.danet.an.util.web.action: This package consists of classes that help in implementing the web-tier of an application.
• de.danet.an.util.multipartform: This package is the project specific contribution to AN's general Java library.
• de.danet.an.util.log4j: This package is the project specific contribution to AN's general Java library.
• de.danet.an.util.cocoon.prefs: This package contains classes that support the usage of Cocoon (i.e.
• de.danet.an.util.cocoon.xforms: This package contains classes that support the usage of Cocoon (i.e.
• de.danet.an.util.cocoon.action
• de.danet.an.util.cocoon
• de.danet.an.util.sax
• de.danet.an.util.web
• de.danet.an.util.userprefs
• de.danet.an.util.persistentmaps
• de.danet.an.util.ejbtimer
Classes:
• JDBCPersistentMap: This class provides an implementation of PersistentMap > PersistentMap that uses JDBC to implement the persistence. The class uses an abstract SQL table model. The table consists of a column for the map id, the entry key and two value entries. All columns except the second value entry are of type string, with lengths as appropriate for the application. The second value field is of type BLOB (binary large object) and is used if either the value to be stored is not of type String > String or longer than a given limit. The map id enables storing of several jdbc persistent maps in a single table. It ...
• Mapping: Base class, implementing the methods used in logic sheet(s). The mathods in this class can be used to support an internationalization of texts and error messages in xsp pages. Together with the logicsheet mapping.xsl , to use the functionality the followng steps must be fullfilled: Include the logicsheet mapping.xsl in your own logicsheet for processing the xsp page. In your logicsheet, include the following match-rules: <xsl:template match="page"> <page> <xsp:logic> if (session == null) { session = request.getSession (true); } session.setAttribute ("errorList", new ArrayList ...
• Duration: This class provides a representation of durations and a parser for strings that represent durations. Strings that can be parsed consist of value/unit pairs. Values can be arbitrary text, valid unit names are "years", "yrs", "months", "mts", "hours", "hrs", "min" and "sec". There may be only one pair for each unit i.e. "5 years 3 yrs" is illegal. Value/unit pairs must be separated from each other with at least one whitespace character. Units may follow values immediately if the value is a number, else they must be separated by at least one whitespace. Any duration unit may be omitted, but the descending ...
• HandlerStack: HandlerStack provides support for dispatching SAX events to the appropriate target during processing of an XML document. Writing an event handler for a SAX parser and being object oriented isn't easy. Most people tend to write one large event handler that knows far too much about the objects that it has to create and provide with information. According to the object oriented approach, every object should implement its own handling for the parts of the XML text that provides information about the object's state. This means changing the parser's content handler in a controlled way. Each time that ...
• ApplLogger: This class provides an alternate access to the log4j logging library. The necessity arises from the usage of log4j as logging package in the JBoss application server. As log4j is already included in JBoss' classpath and configured by JBoss, we cannot have really independent application level logging. The central problem is the static default hierarchy used by org.apache.log4j.Category . For a distinct application level logging we need an alternate hierarchy. Of course, we want to access this hierarchy as simple as Category.getInstance(...) and thus we need a new class that provides the static acces ...
• ActionDispatcher: A ActionDispatcher is a collection of ActionHandler s and ActionDispatcher s. ActionDispatcher s are usually created by ActionHandler s that want to register one or more of their methods. A "top level" ActionDispatcher is used to collect all handlers. This dispatcher is used to handle requests by calling its dispatchRequest 55 methods.
• HttpMultiPartParser: This class provides methods for parsing a HTML multi-part form. Each method returns a Hashtable which contains keys for all parameters sent from the web browser. The corresponding values are either type "String" or "FileInfo" depending on the type of data in the corresponding part. The following is a sample InputStream expected by the methods in this class: -----------------------------7ce23a18680 Content-Disposition: form-data; name="SomeTextField1" on -----------------------------7ce23a18680 Content-Disposition: form-data; name="LocalFile1"; filename="C:\temp\testit.c" Content-Type: text/plain ...
• Mapping: Base class, implementing the methods used in logic sheet(s). The methods in this class can be used to support an internationalization of texts and error messages in xsp pages. To use the functionality the followng steps must be fullfilled: Add action defintion here Define an I18n.properties file for your application. In your xsp page, you can now use the mapping functionality, e.g. <mapping:generate_mappings key="staff.group.list" basename="de.danet.an.staffmgmt.webclient.I18n"/> In your Java classes, where you encapsulate the logic code, you can set error texts like this: Mapping.mapError ...
• WebActionDispatcher: A WebActionDispatcher is a collection of WebActionHandler s and WebActionDispatcher s. WebActionDispatcher s are usually created by WebActionHandler s that want to register on or more of their methods. A "top level" WebActionDispatcher is used to collect all handlers. This dispatcher is used to handle requests by calling its dispatchRequest 55 methods.
• UserPrefs: This class provides the functions needed to use user preferences in an XSP. It provides the method 55 that generates XML representing all user preferences. This method will usually be accessed using the standard template in global.xsl . In addition this class implements an ActionHandler > ActionHandler that can be used to modify the user preferences. Note that in order to use this class, the deployment descripor of the cocoon servlet must bind java:comp/env/DanetUtil to the Danet utility EJB.
• UniversalPrepStmt: This class provides a wrapper that can handle special database requirements. Although suitable for all jdbc-driven database connections, special features of the following databases are supported: Oracle, SAPDB and Hypersonic. In addition, all set/get methods for non-primitives handle null values correctly. Additional methods setBinary 55 and setInt(int, Integer) 55 setLargeString 55 are provided for convenience.
• ApplLog4jFactory: This class provides an alternate access to the log4j logging library for Apache commons logging.. The necessity arises from the usage of log4j as logging package in the JBoss application server. As log4j is already included in JBoss' classpath and configured by JBoss, we cannot have really independent application level logging. The central problem is the static default hierarchy used by org.apache.log4j.Category . For a distinct application level logging we need an alternate hierarchy. This factory uses such an alternate hierarchy. This implementation is based on the Log4JFactory from Apache.
• UserPrefsAsMap: This class provides a map view of user preferences as provided by a user preferences service . This adapter allows user preferences to be fed to the SegmentedMap > SegmentedMap class. NOTE: This view is a snapshot of the preference data at creation time. Subsequent modifications to the preferences are not mirrored by this view.
• SAXContentBuffer: This class provides a buffer for SAX content events. The events reported to an instance of this class are internally recorded. After recording, the events may be played back an arbitrary number of times. The class implements Serializable > Serializable . An instance of this class may thus be transferred to another process and the SAX events may be replayed there. This implementation uses code from Apache's XMLByteStreamCompiler and associated interpreter.
• EJBClientTest: This class provides a wrapper around a JUnit test that will run the test as the subject identified by LoginContext passed to the constructor. The operations performed depend on the context. The default is to simply forward the call to run to the Test passed to the constructor. If the class weblogic.security.Security is available, the test will be passed to its runAs method.
• StackedHandler: StackedHandler represents an item on the HandlerStack . While any ContentHandler > ContentHandler may be pushed on the stack, the StackedHandler provides some convenience methods that may help implementing a stacked handler.
• JDOMSerializationWrapper: This class provides a wrapper or rather patch for a JDOM element of version jdom-b8 in which the variable of additionalNamespaces are transient, this results that the informations of additionalNamespaces get lost after the serialization. In this class the given JDOM Element with additionalNamespaces are serialized correctly.
• SegmentedResourceMap: This class represents a ResourceBundle > ResourceBundle that has been made available as SegmentedMap . It simply adds a method to access the underlying ResourceBundle .
• XmlnsUrisPatcher: This class provides a simple filter that can be used to convert the SAX events reported for attributes with qualified name "xmlns" or prefix "xmlns:" to the later XML namespaces specification. This is intended to be used in conjunction with parsers that do not support the "xmlns-uris" feature.
• ActionHandler: ActionHandler is the base class for web action request handlers used in Cocoon 2. A derived class creates one or more instances of itself (and thus ActionHandler ) by calling the constructor with the name of its method that is to be made invokable as an argument.
• WebActionHandler: WebActionHandler is the base class for web action request handlers. A derived class creates one or more instances of itself (and thus WebActionHandler ) by calling the constructor with the name of its method that is to be made invokable as an argument.
• EJBTimerServiceJBoss: This class adds JBoss sepcific state handling to the basic EJBTimerService . For this extended service, dependencies on the queues can be specified in the JBoss deployment descriptor and the service can thus be started more efficiently.
• DelegatingHandler: DelegatingHandler waits for predefined elements and, if encountered, installs associated handlers on the HandlerStack .
• SitemapParams: This class provides is a simple extension of HashMap > HashMap . Its only purpose is to provide a distinct type that can be used in the parameter list of a handler method.
• ServiceUnavailableException: This exception is thrown by the newUserPrefsService 55 method of UserPrefsServiceFactory .
| Home | Contact Us | Privacy Policy | Terms of Service |