se(). This was the only change needed to make ViewAccessScope
>>> work.
>>> Unfortunately the DynamicContentStreamer isn't used anymore in version
>>> 3.+
>>> :-(
>>>
>>> I really would appreciate if you could post your solution for that
>&g
ts to JSF resource handler. Please note
that you cannot use viewscope beans as viewscoped bean is not
available in resource loading request."
best regards
Thomas
-Ursprüngliche Nachricht-
Von: Christian Beikov [mailto:c.bei...@curecomp.com]
Gesendet: Donnerstag, 16. Februar 2012 17:09
An: My
> > browser will make a request to load the page and then another one to
> > the dynamic image url that points to JSF resource handler. Please note
> > that you cannot use viewscope beans as viewscoped bean is not
> > available in resource loading request."
> >
> > b
an is not available in
resource loading
request."
best regards
Thomas
-Ursprüngliche Nachricht-
Von: Christian Beikov [mailto:c.bei...@curecomp.com]
Gesendet: Donnerstag, 16. Februar 2012 17:09
An: MyFaces Discussion
Betreff: Re: CODI 1.0.1 NPE in JSF ResourceHandler when evaluating
[2] https://cwiki.apache.org/MYFACES/myfaces-commons-resourcehandler.html
- Original Message -
> From: "Carlson, John W."
> To: MyFaces Discussion ; Mark Struberg
>
> Cc: Java Programmers List
> Sent: Thursday, February 16, 2012 10:36 PM
> Subject: RE: CODI 1.0.1 NPE
Struberg
Cc: Java Programmers List
Subject: [java] RE: CODI 1.0.1 NPE in JSF ResourceHandler when evaluating
ValueExpression
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
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 th
> > To: MyFaces Discussion
> > Cc:
> > Sent: Thursday, February 16, 2012 5:05 PM
> > Subject: Re: CODI 1.0.1 NPE in JSF ResourceHandler when evaluating
> ValueExpression
> >
> > hi christian,
> >
> > the short answer is: no - it was never intende
erhard Petracek
> To: MyFaces Discussion
> Cc:
> Sent: Thursday, February 16, 2012 5:05 PM
> Subject: Re: CODI 1.0.1 NPE in JSF ResourceHandler when evaluating
> ValueExpression
>
> hi christian,
>
> the short answer is: no - it was never intended to support it.
>
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
> Thank you very much gerhard!
>
> I just implemented a test for the prob
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 ch
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
Profess
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 that
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 request-lifecyc
14 matches
Mail list logo
