On Oct 6, 2009, at 19:29, Eelco Hillenius wrote:
I must admit that I don't get the whole detachable stuff in Wicket.
I'm used
to think in horizontal tiers
where one tier does all the caching automagically (e.g. 2nd level
cache in
JPA/Hibernate) and the
other tiers don't know about that
mad typos :-)
is not a bug deal but not a big deal *lol*
Am 07.10.2009 um 09:40 schrieb Peter Ertl:
well, not a bug deal!
/image/${fullnameIncludingExtension} can be parsed easily :-)
Am 07.10.2009 um 02:14 schrieb Igor Vaynberg:
erm, although we do not quiet support
/${name}.${format}/
And regarding the excellent wiki page: that's one thing I don't like
about wicket. Documentation is
not were in belongs, in the code or at least checked in with the code.
I always have to figure
it out by myself if some wiki page is up-to-date or not.
I really never had such a hard time
On Wed, Oct 7, 2009 at 9:43 AM, Michael Mosmann mich...@mosmann.de wrote:
If you don't know, which book: http://www.manning.com/dashorst/
Judging from his email address and timezone, I suspect Robin is from
germany, so he might enjoy the german book more.
Martijn
On Oct 7, 2009, at 09:43, Michael Mosmann wrote:
And regarding the excellent wiki page: that's one thing I don't like
about wicket. Documentation is
not were in belongs, in the code or at least checked in with the
code.
I always have to figure
it out by myself if some wiki page is
We call it compressing because you have data X with 10 references to
objects.
then detaching clears 5 (or something like that) of those references to the
objects
So now you graph of objects is not 11 objects but only 6 thats what we call
compressing by detaching.
The after detaching we serialize
