Update of /cvsroot/xdoclet/xdoclet/modules/bea/src/META-INF
In directory
sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21109/modules/bea/src/META-INF
Modified Files:
xtags.xml
Log Message:
support for cache-between-transactions added. Thanks to Enno Runne for the
patch. (XDT-1334)
Index: xtags.xml
===================================================================
RCS file: /cvsroot/xdoclet/xdoclet/modules/bea/src/META-INF/xtags.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -r1.15 -r1.16
*** xtags.xml 26 Sep 2004 10:16:41 -0000 1.15
--- xtags.xml 11 Apr 2005 21:03:47 -0000 1.16
***************
*** 480,484 ****
</options>
</option-set>
! </option-sets>
</parameter>
</tag>
--- 480,525 ----
</options>
</option-set>
! </option-sets>
! </parameter>
! <parameter type="bool">
! <name>cache-between-transactions</name>
! <usage-description>
! The cache-between-transactions element tells the EJB container
whether
! to cache the persistent data of an entity bean across (between)
! transactions.
!
! When a value of 'true' is specified caching between transactions
is
! enabled and long term caching of data is performed. If a value of
! 'false' is specified, (the default) short term caching is done,
which
! means that data is only cached during an individual transaction.
A
! value of 'true' is only allowed if the concurrency-strategy for a
bean
! is either Exclusive, ReadOnly, or Optimistic.
!
! A ReadOnly bean simply ignores the value of the
! cache-between-transactions element since long term caching of
readonly
! data is always performed.
!
! When long term caching is enabled for Exclusive concurrency, the
EJB
! container must have exclusive update access to the underlying
data,
! i.e. the data must not be updated by another application outside
of
! the EJB container. If an Exclusive bean is deployed in a
cluster, long
! term caching is disabled automatically because any node in the
cluster
! may update the data, making long term caching impossible. (Note:
In
! releases prior to WLS 7.0, this feature was controlled using the
! db-is-shared element.)
!
! When long term caching is enabled for Optimistic concurrency, the
EJB
! container reuses cached values from previous transactions, but
ensures
! that updates are transactionally consistent by checking for
optimistic
! conflicts at the end of the transaction. In addition,
notifications
! for updates of optimistic data are broadcast to other cluster
members
! to help avoid optimistic conflicts.
! </usage-description>
! <mandatory>false</mandatory>
! <default>false</default>
! <condition-description>Entity beans</condition-description>
! <condition type="type">
! <condition-parameter>javax.ejb.EntityBean</condition-parameter>
! </condition>
</parameter>
</tag>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
xdoclet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
