On Jul 24, 2008, at 12:14 , Johan Compagner wrote:
what you are describing are services and yes those shouldnt be hold
on to in
wicket components/models
In my case, it's an entity that has the uniqueness constraint, not a
service; for what concern images, first you have to write some code
because BufferedImage isn't serializable by itself; and, second, it
would have some memory consumption impacts.
Keeping the discussion more in general, as per thread subject, my
point is that Wicket is imposing me too many constraints on my design.
--
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[EMAIL PROTECTED] - mobile: +39 348.150.6941
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
