| Home >> All >> org >> jboss >> varia |
Package Samples:
• org.jboss.varia.scheduler.example: Schedular components.
• org.jboss.varia.autonumber
• org.jboss.varia.counter
• org.jboss.varia.deployment.convertor
• org.jboss.varia.deployment
• org.jboss.varia.process
• org.jboss.varia.property
• org.jboss.varia.scheduler
• org.jboss.varia.dsdelegator
Classes:
• DBScheduleProvider: This Provider get its Scheduler from a Database and then adds all the Schedules to the Schedule Manager. The "SQL Statement" must deliver the following attributes: Index Content Data Type ---------------------------------- 1., Target, String 2., Method_Name, String 3., Method_Signature, String 4., Start_Date, String 5., Period, long 6., Repetitions, int 7., Date_Format, String ATTENTION: The "Target" is Object Name of the target MBean as String, the "Method_Signature" is a list of attributes separated by colons which can contain: NOTIFICATION which will be replaced by the timers notification instance ...
• CounterInterceptor: Interceptor that uses the CounterService MBean to record the length of time spent in 'lower' interceptors (below it in the stack). How to use: First, the CounterService MBean must be installed in JBoss. See counter-service.xml for details/examples. Next, you need to configure this interceptor into the interceptor stacks of any beans you wish to monitor. This can be done either globally for a container-config in standardjboss.xml, or on a per-bean basis in a jar's jboss.jcml. Just insert the following at the top of the <container-interceptors> section. If you're overriding this for a bean ...
• JarTransformer: JarTransformer is used to transform passed in jar file. Transformation algorithm: 1. open JarInputStream on passed in Jar file, open JarOutputStream for result; 2. read next Jar entry; 3. check whether Jar entry is an XML file - if it's not, copy Jar entry to result and go to step 2. 4. check whether there is an XSL file with name equal to XML file's in classpath. - if there isn't, copy Jar entry to result and go to step 2. 5. check whether there is a properties file with the name equal to XML file's name + "-output.properties" 6. set needed xsl parameters 7. transform Jar entry with xsl template ...
• AbstractScheduleProvider: Abstract Base Class for Schedule Provider. Any Schedule Provider should extend from this class or must provide the MBean Interface methods. This class is cluster aware and allows the use of the HASingleton MBean attribute to control whether or not it should run as a singleton service or not. When HASingleton is set to true the MBean will usually declare dependency on a cluster partition. When not explicitly set the attribute defaults to false.
• Scheduler: Scheduler Instance to allow clients to run this as a scheduling service for any Schedulable instances. ATTENTION: The scheduler instance only allows to run one schedule at a time. Therefore when you want to run two schedules create to instances with this MBean. Suggested Object Name for the MBean are: :service=Scheduler,schedule= This way you should not run into a name conflict.
• XMLScheduleProvider: This Provider get its Scheduler from a XML configuration string allowing the administrator to add several Schedules with one provider. The "Schedules" properties has to look like:
• DataSourceDelegator: DataSource delegator service. The goal is to dynamically change the datasource, for example, for entity beans at runtime. The service implements javax.sql.DataSource interface and is bound in the JNDI. The target datasource can be changed with setTargetName(String jndiName) passing in the JNDI name of the target datasource.
• ScheduleManager: Schedule Manager which manage the Schedule and their matching Timer notifications and notification listeners. Each provider has to register when it is started where in turn their startProviding() method is called which allows him to add its Schedules because the Manager is now ready.
• SingleScheduleProvider: This Provider adds a single Schedule to the Schedule Manager but you can create more than one of this MBeans and each will add a different Schedule even when the use the same Target. ATTENTION: This is the provider you used in the older Scheduler when you used a MBean as target.
• Schedulable: This interface defines the manageable interface for a Scheduler Service allowing the client to create a Schedulable instance which is then run by this service at given times.
• FoeDeployer: This is the deployer for other vendor's applications with dynamic migration of vendor-specific DDs to JBoss specific DDs.
• BeanShellSubDeployer: A deployer that takes a bean shell script file and creates a JBoss mbean service wrapper for the script.
• CounterService: A service offering accumulator style counters to help in diagnosing performance issues.
• BeanShellScript: A wrapper service that exposes a BeanShell script as a JBoss service mbean.
• SchedulableExample: A simple Schedulable implementaion that logs when an event occurs.
• PropertyEditorManagerService: A service to access java.beans.PropertyEditorManager .
• XslTransformer: XslTransformer is a utility class for XSL transformations.
• AutoNumber: AutoNumber stores autonumbers for items in a collection.
• AutoNumberFactory: AutoNumberFactory can persistently auto number items.
• AutoNumberEJB2: The CMP 2 compatible version of AutoNumberEJB.
• SystemPropertiesService: A service to access system properties.
• ChildProcessService: A service to manage a child process.
| Home | Contact Us | Privacy Policy | Terms of Service |