Hello there!
I have a problem with the CODI JSF Scope ViewAccessScope and the
PrimeFaces ResourceHandler.
Primefaces evaluates a value expression within the resource handler to
retrieve dynamic content, why and how is not important. The fact is,
that the ResourceHandler is called before
hi christian,
a workaround would be an own ConversationFactory - but that means a lot of
work.
since the myfaces codi conversation scopes (the view-access scope is just a
special conversation type) are bound to jsf by default, it wasn't intended
to support access outside of the jsf
The more concrete question on the problem i face would probably be:
Is the ViewAccessScope designed to work for a JSF ResourceHandler which
is called instead of the normal JSF Lifecycle? None of the JSF Phases is
executed when a ResourceHandler is invoked, so would it actually be
possible
hi christian,
the short answer is: no - it was never intended to support it.
however, if you provide an use-case which isn't supported, we will discuss
it.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Thank you very much gerhard!
I just implemented a test for the problem I face and in fact, primefaces
did something very wrong. Even the standard ViewScope is, as expected,
not supported.
I appreciate your fast response time, CODI FTW! ;)
Am 16.02.2012 17:05, schrieb Gerhard Petracek:
hi
you are welcome! :)
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2012/2/16 Christian Beikov c.bei...@curecomp.com
Thank you very much gerhard!
I just implemented
Hi!
the short answer is: no - it was never intended to support it.
+1
To add a bit more info. This is not even intended/supported by JSF. You would
need to hit the server for each and every css, img, js, etc served as resource.
No caching on the browser side would be possible! By default all
@mark:
that's correct. however, since it's possible to customize most parts, it
would be possible (for sure that would cause a performance impact).
everybody is welcome to share use-cases which aren't supported and we can
discuss them.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE
Uh, are you guys saying the FacesContext isn't available in a ResourceHandler?
If it's not available, this is a major pain for people with dynamic resource
generation. Essentially, one would have to pass all the necessary information
through the URL, or through a non-JSF session.
I realize
Looks like it is available. I guess the task is to make it work.
John
From: owner-j...@lists.llnl.gov [owner-j...@lists.llnl.gov] On Behalf Of
Carlson, John W. [carlso...@llnl.gov]
Sent: Thursday, February 16, 2012 1:36 PM
To: MyFaces Discussion; Mark
The problem with the mechanism introduced in JSF-2.0 is to rely on Expression
Language evaluation for the dynamic parts. But that doesn't perform well so the
JSF containers serve it with a cache header. Please checkout Jakobs enhanced
resource handler [1] (especially the Requirements Wiki page)
11 matches
Mail list logo
