Sounds like a bug in your custom save() function. What is it doing?
Mark On Thu, Oct 1, 2009 at 12:31 PM, Scott Brady <[email protected]> wrote: > > On Thu, Oct 1, 2009 at 1:06 PM, Scott Brady <[email protected]> wrote: > > OK, this may be yet another hard-to-describe issue. > > <snip> > > > So, I guess the question is why newly-saved object (release) reports > > as a TransferObject instead of what it's supposed to, > > releaseDecorator, until I refresh the application variables? > > > > I found the fix. Something I neglected to mention is that I was > handling the save() function through our BaseDecorator instead of > using the transferFactory's save() function Initially, this was so we > could programmatically use transactions or not, if we wanted. since > we're not doing that anyway, I can just use the standard save > functionality, and that removes the problem. > > Scott > > > -- > ----------------------------------------- > Scott Brady > http://www.scottbrady.net/ > > > > -- E: [email protected] T: http://www.twitter.com/neurotic W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
