"[EMAIL PROTECTED]" wrote : I cannot reproduce this behavior. If a page action
begins a conversation, everything works just fine for me.
What can I say? Very odd :-)
But now it works fine for me and it also works fine for you, so everybody are
happy :-)
Thanks for your time and help.
View th
I cannot reproduce this behavior. If a page action begins a conversation,
everything works just fine for me.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025294#4025294
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4
Now it works :-)
Old pages.xml (OK for 1.1.5 and not OK for 1.2.0):
| http://jboss.com/products/seam/pages-1.1.dtd";>
|
|
|
|
|
|
|
New pages.xml (OK for 1.2.0. Havn't tried it for 1.1.5):
| http://jboss.com/products/seam/pages-1.1.dtd";>
|
|
|
"holtak" wrote : Just loud thinking:
|
| you always get a new (not nested) conversation with seam 1.2PATCH1 and then
@In can`t inject the old instance? And this is not so when you move back to
1.1.5, for some reason...
|
With 1.2.0 and pages.xml I get a new conversation id at each reques
Just loud thinking:
you always get a new (not nested) conversation with seam 1.2PATCH1 and then @In
can`t inject the old instance? And this is not so when you move back to 1.1.5,
for some reason...
Also, I don`t understand why do you return a String from #{acountBean.begin}?
That makes things
The behaviour for pages.xml have changed in 1.2.0 ! Because if I remove
pages.xml everything will work out just fine.
pages.xml:
| http://jboss.com/products/seam/pages-1.1.dtd";>
|
|
|
|
|
|
|
Something in pages.xml triggers the above problem (for each method
Ok, I will do some more investigation :-)
User (userDomain):
| @Entity
| @Name("userDomain")
| @Table(name = "userx") // user is a reserved word in PostgreSQL
| @Inheritance(strategy = InheritanceType.SINGLE_TABLE)
| @DiscriminatorColumn(name = "DISCRIMINATOR", discriminatorType =
Dis
Nothing significant has changed, no.
No-one can help you if you havn't showed the code for UserDomain.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024863#4024863
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024863
No comments/help from the people behind JBoss Seam?
It's really strange, because I only replaced the 1.1.5 jar files
(jboss-seam.jar and jboss-seam-ui.jar) with the 1.2.0 files.
Have something changed in the @In @Out behaviour in 1.2.0 or/and in the
bijection implementation?
View the origina
"holtak" wrote : What is "userDomain"? (StatefullBean, StatelessBean,...)
| and what scope is it in? Use debug.seam to check if it is really there
where you want it.
|
| I`ll check the @In (create=true) acting today when I come to coding but
I`ve moved to 1.2PATCH1 from 1.1.5 and don`t hav
What is "userDomain"? (StatefullBean, StatelessBean,...)
and what scope is it in? Use debug.seam to check if it is really there where
you want it.
I`ll check the @In (create=true) acting today when I come to coding but I`ve
moved to 1.2PATCH1 from 1.1.5 and don`t have this problems.
View the
Any help please :-)
It's a really big problem for me, that Seam 1.2.0 creates a new instance of
userDomain when an AccountBean method is invoked - for each AccountBean method
call I get a new userDomain instance !
Seam 1.1.5 creates one instance of userDomain and use this instance when an
12 matches
Mail list logo
