On Jan 4, 1:46 pm, "Mark Mandel" <[email protected]> wrote: > This was a bug fix for the new Object meta data lifecycle, where there > were cases where the meta data's parents were sometimes not found, so > this wouldn't affect object caching. > > Was there any other changes you made to the roll back?
Nope, simply rolled back to 1.1 and that fixed the problem. Well, it's possible the problem still exists but I can tell you at a minimum the error I was getting about not being able to find the parentonetomany on restart has disappeared. And we haven't gotten any additional errors where related objects were dropping out causing notfound problems with the getRoleArray(). Both things have cleared up in going back to 1.1. Brian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
