Thank you Sven for help.
I created quickstart and found out a problem.
What you said is true - the problem is really not in CompoundPropertyModel
or in nesting of ListItemModel.
REAL PROBLEM WAS:
I was mistakenly passing Hibernate entities directly between pages -
without proper encapsulating the
Reverting wit Wicket 7.0.0 seems to have solved the issue, I'll wait for
7.2.0 and give it anaothe shot! Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problem-with-wicket-encolsures-and-possibly-OpenEntityManagerInViewFilter-tp4672738p4672740.html
Sent from t
Hi,
> I suppose, that core of the problem is, that ListItemModel does not
> implement IChainingModel, so it cannot be passed to another model...
CompoundPropertyModel does not care of the actual model implementation,
it should work fine with any target model.
Actually Wicket provides Property
PROBLEM:
When ListItemModel is wrapped into CompoundPropertyModel (that is used as
default model of Form),
then Form model-object is never updated -> so old data are saved, without
any changes.
EXAMPLE OF PROBLEM:
Example of problem: (data in form object are NOT updated after from
submission)
Hi,
have you tried Wicket 7.0.0 as well? The problem occurred only with
7.1.0? Try to use version 7.2.0-SNAPSHOT which contains some bug-fixes
for enclosures and component queuing.
Hello!
I've introduced OpenEntityManager filter to my application and switched to
wicket 7.1.0 and all enclosure
Hello!
I've introduced OpenEntityManager filter to my application and switched to
wicket 7.1.0 and all enclosures that worked perfectly before went crazy.
Here is a web xml snippet:
open-entitymanager-in-view-filter
org.springframework.orm.jpa.support.OpenEntityManagerI
