| Home >> All |
Page 1 2
| • | de.caffeine.* (22) | • | de.cgarbs.* (14) | • | de.danet.* (267) |
| • | de.hampelratte.* (9) | • | de.hunsicker.* (300) | • | de.jadv.* (122) |
| • | de.larsrohleder.* (8) | • | de.laures.* (106) | • | de.mhu.* (26) |
| • | de.nava.* (122) | • | de.vdheide.* (29) | • | de.zeigermann.* (12) |
| • | demo.chapters.* (20) | • | demo.eo.* (9) |
Package Samples:
• de.hunsicker.jalopy.swing.syntax: Provides some building blocks to make implementing a Swing-based, graphical user interface for the Jalopy code convention settings easy.
• 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.hunsicker.jalopy.swing: Contains the main classes to directly interact with the Jalopy formatting engine.
• de.hunsicker.jalopy: Contains the main classes to directly interact with the Jalopy formatting engine.
• 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.hunsicker.jalopy.language: Contains all classes related to the task of language recognition and processing.
• de.hunsicker.jalopy.plugin: Supplies the Plug-in hook for the integration with other Java applications.
• de.hunsicker.jalopy.storage: The Jalopy runtime and persistant state storage and configuration facility.
• de.laures.cewolf.util: Servlet based framework to render charts into a client's response stream.
• de.hunsicker.jalopy.plugin.jedit.option: Contains the jEdit Plug-in.
• de.hunsicker.jalopy.printer: Provides classes and interfaces for handling the AST output.
• de.laures.cewolf.taglib.util: Framework classes for the tag library implementation.
• de.hunsicker.util.concurrent: Contains miscellaneous utility and helper classes.
• de.hunsicker.util: Contains miscellaneous utility and helper classes.
• de.zeigermann.xml.simpleImporter: XML utility and helper classes
• de.hunsicker.io: Contains I/O related stuff.
• de.hunsicker.swing.util: Contains GUI related stuff.
Classes:
• SwingWorker: An abstract class that you subclass to perform GUI-related work in a dedicated thread. This class was adapted from the SwingWorker written by Hans Muller and presented in "Using a Swing Worker Thread" in the Swing Connection - http://java.sun.com/products/jfc/tsc/articles/threads/threads2.html A closely related version of this class is described in "The Last Word in Swing Threads" in the Swing Connection - http://java.sun.com/products/jfc/tsc/articles/threads/threads3.html This SwingWorker is a ThreadFactoryUser and implements Runnable. The default thread factory creates low-priority worker threads. ...
• 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 ...
• Validation: This class provides an simple framework for http parameter validation, useful in java servlets, jsp pages (using taglibs) and other java based application with the need of validation of parameters before processing. It comes with common validation cases, which can be extended with appropriate validations by implementing validator interface. Design of these classes was lead by the feeling that implementation of validation and processing of validation results have to be separated and plugable. It contains three basic elements Validator which carry out validation as simple and encapsulated operations, ...
• 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 ...
• SimpleImporter: Simple and fast importer for XML configuration or import files. It is based on SAX and can be considered an extension to it. This means it is callback oriented and does not build an internal data structure like the DOM. While SAX is simple, fast, and memory friendly it might be a bit too rudimentary for most tasks. SimpleImporter adds more high level means for importing XML while preserving the SAX's benefits. As with SAX you register a callback handler ( SimpleImportHandler ) that is called upon events. Consider the following example implementation of a SimpleImportHandler : public class DemoHandler ...
• TransportJunction: The TransportJunction is the place where Transporter s pick up the goods to move them around in a manufacturing system. The goods are normally modeled as some kind of SimProcess es. So what happens at the TransportJunction is some kind of Rendez-vous synchronisation, where Transporter s meet the goods to carry them around. There is one wait queue for the masters ( Transporter s) and one queue for the slaves ( SimProcess es), where they have to wait for each other to cooperate. The Transporter s are the masters which perform the transportation. The corporate transportation process is described in ...
• 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 ...
• Entrepot: Entrepot is some kind of storage where products (in the form of SimProcess es) can be stored. They will be stored in a kind of FIFO order, that means the products arriving first at the Entrepot will be the first ones to be removed. One can remove products from the Entrepot in order to sell (or dispatch) them or to process them in any other way. Note: while products can enter the Entrepot themselves, another process ( SimProcess ) is needed to remove the products from the Entrepot. Because the product processes are passivated while they are stored in the Entepot! The Entrepot has no capacity limit, ...
• 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 ...
• Event: Provides the superclass for user defined events to change an entity's internal state. The state of a discrete model is changed by events that occur at distinct points of simulation time. An event only acts on one entity, changing its state according to the entity's reaction to the specific event in the system under inspection. So each type of event acting on one certain type of entity reqires a new subclass to be derived from this class. Since events are associated to a single Entity, the method executing the changes of state of a specific entity gets that entity passed as a parameter. The scheduler ...
• 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 ...
• Entity: Represents the superclass for all entities of a model. Entities are supposed to be scheduled together with a compatible event at a certain point of simulation time or relative to another event in present or future simulation time. Entities typically encapsulate all information about a model's entity that is relevant to the modeller. Events can manipulate these informations when the scheduled point of simulation time is reached and thus change the state of the model. When modelling different types of entities you need to derive different classes from this superclass. Each carrying the specific information ...
• TreeWalker: Helper class to make implementing tree walkers easy. To implement a class that walks over all nodes simply dereive from TreeWalker and implement the callback method visit(de.hunsicker.antlr.collections.AST) 55 . class MyWalker extends TreeWalker { // called for every node public void visit(AST node) { System.out.println("node visited: " + node); } } If you want to control which nodes will be actually visited, overwrite walkNode(de.hunsicker.antlr.collections.AST) 55 too. // visits only IMPORT nodes and quits after the last IMPORT node found protected void walkNode(AST node) { switch (node.getType()) ...
• Processing: Processing is the object representing the processing process taking place at a WorkStation where a Worker process or a MachineProcess are processing some parts (products) to manufacture some new parts (or products). The kind and the number of parts being processed are determined by a PartsList . The parts (or products) are represented by SimProcess es. The Worker and the MachineProcess are also some kind of SimProcess es. But one Worker or MachineProcess is the master process and the other processes are all slave processes. It is intended that that this Processing is used with the WorkStation construct, ...
• XMLOutputStreamWriter: Adds XML export functionality to the underlying output stream. Formatting and encoding is done as straight forward as possible. Everything you know better than this class must be done by you, e.g. you will have to tell XMLOutputStreamWriter where you wish to have newlines.In effect, no unexpected so called intelligent behavior is to be feared. Another effect is high speed. Caution : Do not forget to call FilterWriter.flush() > FilterWriter.flush() 55 at the end of your exporting process as otherwise no data might be written. Warning : When using two byte encoding (e.g. UTF-16) underlying OutputStream ...
• CondQueue: In a CondQueue processes are waiting for a specific condition to become true. Process synchronisation happens when processes are waiting in a queue for a specific condition to become true. Each process which uses waitUntil(condition) and does not find this condition to be true, is inserted in a waiting queue automatically. Whenever something happens which might influence the condition to become true , signal() should be used to check if the first entity (or, if the attribute checkAll is set to true, all entities) in the waiting queue finds the desired condition now and therefore can continue. The ...
• 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 ...
• Jalopy: The bean-like interface to Jalopy. Sample Usage // create a new Jalopy instance with the currently active code convention settings Jalopy jalopy = new Jalopy(); File file = ...; // specify input and output target jalopy.setInput(file); jalopy.setOutput(file); // format and overwrite the given input file jalopy.format(); if (jalopy.getState() == Jalopy.State.OK) System.out.println(file + " successfully formatted"); else if (jalopy.getState() == Jalopy.State.WARN) System.out.println(file + " formatted with warnings"); else if (jalopy.getState() == Jalopy.State.ERROR) System.out.println(file + " could ...
• XMLWriter: java.io.FilterWriter adding formatted and encoded XML export functionality to the underlying writer. Formatting and encoding is done as straight forward as possible. Everything you know better than this class must be done by you, e.g. you will have to tell XMLWriter where you wish to have newlines.In effect, no unexpected so called intelligent behavior is to be feared. Another effect is high speed. A simple example: Suppose your XMLWriter object is xmlWriter. The following sequence of code xmlWriter.writeStartTag("<root>"); xmlWriter.writeStartTag("<next1>", false); ...
• FutureResult: A class maintaining a single reference variable serving as the result of an operation. The result cannot be accessed until it has been set. Sample Usage class ImageRenderer { Image render(byte[] raw); } class App { Executor executor = ... ImageRenderer renderer = ... void display(byte[] rawimage) { try { FutureResult futureImage = new FutureResult(); Runnable command = futureImage.setter(new Callable() { public Object call() { return renderer.render(rawImage); } }); executor.execute(command); drawBorders(); // do other things while executing drawCaption(); drawImage((Image)(futureImage.get())); ...
• Stock: Stock is the place where a certain kind of product can be stored by producers and retrieved by consumers. There is no difference between the units of one kind of product, the units are indistinguishable. Producers are producing products and store them using store() in the Stock. Consumers make the Stock retrieve() the products to use them up. A Stock is also providing a process synchronization between producers and consumers. If no or not enough units of a product are available for the consumers, they have to wait in a queue until new units are delivered by a producer. The Stock has a certain capacity. ...
• Res: Res is the place where resources are stored in a pool. Processes can come by and the resource pool will provide() resources to them. Each process has to give back the same resources it once has acquired by calling the takeBack() method of the Res. Res is used to implement process synchronization between processes, which are using resources. The resource pool has a limited capacity. A process can acquire one or more resources and use them. After usage the process must release this or these same resources to make them available to other processes. If a process can not get the number of resources ...
| Home | Contact Us | Privacy Policy | Terms of Service |