hi, a fix for openjpa-659 has been added. but have tested it only against JSE environment. If possible, you can apply the change in your environment to let us know if that changes anything.
Marc Logemann-3 wrote: > > Hi, > > the strtegy is: > > @Id > @GeneratedValue(strategy = GenerationType.IDENTITY) > String oid; > > I will check it with both strategies (app vs. datastore) and comment > on it.... > > -- > Marc Logemann > blog http://logemannreloaded.blogspot.com > privat http://www.logemann.org > > > > Am 14.07.2008 um 20:15 schrieb Pinaki Poddar: > >> >> What is the identity strategy used by the Order.class? While >> reproducing the >> error, that factor *seems* to be crucial than whether there is a >> embedded >> field. Can you verify if there is a change in behavior if >> Order.class uses >> datastore vs application identity? >> >> >> Marc Logemann-3 wrote: >>> >>> and yes, for the record: i changed to build time enhancement and now >>> embedded entities work. Still interessted in the "why" answer. >>> >>> -- >>> Marc Logemann >>> blog http://logemannreloaded.blogspot.com >>> privat http://www.logemann.org >>> >>> >>> >>> Am 14.07.2008 um 16:22 schrieb Pinaki Poddar: >>> >>>> >>>> Hi, >>>> Are you using runtime enhancement with Java 5? >>>> If yes, the immediate workaround is to enhance the persistent >>>> classes at >>>> build-time. >>>> >>>> -- >>>> View this message in context: >>>> http://n2.nabble.com/no-state-snapshot-available-on-embedded-mapping-tp526616p527331.html >>>> Sent from the OpenJPA Users mailing list archive at Nabble.com. >>>> >>> >>> >>> >> >> -- >> View this message in context: >> http://n2.nabble.com/no-state-snapshot-available-on-embedded-mapping-tp526616p527706.html >> Sent from the OpenJPA Users mailing list archive at Nabble.com. >> > > > -- View this message in context: http://n2.nabble.com/no-state-snapshot-available-on-embedded-mapping-tp526616p529502.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
