Joe Weder wrote:
>
> I have successfully deployed several beans in to JOnAS 2.3. I developed the
> deployment descriptors from the provided samples. I would like to know the
> complete list of supported parameters and their meanings. For example, I was
> wondering about passivation timeouts and other cache options that JOnAS
> might support in either the ejb-jar.xml or the jonas-ejb-jar.xml. These are
> not present in the examples and I have not found any mention in the docs.
>
> Is there a listing somewhere of all the supported deployment descriptor
> parameters?
>
Hi Joe,
The jonas-ejb-jar.xml syntax is defined in a DTD where you can find
in $JONAS_ROOT/xml/jonas-ejb-jar.dtd.
The jonas-ejb-jar.xml content is more or less described in the
JOnAS Bean Programmer's Guide in various chapters.
I so will try to give you below, a complete list depending on
the enterprise bean types: session, entity or message-driven.
On the other hand, the ejb-jar.xml content is completly defined
in the Entreprise Javabeans specification.
I hope this will help you.
Kind regards.
H�l�ne.
===========================================================================+
Session specific
----------------
- <session-timeout>
A session will be automatically removed after a timeout if this tag has
been
specified. The value is in seconds. The default is "no timeout".
Entity specific
---------------
- <is-modified-method-name> (for CMP only)
In order to improve performance we have implemented in JOnAS the
isModified extension.
Before performing an update the container will call a method of the bean
whose name
is indicated in the is-modified-method-name element of the JOnAS
specific deployment descriptor.
This method is responsible to tell if the state of the bean has been
changed.
Doing so, the container is able to know if it must store data in the
database or if it's useless.
- <passivation-timeout>
Entity bean instances are passivated at the end of the transaction, and
reactivacted at
the beginning of the next transaction. In case these instances are
accessed outside
any transaction, their state is kept in memory to improve performances.
However a passivation will occur in 3 circumstances:
1. When the bean is unloaded from the server, at least when the
server is stopped
2. When a transaction is started on this instance
3. After a configurable timeout. This may be interesting to be sure
that the bean
state is periodically stored on disk, if the bean is always
accessed with no transaction.
This passivation timeout can be configured in the jonas specific
deployment descriptor,
with a non mandatory tag <passivation-timeout>. Example:
<jonas-entity>
<ejb-name>Item</ejb-name>
<passivation-timeout>5</passivation-timeout>
.....
</jonas-entity>
This entity bean will be passivated every 5 second, if not accessed
within transactions.
- <jdbc-mapping> (for CMP only)
See the chapter "Configuring Database Access for Container-managed
Persistence"
of the Bean Programmer's Guide.
Message-driven specific
-----------------------
- <jonas-message-driven-destination>
See the chapter "Developing a Message-driven Bea" of Message-driven
Beans Guide
Any bean
--------
- <jndi-name> of the bean (for session and entity only)
To specify the JNDI name of the bean.
- <jonas-resource>, <jonas-resource-env>, <jonas-ejb-ref>
See the chapter "Enterprise Bean's Environmen" of the Bean Programmer's
Guide.
--
-=- H�l�ne JOANIN -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
mailto:[EMAIL PROTECTED] http://www.evidian.com
Phone: 33.4.76.29.73.53 Fax: 33.4.76.29.76.00
Download our EJB Server JOnAS at http://www.objectweb.org
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
