JBoss In Action - Errata. EJB3 Plugin. JBoss EJB3 Plugin The EJB3 Plugin is an executable JAR which will patch an existing AS installation with the latest EJB3 binaries (and dependent projects).
EncryptingDataSourcePasswords - JBoss Community. A simple login module for encrypting a datasource password The org.jboss.resource.security.SecureIdentityLoginModule can be used to encrypt database passwords rather than using clear text passwords in the datasource configuration.
It uses a hard-coded password to encrypt/decrypt the datasource password. You can encrypt the datasource password using the SecureIdentityLoginModule main method by passing in the cleartext password, here shown as 'password': Transaction Timeouts and EJB3/JPA. I recently discovered somewhat odd behavior in the way transactions are timed out in my EJB3/JPA app.
It was surprising to me how it worked, and though I guess it makes sense when thinking about it, something here still doesn't "feel right". Consider an EJB3/JPA application deployed in JBossAS 4.2 that uses the Arjuna's Transaction Manager (aka JBossTM - although I still call it Arjuna :) and Hibernate as the JPA implementation. Annotating an EJB3 stateless session bean (SLSB) method, is this: @org.jboss.annotation.ejb.TransactionTimeout(60) If my method takes longer than 60 seconds, the transaction it is running in will timeout, and thus rollback.
What I was assuming would happen is the thread running my method would get interrupted, and (assuming the JDBC driver or file IO subsystem or Thread.sleep or whatever my method was doing at the time can handle the interrupt) the method would abort with that interrupted exception and immediately begin the rollback procedures. Chapter 6. Messaging on JBoss. Chapter 6.
Messaging on JBoss JMS Configuration and Architecture The JMS API stands for Java Message Service Application Programming Interface, and it is used by applications to send asynchronous business-quality messages to other applications. In the messaging world, messages are not sent directly to other applications. Instead, messages are sent to destinations, known as queues or topics.
The JMS API is the standardized interface to a JMS provider, sometimes called a Message Oriented Middleware (MOM) system. HornetQ General FAQs - JBoss Community. What is HornetQ?
HornetQ is an open source project to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. HornetQ is designed with usability in mind. HornetQ is an example of Message Oriented Middleware (MoM) For a description of MoMs and other messaging concepts please see the chapter 2 of the user manual "Messaging Concepts". HornetQ takes over from JBoss Messaging as our premier JMS implementation.
Why a Hornet? Hornets are fast, angry and have attitude, with a sting in their tail. The HornetQ Team Blog. HornetQ Quickstart Guide. The JMS Examples all follow the same format.
Each examples is contained in its own directory which contains the following. build.xmlThis is the ant build file used to run the examplesrc directoryThis contains the source code for the exampleserver0 configuration directoryThis contains the configuration files needed to run the server for the example. There may be multiple configuration directories server0, server1 etc for clustered examples etc. Each example will start one or more stand-alone servers and stop them after the example has completed. As a quick start we'll run the queue example. Firstly open a Shell or a Command prompt and navigate to the examples/jms/queue directory. Chapter 3. Naming on JBoss. This chapter discusses the JBoss JNDI based naming service and the role of JNDI in JBoss and J2EE.
An introduction to the basic JNDI API and common usage conventions will also be discussed. The JBoss specific configuration of J2EE component naming environments defined by the standard deployment descriptors will also be addressed. The final topic is the configuration and architecture of the JBoss naming service. The JBoss naming service is an plays a key role in J2EE because it provides a naming service that allows a user to map a name onto an object. This is a fundamental need in any programming environment because developers and administrators want to be able to refer to objects and services by recognizable names. Chapter 1. Session EJB and MDB Configuration. Index of /j2ee. 5.x Tuning/Slimming - JBoss Community. The following slimming recommendations are for a standard JBoss AS 5.1.0 GA (Community) "All" configuration and can be used for Jboss EAP 5.1.0 (Enterprise).
Slimming is very application specific, so this is by no means a universal document. If you have documented the process for slimming other services for JBoss 5.x please add to them here. Slimming Remove EJB3 services In server/<node>/deploy/ remove: AS 5 FAQ - JBoss Community. Chapter 5. XML Bindings. In the last sections you saw how to code aspects and how pointcut expressions are formed.
This chapter puts it all together. There are two forms of bindings for advices, mixins, and introductions. EJB 3.0. JBoss provides a few extensions to the EJB 3.0 spec.
This chapter describes those features here. An extension offered by JBoss EJB 3.0 is the notion of a @org.jboss.annotation.ejb.Service annotated bean. They are singleton beans and are not pooled, so only one instance of the bean exists in the server. They can have both @Remote and @Local interfaces so they can be accessed by java clients. When different clients look up the interfaces for @Service beans, all clients will work on the same instance of the bean on the server. Jboss.j2ee:service=EJB3,name=<Fully qualified name of @Service bean>,type=service.
JBoss Tutorial - HermesJMS - Confluence. JBoss Enterprise Application Platform.