I have One Array-list(with over 1 objects in it) what is the best
practice for caching it so I don't have to load it over and over again in
each request?
Jan
On Wed, Mar 9, 2011 at 1:00 PM, Jan Juno janko...@gmail.com wrote:
I have One Array-list(with over 1 objects in it) what is the best
practice for caching it so I don't have to load it over and over again in
each request?
Usually at our company we expect our ORM mapper (hibernate) to take
can you point me to a good wicket + ehcache tutorial?
On 9 March 2011 13:13, Martijn Dashorst martijn.dasho...@gmail.com wrote:
On Wed, Mar 9, 2011 at 1:00 PM, Jan Juno janko...@gmail.com wrote:
I have One Array-list(with over 1 objects in it) what is the best
practice for caching it so
-with-over-1-objects-tp3343442p3343499.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
.1842946.n4.nabble.com/Storing-ArrayList-with-over-1-objects-tp3343442p3343499.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
Hi,
Another way is to have a service manage the list. We have a reference
data list (list of streets) in our application that has 100k elements
that is stored in memory and we have a service hold one instance that is
shared between all accessors (typically the autocomplete search fields)
of
