| Home >> All >> de >> danet >> an |
| • | de.danet.an.installdb.* (1) | • | de.danet.an.staffmgmt.* (29) | • | de.danet.an.util.* (66) |
| • | de.danet.an.webform.* (5) | • | de.danet.an.workflow.* (166) |
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.workflow.clients.c2client.library
• de.danet.an.workflow.omgcore
• de.danet.an.workflow.api
• de.danet.an.workflow.domain
• de.danet.an.workflow.spis.ras
• de.danet.an.workflow.spis.aii
• de.danet.an.workflow.spis.rms
• de.danet.an.workflow.util
• de.danet.an.workflow.engine
• de.danet.an.workflow.ejbs.admin
• de.danet.an.workflow.ejbs.util
• de.danet.an.workflow.ejbs.assignment
• de.danet.an.workflow.ejbs.core
• de.danet.an.workflow.tools.soapclient
• de.danet.an.workflow.tools.rhino
Classes:
• StandardResourceAssignmentServiceFactory: Implements a simple resource assignment service factory. Usage of this class as service factory requires an additional configuration parameter. The service factory implementation needs to connect to the assignment service EJB. In order to do so, it needs a JNDI name to look up the home interface. As JNDI names must be changeable by the application deployer, the name can't be hard coded. This factory therefore uses the following ordered lookup procedure to determine the JNDI name of the assignment service EJB home interface: Look for a name in java:comp/env/de.danet.an.workflow.assignment.assignmentService ...
• ToolAgent: This interface is used to invoke applications that execute work items. An application may implement this interface directly (it is "workflow aware"). Usually, however, this interface will be implemented by some adapter class (a.k.a. tool agent) that controls the application. An application is declared to participate in a workflow by the application tag in the XPDL. This declaration is associated with the implementation class of ToolAgent using an extension. The extension syntax supported allows to pass parameters to the constructor of the class (see the user manual for details). If parameters are ...
• StaffMgmtUserPrefsServiceFactory: Implements a user preferences service factory based on the staffmgmt package. Usage of this class as service factory requires an additional configuration parameter. The service factory implementation needs to connect to the staff directory EJB. In order to do so, it needs a JNDI name to look up the home interface. As JNDI names must be changeable by the application deployer, the name can't be hard coded. This factory therefore uses the following ordered lookup procedure to determine the JNDI name of the staff directory EJB home interface: Look for a name in java:comp/env/de.danet.an.staffmgmt.userprefs.staffDirectory ...
• 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 ...
• StaffMgmtResourceManagementServiceFactory: Implements the factory API that enables a workflow component to obtain a workflow resource management service. Usage of this class as service factory requires an additional configuration parameter. The service factory implementation needs to connect to the staff management EJBs. In order to do so, it needs a JNDI name to look up the home interface. As JNDI names must be changeable by the application deployer, the name can't be hard coded. This factory therefore uses the following ordered lookup procedure to determine the JNDI name of the staff management EJB home interface: Look for a name in java:comp/env/de.danet.an.staffmgmt.resource.staffDirectory ...
• 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 ...
• StandardWorkflowServiceFactory: Implements the workflow service factory. Usage of this class as service factory requires an additional configuration parameter. The service factory implementation needs to connect to the workflow engine EJB. In order to do so, it needs a JNDI name to look up the engine's home interface. As JNDI names must be changeable by the application deployer, the name can't be hard coded. This factory therefore uses the following ordered lookup procedure to determine the JNDI name of the workflow engine EJB home interface: Look for a name in java:comp/env/de.danet.an.workflow.Engine . The configuration for ...
• WfRequester: WfRequester is the interface that has a direct concern with the execution and results of a workflow process. It represents the request for some work to be done. Its performer, a WfProcess is expected to handle its request and communicate significant status changes; in particular to inform the requester when it has completed performing the request work. The support of WfRequester s in a workflow engine implementation is complicated because the receiveEvent 55 method reverses the client server relationship and because an object from the application space must be stored by the server. Implementations ...
• 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 ...
• InstallDB: This class create a database and can called with three parameters: java -jar installdb [-v] [-convert <database type>] [<install script> [resource script]] -v - the SQL statements should be printet on standard out. -convert - the database type as driver class name(org.hsqldb.jdbcDriver, oracle.jdbc.driver.OracleDriver, ...). It is used for searching a property file with the convert rules of the standard SQL datatypes to the specific datatypes of the vendor-specific database. install script - contains the path and file name to the file with sql database creating commands. resource script ...
• StaffMemberLoginModule: A login module that uses methods from the staff management package to authenticate the users. The resulting LoginContext has as CallerPrincipal " StaffManagementMember DBId " where DBId is the primary key of the StaffManagementMember . Every authenticated user has a default role " Danet StaffMgmt Member " assigned. Additional roles are derived from the group memberships of the authenticated member. Groups with primary keys less than 100 have role names " StaffManagementGroup DBId " where DBId is the primary key of the StaffManagementGroup . For other groups the group name is used directly as role ...
• DefaultRequester: This class provides an implementation of a WfRequester > WfRequester . It class may be used directly if the events that are usually delivered to a requester are of no interest. If events are to be processed, DefaultRequester must be subclassed with receiveEvent 55 overridden with the event handling code. As an alternative to subclassing, a handler may be passed to the constructor 55 . Events will then be forwarded to the handler. This is convenient in situation where the implementation of WfAuditHandler > WfAuditHandler already exists and a subclass would only do the forwarding. Note that the reference ...
• ResourceSupport: This class provides the standard implementation of the WfResource > WfResource methods workItems > workItems 55 , isMemberOfWorkItems > isMemberOfWorkItems 55 and release > release 55 . The class uses the ResourceAssignmentServiceFactory > ResourceAssignmentServiceFactory as described in de.danet.an.workflow.spis.rms . The class caches the resource factory obtained from the first call to ResourceAssignmentServiceFactory.newInstance() > ResourceAssignmentServiceFactory.newInstance() 55 .
• ResourceAssignmentService: This interface defines the resource assignment facility used by the workflow component. A central design issue for this interface is the identification of activites. The key method > key method 55 of WfActivity is by definition only unique within the scope of the containing process and can thus not easily be used to identify a single activity in a workflow engine. Even worse, a resource assignment service might be used by more than one workflow engine. The activity is therefore identified by an ActivityFinder and an identifier that is unique with respect to the ActivityFinder . The ActivityFinder ...
• 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 ...
• ActivityFinder: This interface defines facilities that map activity ids to WfActivity > WfActivity objects. ActivityFinders are used (in combination with an identifier) to identify activities in calls to a ResourceAssignmentService . They are guaranteed to be serializable objects with properly implemented equals > equals 55 and hashCode > hashCode 55 methods. It is expected that resource assignment facilities keep a peristent, indexed record of ActivityFinder s and store references to activities as tuples of a finder index and an activity identifier.
• ProcessDataWithParams: This class is used to return the results from a sub-process invocation to the invoking activity. There is a nasty problem in doing this which is solved by this class. In order to merge the results properly, the calling activity must know the formal parameters of the called process. All it does know, however, are the package and process ids of the called process, it does not record the key of the called process. While normally the package and process ids may be used to lookup the process definition and retrieve the formal parameters, it may happen that the process definition of the called process ...
• 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.
• SAXEventBuffer: This interface is implemented by classes that can provide XML content by emitting SAX events. Applications that use XML at their interfaces can sometimes not avoid using XML like data structures for internal data representation. Holding this data as XML is not very time efficient, because it must be parsed in order to be processed (although parsing time for XML is often overestimated). Holding the data in either W3C DOM or JDOM representations is not very memory efficient. Depending on the implementation, DOM representations use a factor of 6 to 10 compared with the file space of the same description. ...
| Home | Contact Us | Privacy Policy | Terms of Service |