"petemuir" wrote : Reading through Sergey's answers it sounds like we need to
work on getting a4j:mediaOutput and Seam to work properly together.
That would be fantastic. in the meantime the Lifecycle.beginRequest() and
Lifecycle.endRequest() looks like exactly what I needed.
Thanks.
View the
Reading through Sergey's answers it sounds like we need to work on getting
a4j:mediaOutput and Seam to work properly together.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041794#4041794
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
"courtneycouch" wrote : As far as lazy initializing, I need the managed-bean to
have access to seam components, if its lazy initialized then its initialized
outside of the seam context and cant access them. Seam has to initialize the
managed beans so I have to create a seam component whose sole
Oops i missed part of that quote from the thread.
>From the ajax4jsf thread:
"SergeySmirnov" wrote : There is a dilemma there. You can use the whole JSF
lifecycle with restoring the session for each request to resources like this OR
serialize only the required data and pass it directly to the m
"petemuir" wrote : "courtneycouch" wrote : The reason for this is that ajax4jsf
mediaOutput components cant be seam component. They need to be simply
managed-beans. When I'm using managed-beans in a seam application the regular
lifecycle stuff for managed-beans doesnt work since seam is in con
"courtneycouch" wrote : The reason for this is that ajax4jsf mediaOutput
components cant be seam component. They need to be simply managed-beans. When
I'm using managed-beans in a seam application the regular lifecycle stuff for
managed-beans doesnt work since seam is in control.
This is some
"petemuir" wrote : Seam's session context is driven by the web application.
Seam is notified when the session has been created and processes the creation
of @Startup @Scope(SESSION) components. We are calling the hooks as late as
possible afaics.
|
| What are you trying to do - which method
Seam's session context is driven by the web application. Seam is notified when
the session has been created and processes the creation of @Startup
@Scope(SESSION) components. We are calling the hooks as late as possible afaics.
What are you trying to do - which methods? What is going wrong - wha
"[EMAIL PROTECTED]" wrote : @Startup is not related to the session context, so
I don't understand what you want. However, we had some other requests for more
fine-grained interception of the Seam startup procedure and there might be open
JIRA issues you can attach your request to. Search first,
@Startup is not related to the session context, so I don't understand what you
want. However, we had some other requests for more fine-grained interception of
the Seam startup procedure and there might be open JIRA issues you can attach
your request to. Search first, if nothing is there, open a
None quite fit the point I need the method called..
In essense I would need something like:
org.jboss.seam.postCreateContext. ? called after the context is created
but there doesnt appear to be that kind of granularity.
The @Startup annotation isnt a pre or post session creation.. it occurs du
Maybe you can use one of the built-in events you can find in section 5.1.3 of
the documentation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041770#4041770
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041770
12 matches
Mail list logo
