https://issues.apache.org/jira/browse/WICKET-3779
On Wed, Jun 8, 2011 at 11:32 AM, Igor Vaynberg <[email protected]>wrote: > most likely it is an oversight. open an issue. at some point session > access was synchronized, but later it was made more granular. the > metadata code may have never been updated. > > -igor > > > On Wed, Jun 8, 2011 at 11:29 AM, Dan Retzlaff <[email protected]> wrote: > > Hey all, > > > > Can someone help me understand the synchronization and dirty-marking > > requirements surrounding Session#setMetaData()? I thought the rules for > > Session use were (1) synchronize data access, (2) call Session#dirty() > after > > data changes to replicate the changes across the cluster. However, I > don't > > see either of these happening in Wicket's internal use of Session > MetaData. > > Is this an oversight, or am I missing something? > > > > Thanks, > > Dan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
