<manisha>
3. Data synchronization : Does the container-provided
data synchronization for entity beans through
ejbLoad() and ejbStore() is efficient ? When will
these methods be called ? Does every vendor will have
their own way of doing it or is there any standards
again ? My question is, whether these methods will be
called after every update of a field or only after
complete update of all the fields in the bean ? I
couldn't understand this concept. How do the container
know the data in the bean is dirty ?
<vendor> I heard that there is a flag in weblogic
isModified(), which will determine if the data is
dirty or not ? I am not clear about this one too
<vendor>
</manisha>
<vendor>
I include extracts from a previous post from Jonathan Weedon (Inprise) on
the support provided our containers cmp engine in relation to the above.
Have you not been reading the previous posts?
......
* Tuned updates: we (optionally) issue an update for exactly the
fields modified (or none, if the bean was unmodified), not all the
CMP fields. .....
* Verified updates: we (optionally) issue an update which verifies
the values of the CMP fields from the start of the transaction,
which addresses issues with optimistic concurrency.
.....
* DD configurable loading of state in finder methods (this is your
optimization).
.....
* Beyond the above "big" features, there are lots of little feature,
like batching of updates, recycling of prepared statements, etc.
which all help to improve the overall performance.
The above will not require you to write code specific to some vendors cmp
engine and its optimizations.
</vendor>
William Louth
Inprise
www.inprise.com/appserver
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
