| Home >> All >> org >> [ jboss Javadoc ] |
Page 1 2 3
| • | org.jboss.jetty.* (14) | • | org.jboss.jms.* (10) | • | org.jboss.jmx.* (60) |
| • | org.jboss.logging.* (21) | • | org.jboss.mail.* (1) | • | org.jboss.management.* (106) |
| • | org.jboss.metadata.* (26) | • | org.jboss.monitor.* (9) | • | org.jboss.mq.* (225) |
| • | org.jboss.mx.* (120) | • | org.jboss.naming.* (14) | • | org.jboss.net.* (101) |
| • | org.jboss.netboot.* (1) | • | org.jboss.odmg.* (2) | • | org.jboss.ojb.* (4) |
• org.jboss: Javadoc index of package org.jboss.
Package Samples:
• org.jboss.net.axis.server: This package contains server- as well as client-side glue code to integrate the Axis project into JBoss.
• org.jboss.net.jmx.server: This package hosts XML-interoperability code especially for the JMX-API.
• org.jboss.net.jmx.adaptor.server: The JMX connector exports the JMX API as a web-service itself.
• org.jboss.jms.asf: Provides support for the Java Message Service (JMS).
• org.jboss.jms.jndi: Provides support for the Java Message Service (JMS).
• org.jboss.mx.util.propertyeditor: Utilities for the Java Management Extentions API.
• org.jboss.net.axis: This package hosts the source of the JBoss.net module.
• org.jboss.net.taglib: This package hosts the source of the JBoss.net module.
• org.jboss.mx.logging.log4j: The JBossMX logging framework .
• org.jboss.monitor.client: Package description goes here .
• org.jboss.naming.java: Package description goes here .
• org.jboss.management.j2ee.statistics: Package description goes here .
• org.jboss.logging.layout: Common logging infrastructure.
• org.jboss.logging.util: Common logging infrastructure.
• org.jboss.net.protocol.resource: URL protocol stream helpers.
• org.jboss.ojb.pb
• org.jboss.ojb.odmg
• org.jboss.net.protocol.jndi
• org.jboss.mq.il.ha
• org.jboss.logging.appender
Classes:
• MIME2Java: MIME2Java is a convenience class which handles conversions between MIME charset names and Java encoding names. The supported XML encodings are the intersection of XML-supported code sets and those supported in JDK 1.1. MIME charset names are used on xmlEncoding parameters to methods such as TXDocument#setEncoding and DTD#setEncoding . Java encoding names are used on encoding parameters to methods such as TXDocument#printWithFormat and DTD#printExternal . Common Name Use this name in XML files Name Type Xerces converts to this Java Encoder Name 8 bit Unicode UTF-8 IANA UTF8 ISO Latin 1 ISO-8859-1 ...
• LdapLoginModule: An implementation of LoginModule that authenticates against an LDAP server using JNDI, based on the configuration properties. The LoginModule options include whatever options your LDAP JNDI provider supports. Examples of standard property names are: Context.INITIAL_CONTEXT_FACTORY = "java.naming.factory.initial" Context.SECURITY_PROTOCOL = "java.naming.security.protocol" Context.PROVIDER_URL = "java.naming.provider.url" Context.SECURITY_AUTHENTICATION = "java.naming.security.authentication" The Context.SECURITY_PRINCIPAL is set to the distinguished name of the user as obtained by the callback handler ...
• StateMachine: A generalization of a programmable finite-state machine (with a twist). A state machine is backed up by a StateMachine.Model which simply provides data encapsulation. The machine starts in the initial state, which must not be null. Care must be taken to ensure that the machine state is not corrupted due to invalid modifications of the model. Best to leave the model alone once the machine has been created. Provides change notification via StateMachine.ChangeListener objects. When a listener throws an exception it will not corrupt the state machine; it may however corrupt any application state which ...
• AbstractWebContainer: A template pattern class for web container integration into JBoss. This class should be subclasses by web container providers wishing to integrate their container into a JBoss server. It provides support for mapping the following web-app.xml/jboss-web.xml elements into the JBoss server JNDI namespace: - env-entry - resource-ref - resource-env-ref - ejb-ref - ejb-local-ref - security-domain Subclasses need to implement the performDeploy() and performUndeploy() 55 methods to perform the container specific steps and return the web application info required by the AbstractWebContainer class. Integration ...
• TxConnectionManager: The LocalTxConnectionManager is a JBoss ConnectionManager implementation for jca adapters implementing LocalTransaction support. It implements a ConnectionEventListener that implements XAResource to manage transactions through the Transaction Manager. To assure that all work in a local transaction occurs over the same ManagedConnection, it includes a xid to ManagedConnection map. When a Connection is requested or a transaction started with a connection handle in use, it checks to see if a ManagedConnection already exists enrolled in the global transaction and uses it if found. Otherwise a free ...
• LocalTxConnectionManager: The LocalTxConnectionManager is a JBoss ConnectionManager implementation for jca adapters implementing LocalTransaction support. It implements a ConnectionEventListener that implements XAResource to manage transactions through the Transaction Manager. To assure that all work in a local transaction occurs over the same ManagedConnection, it includes a xid to ManagedConnection map. When a Connection is requested or a transaction started with a connection handle in use, it checks to see if a ManagedConnection already exists enrolled in the global transaction and uses it if found. Otherwise a free ...
• HTTPClient: Utility class that provides HTTP functionality. This class is modeled after Scott's Util class in org.jboss.invocation.http.interfaces.Util, however, that class deals with Invocation object, while this handles HTTPILRequest objects. Other then that, it is a pretty close reproduction. Concerning SSL, like Scott's Util class, a check is performed at run time to determine if the connection is the JSSE 1.0.2 package (i.e. the connection is an instance of com.sun.net.ssl.HttpsURLConnection). If so, the system properties are queried to see if the org.jboss.security.ignoreHttpsHost value is set to true. ...
• JmsManagedConnection: Managed Connection, manages one or more JMS sessions. Every ManagedConnection will have a physical JMSConnection under the hood. This may leave out several session, as specifyed in 5.5.4 Multiple Connection Handles. Thread safe semantics is provided Hm. If we are to follow the example in 6.11 this will not work. We would have to use the SAME session. This means we will have to guard against concurrent access. We use a stack, and only allowes the handle at the top of the stack to do things. As to transactions we some fairly hairy alternatives to handle: XA - we get an XA. We may now only do transaction ...
• XATxConnectionManager: The XATxConnectionManager connection manager has to perform the following operations: 1. When an application component requests a new ConnectionHandle, it must find a ManagedConnection, and make sure a ConnectionEventListener is registered. It must inform the CachedConnectionManager that a connection handle has been given out. It needs to count the number of handles for each ManagedConnection. If there is a current transaction, it must enlist the ManagedConnection's XAResource in the transaction. Entry point: ConnectionManager.allocateConnection. written. 2. When a ConnectionClosed event is received ...
• CompatibilityTool: This is a compatibility tool, used to either generate serialized files from loaded classes, or to test loaded classes against serialized files for backwards compatibility. In order to get backwards compatibility, classes that are "contract" classes need to support the java serialization api and how this works with compatibility. This tool uses the following syntax: java org.jboss.compatibility.CompatibilityTool make|check fully-qualified-class-name1,... make: Creates serialized versions of the fq classes given as arguments check: Verifies class files by loading them into the classloader and then ...
• TopologyMonitorService: A cluster parition membership monitor. It can be used to view how the nodes in a cluster are seeing the topology change using either email or a centralized log server. To use this to send email on change notifications use the following log4j.xml fragments: You can also have this service notify another MBean of the change to perform arbitrary checks by specifying the MBean name as the TriggerServiceName attribute value. This MBean must have an operation with the following signature: param: removed ArrayList of nodes that were removed param: added ArrayList of nodes that were added param: members ...
• XElement: XElement provides an interface to an XML element. An XElement represents an XML element which contains: Name (required) Attributes (optional) character data (optional) other elements (optional) It is important to understand the diffrence between an "field" XElement and a non "field" XElement. If an XElement does not contain any sub elements, it is considered a "field" XElement. The getField(String) and getValue() functions will throw an XElementException if they are used on non "attribute" objects. This give you a little bit type checking (You'll get an exception if you try to access the character ...
• EVENT_TRACE: A trival implementation of Protocol that traces all activity through * it to its logger. This should be inserted between any two protocols * you which to view the events between. Its supports a name property that * allows you to insert the element multiple times in a stack to trace * multiple protocols. An example config for the ClusterPartition for such * a usage is: * JNDITestPartition * @author Scott.Stark@jboss.org * @version $Revision: 1.1.4.4 $
• Connection: This class implements javax.jms.Connection. It is also the gateway through wich all calls to the JMS server is done. To do its work it needs a ServerIL to invoke (@see org.jboss.mq.server.ServerIL). The (new from february 2002) logic for clientID is the following: if logging in with a user and passwork a preconfigured clientID may be automatically delivered from the server. If the client wants to set it's own clientID it must do so on a connection wich does not have a prefonfigured clientID and it must do so before it calls any other methods on the connection (even getClientID()). It is not allowable ...
• NonSerializableFactory: A utility class that allows one to bind a non-serializable object into a local JNDI context. The binding will only be valid for the lifetime of the VM in which the JNDI InitialContext lives. An example usage code snippet is: // The non-Serializable object to bind Object nonserializable = ...; // An arbitrary key to use in the StringRefAddr. The best key is the jndi // name that the object will be bound under. String key = ...; // This places nonserializable into the NonSerializableFactory hashmap under key NonSerializableFactory.rebind(key, nonserializable); Context ctx = new InitialContext(); ...
• TrapFactorySupport: TrapFactorySupport takes care of translation of Notifications into SNMP V1 and V2 traps Data Structure Guide It looks complicated but it ain't. The mappings are read into a structure that follows the outline defined in the Notification.xsd. Have a look there and in the example notificationMap.xml and you should get the picture. As an optimization, 2 things are done: 1. The "NotificationType" fields of all the mappings are read, interpreted and compiled as regular expressions. All the instances are placed in an array and made accessible in their compiled form 2. The "wrapperClass" attribute is interpreted ...
• MBeanServerImpl: MBean server implementation. This is the default server implementation returned by the MBeanServerFactory class ( DEFAULT_MBEAN_SERVER_CLASS 55 ). The MBean server behaviour can be further configured by setting the following system properties: jbossmx.loader.repository.class ( LOADER_REPOSITORY_CLASS_PROPERTY 55 ) jbossmx.mbean.registry.class ( MBEAN_REGISTRY_CLASS_PROPERTY 55 ) jbossmx.required.modelmbean.class ( REQUIRED_MODELMBEAN_CLASS_PROPERTY 55 ) The loader repository is used for managing class loaders in the MBean server. The default repository uses the BasicLoaderRepository implementation ...
• JDBCOptimisticLock: This class is an optmistic lock implementation. It locks tableFields and their values during transaction. Locked tableFields and their values are added to the WHERE clause of the UPDATE SQL statement when entity is stored. The following strategies are supported: - fixed group of tableFields Fixed group of tableFields is used for locking . The tableFields and their values are locked at the beginning of a transaction. The group name must match one of the entity's load-group-name. - modified strategy The tableFields that were modified during transaction are used as lock. All entity's field values ...
• Boot: Starts multiple applications using seperate classloaders. This allows multiple applications to co-exist even if they typicaly could not due to class version problems. Each application is started in it's own thread. Usage is Boot [-debug] -cp app-classpath app-class-name app-arguments ( , -cp app-classpath app-class-name app-arguments )* Where: app-classpath is a comma seperated URL form classpath to the application classes. app-class-name is the class that will be started app-arguments will be the String[] that will be passed to the main method of the application class Jboss + Another Application ...
• HTTPClientILService: The HTTP/S implementation of the ClientILService object. One of these exists for each Connection object. Normally, this would be where you would boot up a client-side listener for the server to invoke. However in this case, we poll the server instead. In short, the ClientIL that we provide, once serialized and shipped to the server, simply places requests the server makes to it in a server-side storage mechanism. Then, when we send an HTTP request to the server, the servlet looks for queued requests waiting for us, batches them up and returns them in the response. Since we place ALL requests delivered ...
• EJBProvider: A JBoss-compatible EJB Provider that exposes the methods of any session bean as a web service endpoint. Basically it is a slimmed downed derivative of the Axis-EJBProvider without the usual, corba-related configuration mumbo-jumbo that is operating under the presumption that the right classloader has already been set by the request flow chain (@see org.jboss.net.axis.SetClassLoaderHandler). Since Version 1.5 and thanks to Kevin Conner, we now also support stateful beans that are tied to the service scope (you should reasonably choose scope="session" in the tag of the corresponding web-service.xml) ...
• EJBTestRunner: The remote interface of the server side test runner. The EJBTestClient calls run with the names of the test class and test method to execute. Then run calls setUpEJB, runTestCase, and tearDownEJB in sepperate transactions. In order for the the tests to run as expected by the client the EJBTestRunner bean must be setup exactly as follows in the ejb-jar.xml file: <?xml version="1.0"?> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd"> <ejb-jar> <enterprise-beans> <session> <description>JUnit ...
• AuthenticatorBase: Overrides the superclass version by using class org.jboss.web.tomcat.tc4.authenticator.SingleSignOn instead of org.apache.catalina.authenticator.SingleSignOn as its method expected single sign-on valve. This class also differs from the standard Tomcat version in its implementation of method reqister 55 . Basic implementation of the Valve interface that enforces the <security-constraint> elements in the web application deployment descriptor. This functionality is implemented as a Valve so that it can be ommitted in environments that do not require these features. Individual implementations ...
• InvocationHandler: An invoker is a target of method calls, where the calls are expressed not as primitive Java method invocations, but according to the conventions of the Core Reflection API. Invokers are designed to be used along with the Core Reflection API. The Invoker.invoke operation is similar to java.lang.reflect.Method.invoke, except that the object (or objects) which receives the message is hidden behind the invoker. Also, unlike Method.invoke, the action of the Invoker.invoke operation is completely under programmer control, because Invoker.invoke is an interface method, not a native method. You can wrap ...
• 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 ...
| Home | Contact Us | Privacy Policy | Terms of Service |