work around for my use case: because a client uploads a file which then starts the multiple inserts into the managed collection i could refresh that collection from the client side after my upload complete event. Because the client then gets new data, all other clients's (with that managed collection open) data also updates. This would obviously not work if the change to my data was initiated by a non flex client.
On Tue, Mar 31, 2009 at 6:36 PM, Johannes Nel <johannes....@gmail.com>wrote: > Hi All > > Using a many to one relationship on a collection and I have more than one > client which has the collection visible. > From my java code I refresh my fills and then I get the no message broker > error. Yet if I add anything to the collection from within my flex app the > changes propagate fine. > So really this only happens when telling my hibernate assembler to refresh > post me creating more items in the collection. The error is as clear as mud, > so can someone point me in some direction. > > johan > > -- > j:pn > \\no comment > -- j:pn \\no comment
