Book Image

Apache Geronimo 2.1: Quick Reference

Book Image

Apache Geronimo 2.1: Quick Reference

Overview of this book

Apache Geronimo is a robust, scalable, secure, and high-performing application server. But like all application servers, this power comes with a steep learning curve. This book can help you save your time and get working with Geronimo in matter of a few hours. This book is a quick-reference guide to Apache Geronimo that mitigates the starting pains that most developers have when they migrate to a new Application Server. It will help you to extend and amplify your existing development skills, empowering you to build new types of applications regardless of the platform or browser. The book will introduce you to the exciting features of Apache Geronimo Application Server. You will see how easily you can develop and deploy Java EE 5 applications on Geronimo. It covers everything from downloading the server to customizing it using custom GBeans. By following the practical examples in this book, you will be able to develop applications quickly using Geronimo Eclipse Plugin. The book covers Geronimo internals in detail, which helps you write custom services on Geronimo. Also, it helps you to gain a deep understanding of Geronimo plugin architecture and teaches you to extend your server functionality via plugins. By the end of the book, you will develop proficiency in Geronimo and Java EE 5 application development.
Table of Contents (21 chapters)
Apache Geronimo 2.1
Credits
About the Authors
About the Reviewer
Preface

Application local JNDI context


A Java EE application's local JNDI context is immutable and is only accessible by that Java EE application. The context is bound at java:comp/env for each application. It contains references to the resources and Java EE components that the application references.

Because this is an immutable context, we cannot bind anything into it programmatically by using the javax.naming.Context.bind method. However, we can specify all of the resources and components that we require to be bound in the context, in the Java EE deployment descriptor and the Apache Geronimo-specific deployment plan. The name specified in the ref-name element is the name under which the resource will be available in the application local JNDI context.

For example, if you specify a ref-name of jdbc/DataSource for a DataSource object as given in the XML fragment shown below:

<resource-ref>
<res-ref-name>jdbc/DataSource</res-ref-name>
<res-type>javax.sql.DataSource</res...