On Mon, Nov 3, 2008 at 2:09 PM, JulianS <[EMAIL PROTECTED]> wrote:
>
To answer your question, here's my
> implementation of dataprovider#model():
>
>public IModel model(Object object)
>{
>return new Model((Serializable) object);
>}
>
> Of course, it's very po
James, thanks for your reply. I've checked that my
OpenEntityManagerInViewFilter precedes the Wicket filter. And my debug log
indeed shows that it seems to be opening and closing the entity manager
before and after the wicket filter runs. I'm hoping to avoid the type of
query you suggest, but I'm
Igor,
I'm not using a loadable detachable model because I was hoping to get the
list of foos directly from the Bar object, as opposed to having a dedicated
dao method to get the list of foos, which seems to defeat the benefit of
using JPA's object chaining. To answer your question, here's my
impl
what is your dataprovider#model() look like? are you using a loadable
detachable model?
-igor
On Mon, Nov 3, 2008 at 11:04 AM, JulianS <[EMAIL PROTECTED]> wrote:
>
> I am experiencing exactly the problem outlined in the subject of this post,
> and I would really appreciate any help I can get, as
Firstly, your code is rather strange. That getFoos() method is not part of
the List Interface API.
Two possible solutions:
The filter chain maybe incorrect in your web.xml. Your
OpenEntityManagerInViewFilter might not be preceding the Wicket filter.
Check that it does precede it.
If you have a d
Oops...I meant:
Bar bar = myApi.getBar();
List foos = bar.getFoos();
JulianS wrote:
>
> I am experiencing exactly the problem outlined in the subject of this
> post, and I would really appreciate any help I can get, as I am under a
> deadline. It's the first tim
I am experiencing exactly the problem outlined in the subject of this post,
and I would really appreciate any help I can get, as I am under a deadline.
It's the first time I'm using Wicket with JPA, and I just don't understand
why this isn't working.
I have a Wicket dataprovider that looks like
Are we talking about a "wizard" here? What if you used something like this:
https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/wicketopia/src/main/java/org/wicketopia/model/proxy/ProxyModelManager.java
Basically, the "models" cache their values until you call "commit" on
the ProxyMo
On Thu, 09 Oct 2008, Lutz Müller wrote:
> It might work if you dont have any ajax on your page. otherwise each ajax
> call
> happens in a new request and causes your domain object to be retrieved from
> the database.
> this way you lose every change made to your object. writing all changes to
>
Hi Lutz
I agree, there is something to this.. However it's not wicket related..
I know that Bjarni are hacking away at something, I've dicussed a few
things with him.
I guess if you are creating entities then you can store your data in a
temporary model... However Bjarni Gudmondurs thing(sti
maybe this will help
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
-igor
On Thu, Oct 9, 2008 at 7:02 AM, Michael Sparer <[EMAIL PROTECTED]> wrote:
>
> you mean changing each property of an existing object by means of ajax? if
> the object is serializable, clone the object and p
you mean changing each property of an existing object by means of ajax? if
the object is serializable, clone the object and perform the changes on that
object ... if it isn't set the properties in your form and apply them
onsubmit ... or am I missing the point completely?
Lutz Müller wrote:
>
>
It might work if you dont have any ajax on your page. otherwise each ajax call
happens in a new request and causes your domain object to be retrieved from
the database.
this way you lose every change made to your object. writing all changes to
database before detaching can be an option, but then
Yup the way that I do it too almost down to every line:)
Michael Sparer wrote:
When using the OSIV-filter the lazyload exception may only happen if the same
entity is used among different requests ... sothat it gets detached from
hibernate. have a look at
http://talk-on-tech.blogspot.com/2008/05
Would you be able to create a quickstart that exhibits this behavior?
If you want, you can use the JPA archetype in wicketopia (the code I
referenced) to set everything up for you automatically.
On Mon, Sep 29, 2008 at 12:21 PM, Korbinian Bachl - privat
<[EMAIL PROTECTED]> wrote:
> Hmm,
>
> I copi
Hmm,
I copied it to web.xml, but result is:
2008-09-29 18:07:24,125 ERROR org.hibernate.LazyInitializationException
- failed to lazily initialize a collection of role:
de.xxx....xxx., no session or session was closed
org.hibernate.LazyInitializationException: failed to lazily i
We don't use JPA at work, but we use OSIV (we're using straight
hibernate). Anyway, for the JPA configuration, you can look at:
https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/jpa-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/web.xml
On Mon, Sep 29, 20
really? - I tried it but...
would you please be so nice and post the part of the web.xml where it is
mapped and the corresponding part of the spring-application.xml ?
what wicket version are you on? what runtime (Tomcat 6?)?
Best,
Korbinian
James Carman schrieb:
On Mon, Sep 29, 2008 at 7:
When using the OSIV-filter the lazyload exception may only happen if the same
entity is used among different requests ... sothat it gets detached from
hibernate. have a look at
http://talk-on-tech.blogspot.com/2008/05/custom-reuseable-loadabledetachablemode.html
... that's the way we're doing it
On Mon, Sep 29, 2008 at 7:14 AM, Korbinian Bachl - privat
<[EMAIL PROTECTED]> wrote:
> However, the OpenSessionInViewFilter will not work with wicket, even if
> mapped to "/*" in the web.xml
Huh? We use it and it works just fine. By the way, have you tried
OpenEntityManagerInViewFilter if you'r
>I think it could be something about
> missing usage of loadabledetachable model..?
not for me, as the original entity is pulled using an
loadabledetachableModel via a SortedDataProvider :/
if you look around, the all called solution for this is the
"OpenSessionInViewFilter" and the usage of
Hi Korbinian
Im facing the same problems... I also use extended.. So gonna be great
to see the outcome of this thread.. I think it could be something about
missing usage of loadabledetachable model..?
Korbinian Bachl - privat wrote:
Hi,
I'm currently struggling with the famous "lazy loa
Hi,
I'm currently struggling with the famous "lazy load exception" under
spring + jpa with wicket.
The problem is, in my case, that i pull an entity from the database
using a spring-bean (@SpringBean) and JPA (hibernate). Then in the
wicket class i need to walk the entity tree a bit, based o
23 matches
Mail list logo
