Am 06.08.13 20:03, schrieb saty:
...various wicket
panels use this data-manager to request data that they need to
display/update etc.
I think it matters how you acces this data-manager from your panels. If
you use something like this:
Application.get().dataManager().doSomething(bla)
you should not have any problems like that. So I think you are holding a
reference to the data-manager as a field in your panel. This way its
part of the object and will be serialized.
You can put this kind of stuff in an LDM an overwrite the load()-method with
Application.get().dataManager().doSomething(bla)
This way your panel can use this model like any other model.
Access to data is well protected using various synchronization techniques
and have no problem in that. The problem seems to be, is somehow wicket is
trying to serialize this LRUMAP which conflicts with application wring data
to it at that same time.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-resolve-this-java-util-ConcurrentModificationException-tp4660273p4660730.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
