Since the original question was about storing component references as
class members, let me answers how we handle that in our shop.
Wicket serializes stateful pages anyway, so any component references
within the page don't hurt (at all). It's just a 4-byte reference to an
object wicket
Hi!
I'm trying to get an efficient pagination with MongoDB and Wicket working.
The problem with MongoDB is, that the skip operation can become really
expensive on large datasets (basically every time you really need
pagination). So the best practice for pagination in MongoDB is to make
range
Hello wicket,
the current released version for wicket-native-websocket-jetty9 etc. is
0.13.0.
What kind of release cycle are you using for websockets??
The reason i am asking is that for wicket-native-websocket-jetty9
deprecation warnings were fixed with a commit on 11. Juli 2013. In the most
Hi,
http://central.maven.org/maven2/org/apache/wicket/wicket-native-websocket-jetty9/0.14/
Wicket Native WebSocket is experimental module so it doesn't have the same
version as Wicket Core.
On Fri, Nov 8, 2013 at 6:17 PM, Jan Moxter jan.mox...@innobix.com wrote:
Hello wicket,
the current
It sounds like you are trying to force a paradigm that doesn't fit with the
api's you've chosen.
It's not very hard to implement a custom pager using a RepeatingView or
RefreshingView. In your model object you'd have something like static
ListYourPojo getResults(int start, int count) where you'd
Hi Martin,
- thank you for pointing me to the version 0.14 I will check out if the
problem still exists.
- We do use Jetty 9.0.x so the version seems to be appropriate, but thanks
for explaining the differences
By the way for something being experimental Wicket Native WebSocket
runs really
