Home >> All >> org >> jbpm >> [ util Javadoc ]

•	org.jbpm.util.ant.* (3)	•	org.jbpm.util.aspect.* (2)	•	org.jbpm.util.cache.* (4)
•	org.jbpm.util.client.* (3)	•	org.jbpm.util.db.* (8)	•	org.jbpm.util.ejb.* (4)
•	org.jbpm.util.experimental.* (19)	•	org.jbpm.util.file.* (4)	•	org.jbpm.util.msg.* (1)
•	org.jbpm.util.sequence.* (3)	•	org.jbpm.util.tcp.* (1)	•	org.jbpm.util.test.* (1)
•	org.jbpm.util.xml.* (3)

• org.jbpm.util: Javadoc index of package org.jbpm.util.


Package Samples:

• org.jbpm.util.experimental.container.lifecycle: This container specification is a runtime environment for loosely coupled components.  
• org.jbpm.util.ant
• org.jbpm.util.sequence.impl
• org.jbpm.util.sequence
• org.jbpm.util.experimental.container.impl
• org.jbpm.util.experimental.container
• org.jbpm.util.msg
• org.jbpm.util.db
• org.jbpm.util.xml
• org.jbpm.util.file
• org.jbpm.util.cache
• org.jbpm.util.tcp
• org.jbpm.util.ejb.impl
• org.jbpm.util.test
• org.jbpm.util.client
• org.jbpm.util.aspect

Classes:

• Relations: specifies which related objects should be resolved for data-transfer-objects, returned from a session-facade. A session facade is supposed to collect data from the persistency-layer and return data-transfer-objects to the client. If the datamodel has a lot of relations, a problem arises : Which related objects should be resolved in the object that is returned to the client. A Relations-object is a convenient way of specifying which related objects you want to be resolve on the objects returned by the session facade. You can specify these Relations with dot-separated property-names. E.g. if the ...
• Configuration: contains the configurations as specified within a configuration-element inside the configuration.xml. The 'path' parameter is a dot-separated hierarchical name. The hierarchy corresponds with the xml-nesting. E.g. path one.two.three could correspond with <one> <two> <three> --this is the value-- </three> </two> </one> Alternatively, XPath could be used for this, I think.
• Aspect: is a decorator for services, also known as interceptor (jboss) or filter (servlets). An Aspect-implementation must have the following constructor : Constructor( Container, Configuration ) throws DependancyException, ConfigurationException; Aspects can be chained. Note that in a chain the postInvocations are called in the opposite order then the preInvocations.
• DbSession: This class wraps the Hibernate Session. It adds the guarantee that if a method throws an exception, the session will already be closed. Furthermore, this wrapper adds 2 convenience-methods findOne(...) and iterateOne(...) that checks if exactly one object is returned and extracts that single object from the collection.
• TcpProxy: This is a modified version of the TcpTunnelGui utility borrowed from the xml.apache.org project. A TcpTunnelGui object listens on the given port, and once Start is pressed, will forward all bytes to the given host and port. All traffic is displayed in a UI.
• InvalidServiceNameException: is thrown when a ServiceMgr tries to publish a service with an invalid name. A serviceName is invalid if another published service is already assigned the same name or if the serviceName contains illegal characters as described in Container#publishService.
• DependancyException: is thrown when a ServiceMgr could not create its services because it needed another service which it couldn't retrieved from the container
• RemoveListener: allows any interested party to handle service- and aspect-dependancies. Interested parties could be servic-objects's, Aspect's, ...
• DbType: This class wraps all the hibernate types so that users of this package don't have to include the net.sf.hibernate packages.
• ServiceInvocation: contains all information related to a service method invocation that could be needed by an Aspect-implementation.
• SequenceSessionBean: SequenceSessionBean is part of an id-generation strategy. It allocates a new block of id's for the client.
• ArrayUtil: is a utility class for common Array-methods that are not available in the system libraries.
• ServiceUnavailableException: is thrown by the container when a service is requested that is not published.
• Service: allows the service-user to obtain a service implementation object.
• Deployer: The deployer takes a service archive and deploys it.
• Removable: is an object that can be removed from the Container.
• LoginUtil: provides utilities for remote application clients.
• Configurable: is an object which can be configured.
• Container: manages a collection of services.
• IoUtil
• DeployProcess
• DeployProcessTask
• StartJBossTask
• AspectChain

Home | Contact Us | Privacy Policy | Terms of Service