Hi Tim,
On Nov 8, 2011, at 10:50 AM, [email protected] wrote:
Craig,
Thanks for the minutes write up.
I've been going through the JDO API in more detail and in order to
implement the QBE and get the changed information for a JavaBean, it
appears to require that an object not be in the Transient state.
However,
the objects I see being created for the QBE will always be in the
Transient state. To make this work in the Transient state, this would
required that there be a StateManager associated with the JavaBean.
That is the purpose of makeTransactional. This API associates a
StateManager with the transient object.
Then we need to see what other APIs will help you to use the
information that is known by the StateManager.
Hope this helps,
Craig
So,
I'm looking at the implication of associating a StateManager with a
JavaBean while in the Transient state and the effect it might have
if a
developer than happens to try and make the JavaBean persistent.
This will
take a little longer than I had hoped.
Tim Gallagher
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
