I use CODI in an clustered environemnt, no problems till now :)
2012/5/16 tclam tc...@hkeaa.edu.hk
I am trying to implement conversation scope in backing bean of JSF for our
application. At first, I am trying to use MyFaces Orchestra. It seems to
work well. However, I am concerning the case
Thank you.
Have you test the conversation during session replication?
Anyone try MyFaces Orchestra?
Thomas Andraschko-2 wrote:
I use CODI in an clustered environemnt, no problems till now :)
2012/5/16 tclam tc...@hkeaa.edu.hk
I am trying to implement conversation scope in backing
I don't use codi/cdi conversations but just try it, it should work.
If you would like to use OWB, there is an open issue which prevents session
replication with Tomcat 7.0.22+ but there is also an patch available.
https://issues.apache.org/jira/browse/OWB-669
2012/5/16 tclam tc...@hkeaa.edu.hk
Hi!
All the CDI @ConversationScoped gets stored in a @SessionScoped bean managed by
the CDI container. Finally this will somewhen end up in the session (the 'when'
is implementation specific).
LieGrue,
strub
- Original Message -
From: tclam tc...@hkeaa.edu.hk
To:
Hi struberg,
Do you mean that all the @ConversationScoped bean is already stored in
@SessionScoped bean in CDI specification?
Or
Do you mean that I have to wrap a @ConversationScoped bean with another
@SessionScoped bean in my own coding?
struberg wrote:
Hi!
All the CDI
MyFaces Orchestra doesn't support session persistence because the conversation
object isn't serializable, and will not work in a cluster environment.
According to the official page (http://myfaces.apache.org/orchestra/index.html,
see Limitations) there is still some work to be done.
Because of
The context for handling all CODI @ConversationScoped beans ALREADY get stored
in a @SessionScoped bean. Thus it will end up in the Session somehow. But this
is impl and situation depending!
In OWB we do NOT store @SessionScoped beans directly in the Session, because
the http session is _damn_
Because of that, we're now in the process of switching to CODI that it's
fully serializable, and allows the session to be persisted/distributed.
Yes, but please be aware that the EntityManager is still NOT Serializable! Even
if some JPA providers claim it, they will loose state on
Hello,
I'm currently using myfaces 1.1.9 for my web app and I am seeing a strange jsf
behavior when using jsp:include. Below is what the include page looks like.
Inside this include page, it has a h:commandLink inside of a regular HTML
table. For some reasons, the JSF is generating the
9 matches
Mail list logo
