This content has been marked as final.
Show 7 replies
-
1. Re: seam-gen: behaviour of an generated app
baz Apr 19, 2007 7:14 AM (in response to baz)Any comments?
-
2. Re: seam-gen: behaviour of an generated app
lundegaard Apr 19, 2007 7:46 AM (in response to baz)<h:commandButton action="/path/to/Car.html" immediate="true" />
or<a href="Car.html">Done</a>
or<s:link view=/path/to/Car.html? value=?Car?/>
should work. -
3. Re: seam-gen: behaviour of an generated app
baz Apr 19, 2007 9:52 AM (in response to baz)Hello,
thanks for the answer i have tried immediate = true and s:link
Both solution do not work. I get the well known behaviour.
I have to do a reload (on CarEdit or on Car) for getting the old value:-(
Ciao,
Carsten -
4. Re: seam-gen: behaviour of an generated app
pmuir Apr 20, 2007 6:19 AM (in response to baz)Post the carEdit.page.xml and carEdit.xhtml
-
5. Re: seam-gen: behaviour of an generated app
baz Apr 20, 2007 7:50 AM (in response to baz)Hello Pete,
i have not modified them. They are the same as they are generated by seam-gen -
6. Re: seam-gen: behaviour of an generated app
pmuir Apr 20, 2007 8:02 AM (in response to baz)Odd, that works fine for me. An EntityQuery is Event scoped so should reload.
-
7. Re: seam-gen: behaviour of an generated app
baz Apr 24, 2007 2:58 AM (in response to baz)I will investigate further on the next weekends.
Perhaps my generated app is to complex? It contains oer 20 entities which are making massive use of composite primary keys.
I am going to create a tiny little datamodel with only 2 tables and one foreign key. If i can hunt the problem done, i will report.
Ciao,
Carsten