when i find out what's causing my bean to be instantiated on every ajax call
i'll come back here to report.
That sounds familiar - good luck ;)
Which scope does your bean have? You are sure that you are really using CDI
javax.enterprise.context.* scopes and not javax.faces.bean.* scopes due
Gerhard pinged me that you are using @ViewAccessScoped. In that case I'd
recomment to debug if the whole Context Extension gets properly registrated.
If the CDI container doesn't know the @ViewAccessScoped annotation then all
your beans will end up as @Dependent...
LieGrue,
strub
-
hi mark,
since rafael mentioned that it works without a4j and there is no issue with
a4j in the demo, i don't think that it is such a basic issue.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional
Hi guys,
I think that what Mark stated can be happening in the environment at my
company(weblogic 11g, mojarra 1.2, owb and CODI) cause a simple forward is also
causing the bean to be instantiated(tested with ViewAccess and WindowScoped),
How can i ensure that the whole Context is being
Oops, overlooked that.
In that case I'd say the following things might get checked.
a.) If you get an AJAX request, does the windowId get propagated properly?
Does a CODI @WindowScoped bean show the correct context, or do you loose it
with each request?
- windowId gets lost somewhere
b.)
Hi Rafael!
Please try to set a breakpoint in
GroupedConversationContextExtension#afterBeanDiscovery()
The new contexts get added via the AfterBeanDiscovery events addContext()
method.
If this doesn't get invoked, then the Extension detection probably doesn't work.
LieGrue,
strub
-
hi rafael,
for a wls 11g deployment you have to follow [1].
regards,
gerhard
[1] https://cwiki.apache.org/confluence/display/EXTCDI/JavaEE5+Support
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for
7 matches
Mail list logo
