Heres a list of some of the most common problems we get:
* bad unsaved-value mappings
* problems with cascade save for composite-id classes
* "an object with this id was already associated with the session"
It turns out that they can all be addressed by adding a new method
to the session. This met
Cascade semantics for this operation are the same as for
saveOrUpdate().
What I mean by this is that saveOrUpdateCopy() cascades to
itself whenever saveOrUpdate() would cascade.
---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November
On 10 Nov (00:27), Gavin King wrote:
> loaded object from the session cache). The new state is then /copied/
> onto the loaded object and the loaded object is returned to the user.
> We never get the exception listed above, because we don't try to add
> the given object to the cache. If no object
Hello all,
This will probably be very useful in situations where we do not have full
control of the object in question. For example Axis is a very good
framework for implementing web services, as well as Java -> XML & XML ->
Java binding. However without modification of Axis, the returned Java
o
