Ok, all done :
http://jira.jboss.org/jira/browse/JBSEAM-1423
I had to attach it in 4 parts, all zipped. I've included test cases that
demonstrates the problem.
In the test app (a cut down version of my dummy book store app) there is no
exception on the page flow navigation page changes, only
Attach the whole thing if it fits. I might have diff jar versions.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052369#4052369
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052369
I have stripped down my seam-gen generated bookstore test app to the minimum,
and created an import sql script and written some test cases to demonstrate the
problem.
Do you want me to include all 30meg (zipped) of jars also, or should I just
delete them from the zip file? There's nothing addi
Please create a very simple project that reproduces the problem, and add an
issue to JIRA so we can take a look.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052230#4052230
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
Sorry, should clarify that :
according to http://jira.jboss.com/jira/browse/JBSEAM-976, the id="" portion of
the @Begin annotation is possibly being deprecated in favour of natural
conversation Ids in the pages.xml, not the whole @Begin annotation.
View the original post :
http://www.jbos
Ok, now I think I know what the problem is (but not the answer).
|
|
This xml lets seam detect an existing conversation for the same entity, and
switches to it instead of creating a new one. It works fine when starting a new
conversation (i.e. editing a book from the search list).
How
D'oh, yeah, I know that should be :
| propagation="nest"
|
That seems to get rid of the original problem, but introduces other problems
that I'll have to go investigate.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051908#4051908
Reply to th
