Well, you can either store it as application metadata or make your
locking service implementation a singleton (managed by your dependency
injection framework of choice).
Either way, you abstract away the exact storage location of your locks
behind the facade of your EntityLockingService.
Met vriendelijke groet,
Kind regards,
Bas Gooren
schreef ChambreNoire op 3-2-2014 14:48:
Hello,
OK so no storing my Map<String, EntityLock> in the Application MetaData
then?
Many thanks,
Chambre
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Accessing-WebApplication-from-the-service-layer-tp4664145p4664147.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
