yes - it run's smoothly together ...
Am 18.09.2009 um 07:44 schrieb Michael Mosmann:
Am Freitag, den 18.09.2009, 00:35 +0200 schrieb Peter Ertl:
as an further improvement use salve to completely remove your
headache :-)
http://code.google.com/p/salve
thank you.. interesting stuff..
do yo
Am Freitag, den 18.09.2009, 00:35 +0200 schrieb Peter Ertl:
> as an further improvement use salve to completely remove your
> headache :-)
>
>http://code.google.com/p/salve
thank you.. interesting stuff..
do you have any experience in combination with hibernate?
mm:)
> Am 17.09.2009 um 2
as an further improvement use salve to completely remove your
headache :-)
http://code.google.com/p/salve
Am 17.09.2009 um 23:51 schrieb Michael Mosmann:
Hi,
(Solution with no Spring is
preferable).
Use Spring, because it will limit your headache..
Maybe this is usefull:
http://www.wi
Hi,
> (Solution with no Spring is
> preferable).
Use Spring, because it will limit your headache..
Maybe this is usefull:
http://www.wicket-praxis.de/blog/download/
use Link behind "Praxisbuch Wicket Beispielcode" for a maven-based
project with:
- Spring (open session in view filter, @Spring
hi,
you could also use an Aspekt (e.g. with Aspekj) zu reinit all lazy
proxies on the next request. The Proxy objects would be detachted and
serialized throw
the models. With an Aspekt you can re-attach ALL hibernate proxies,
without triggering the DB.
Martin
Anton Komratov schrieb:
> Hi, I'm
Hi Anton
The Problem you encounter is probably because you're holding on to a
hibernate object between requests, thus the references are not valid
anymore.
Have a look at
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
This works for us with hibernate.
Matt
Anton Komratov w
Hi, I'm using Wicket + Hibernate (without Spring).
In my application I open Hibernate *session* in WebRequestCycle.*
onBeginRequest*() and close it in WebRequestCycle.*onEndRequest*().
But having association (many-to-one mappings between classes) I've got
LazyInitializationException (no Session).