| Home >> All >> org >> jdaemon |
| • | org.jdaemon.era.* (69) | • | org.jdaemon.six.* (8) | • | org.jdaemon.test.* (8) | • | org.jdaemon.util.* (54) |
Package Samples:
• org.jdaemon.era
• org.jdaemon.era.java
• org.jdaemon.era.six
• org.jdaemon.era.sql
• org.jdaemon.era.xml
• org.jdaemon.era.xml.alt
• org.jdaemon.six
• org.jdaemon.test.era
• org.jdaemon.test.sql
• org.jdaemon.util
• org.jdaemon.util.data
• org.jdaemon.util.data.jndi
• org.jdaemon.util.data.xml
• org.jdaemon.util.formats
• org.jdaemon.util.iterator
• org.jdaemon.util.jndi
• org.jdaemon.util.resource
• org.jdaemon.util.sql
• org.jdaemon.util.xml
Classes:
• Type: Mechanism for persisting Java objects in a DataRepresentation. The Type object allows Java objects to be both retrieved from and written to a DataRepresentation. A single Type object provides a mapping between the element type stored in a DataRepresentation and the class of a java object. For instance a java object of class 'org.jdaemon.Polygon' might have an element type of 'POLYGON'. In addition, Type has two abstract methods (read and write) which must be implemented in order to define the exact mapping between fields of a java class and attributes of an element representing that class in a ...
• ReportBuilder: ReportBuilder provides utility methods for creation of report documents. Generally ReportBuilder will be used to create XML documents. A number of XML element types are implicitly defined by the ReportBuilder API: report header row group cell sort free-text These element types are primarily morphological in as much as they define how documents generated by ReportBuilder are laid out: For example, header elements can contain header-row elements but not datum elements. Most of these elements also support a class attribute. This allows element types which have the same morphological characteristics ...
• DataRepresentation: Uberinterface for properties files, directory data, XML config, etc. A DataRepresentation object represents two things: a named collection of simple attributes, and a named collection of child DataRepresentations (aka Elements). In addition, each DataRepresentation has a 'Type' value which can be retrieved through the getElementType method. This paradigm works well for both data held in XML files and data held in JNDI directories. (Indeed, the API of DataRepresentation can be thought of as the lowest common denominator between the JNDI and DOM interfaces). In the case of XML, a DataRepresentation ...
• AggregatingIterator: Abstract class for generating aggregate data from a collection To create a concrete subclass of AggregatingIterator beginGroup should be implemented to return a 'zero' value for aggregate data addToGroup should be implemented to add a value from the underlying collection to the aggregate For example, if beginGroup returns new Integer(0), and the underlying collection contains instances of a an employee class with name, department, and salary fields, addToGroup() could be implemented to add the salary from an employee object to the total. Then if the Comparator object given to the AggregatingIterator ...
• DescriptorBuilder: Interface for outputting Report metadata in order to dynamically build a stylesheet. Although a given report can be rendered by a static stylesheet, the limitations of XSL make it difficult to create a single stylesheet that will render a large variety of different reports. For instance, simple tasks like hiding a column of data require either that the name of the column be hardwired into the stylesheet, or that we use some non-standard XSL features. We solve this problem instead by defining a report metadata language that can be rendered into a stylesheet using XSL. In essence, we use a meta-stylesheet ...
• Builder: Builder is an interface for the dynamic creation of complex document structures Although Builder is oriented towards creating XML-style documents, in principle it can be used for creating arbitrary document types. The document model that 'Builder' implicitly defines is similar, but not identical to, the XML document model. As in XML, a document is comprised of a tree of elements. Elements have a type string, which is equivalent to the XML tag. Elements can have attributes, also like XML. Elements can also contain 'content'. Unlike XML, the content of an element is not assumed to be textual. Instead, ...
• Cube: Interface to support generic slicing-and-dicing of data using an OLAP cube metaphor. A cube contains a collection of data items of some type (In principle any java object). Each object within the collection is assumed to have a set of named attriubutes; Subsets of this data collection can be generated either through an arbitrary filtering mechanism or through placing standardised constraints on object attribute values.
• IndexedJavaCube: A JavaCube which is indexed on a single attribute An IndexedJavaCube maintains data objects arranged into groups according to the value of a particular 'key' attribute. Each group contains objects which have the same value of the key attribute. These groups can be rapidly accessed with the 'getGroup' method, and a 'groups' iterator is provided which allows each group to be visited in turn.
• GenericTotal: This is a helper class used for inserting totals after groups breaks. This class is used by XMLCube for totaling non numeric fields for each report. The group breaks and columns which need to be totaled are passed in as an argument. The class accepts a Document object for XML and arrays for group list and total columns. The first group should be the first element in the groupby arrray
• QuickList: A quick-and-dirty LISP-style list class. QuickList differs from the List Collection in as much as once created, a QuickList does not change. New elements are added to a QuickList by creating a new QuickList which includes both the new element and the old QuickList. This makes QuickList suitable for generating low-overhead temporary data structures (amongst other things).
• Accessor: An adapter interface which allows attributes of an object to be accessed via standard methods. Attributes must have name through which they can be accessed. Accessor provides a way of getting an attribute value (getAttribute) and setting and attribute value (setAttribute). It explicitly does not provide any way to add new attributes to an object.
• AttributeList: Simple class for dynamically created list of Name/Value pairs. This class is optimised for fast creation rather than fast searches; Currently implemented using QuickList. However note that, like QuickList, adding an entry to an AttributeList does not change the original list, but rather returns a new list which has the additional element added.
• AbstractJavaCube: AbstractJavaCube JavaCubes delegate their getAttribute() and getComparator() methods to their descriptor object (which will be a JavaCubeDescriptor rather than a simple CubeDescriptor). This is because the data structures supporting these methods will be invariant across all cubes having the same descriptor.
• MapEntryConverter: Iterator that converts data into map entry objects If o is an object returned by the next() method of iterator i, And j = new MapEntryConverter(i), then j.next() will return an object e supporting the Map.Entry interface. e.getKey() and e.getValue() will both return o
• AbstractCubeDirectory: Base implementation for cube directories Assumes an index of cubes exists on a given attribute set. Implements getCube and getValues in terms of abstract operations on this index. Note: At some stage this implementation should be extended to handle multiple indexes
• BeanAccessor: Accessor which allows items stored in a bean-like object to be given symbolic names. Every symbolic name will have to have a corresponding 'get' method. For example, an attribute AccountName will have to have a corresponding getAccountName method.
• AbstractXMLCube: Abstract implementation of XMLCube. Extends AbstractCube (for completeness -- even though it does not reuse much -- may have to revise this class or AbstractCube). Note that AbstractCube more closely matches the requirements of the JavaCube than the XMLCube.
• BuilderDelegator: A Builder instance that delegates all calls to some other Builder (the delegate). This class is used as a base for other classes that enrich the functionality of some other builder. In itself it provides no worthwhile functionality.
• GroupAggregatingIterator: Iterator that will group data into Cubes. This is a package-level class because it is heavily dependent on certain implementation details of SQLCube and JavaCube, so not generally suitable for use elsewhere.
• SimpleCubeDescriptor: Simple Cube Descriptor class to be used for Cubes other than xml, java or sql Cubes, e.g. for existing Business Object classes that extend the Cube interface. (Adapted from JavaCubeDescriptor)
• CompoundIterator: Takes two iterators and turns them into a single iterator Elements in the enumeration A will be returned until there are none left; After that, elements in the enumeration B will be returned.
• TestConnection: Dummy implementation of java.sql.Connection for testing purposes Implementation is currently pretty skeletal; could easily be fleshed out in order to make this class more useful.
• NTree: Interface for N-dimensional trees 1 dimensional tree is a binary tree 2 dimensional tree is a quadtree 3 dimensional tree is an octree 4+ dimensions is a hyper-quadtree
• Filter: A general purpose predicate object. Filter is a predicate which can be used to define a sub-selection of objects in a Cube using the Cube's constrain(filter) method.
| Home | Contact Us | Privacy Policy | Terms of Service |