Am 13.12.2012 00:45, schrieb Denis Forveille:
Le 2012-12-12 18:27, Christian Beikov a écrit :
Sorry I mixed up your 3 emails a bit. Answers inline.
Am 13.12.2012 00:01, schrieb Denis Forveille:
This is the pattern defined by Seam 2 all the way and the assumption
on which it has been designed
Le 2012-12-12 18:27, Christian Beikov a écrit :
Sorry I mixed up your 3 emails a bit. Answers inline.
Am 13.12.2012 00:01, schrieb Denis Forveille:
This is the pattern defined by Seam 2 all the way and the assumption on which
it has been designed on first place...
I don't really understand
Sorry I mixed up your 3 emails a bit. Answers inline.
Am 13.12.2012 00:01, schrieb Denis Forveille:
This is the pattern defined by Seam 2 all the way and the assumption
on which it has been designed on first place...
I don't really understand your points, mostly I think because it seems
you
This is the pattern defined by Seam 2 all the way and the assumption on which
it has been designed on first place...
I don't really understand your points, mostly I think because it seems you
describe patterns we don't use..
At high level, our classes are organized like this :
- "Managers" cla
Why do you want to scope something that is stateless? I mean stateless
already is some kind of scope, like pooled application scoped. Since you
don't want to have a state in a stateless bean, why using a scope that
will cause destroying the instance after conversation end?
You should maybe con
Bad news: In fact, in practice this does not work for us.
We are moving from seam 2/jsf1.2 to cdi/jsf2.0/codi and we use SLSB
(Stateless Session Beans) as JSF backing beans.
Those SLSB may be of scope "ViewScope" (= Seam 2 "PageScope") and need
to be injected at leats "FacesContext" (to send back
I forgot to say that when I use the CDI @ConversationScoped standard
annotation, it works
The code fail if I use CODI @ConversationScoped annotation
Also If I remove the @Stateful annotation to use a plain POJO instead
of a SFSB, it works too..
2012/12/12 Denis Forveille :
> Hello,
> In WebSphere
Hallo
Ok I tried to reproduce the error with your example with stock IE8
I was not able to reproduce it.
Can you provide a war with the isolated code which produces the error so
that I can have a deeper look at it.
Werner
Am 12.12.12 17:12, schrieb Werner Punz:
Thanks for the example, I w
Thanks for the example, I will look into the issue tomorrow morning, I
will keep you updated.
Werner
Am 12.12.12 16:59, schrieb Bashirazad, Wahid:
Hi,
my Ajax call is in a composite component:
Hi,
my Ajax call is in a composite component:
Wahid
An: users@myfaces.apache.org
Betreff
Hi, can you isolate the problem into a small example so that I can have
a look at it. It seems like you run into something in the
AjaxRequest.send method, which triggers an error internally.
I cannot reproduce the problem here with my testsuite, so an example
would be helpful.
Werner
Am 12
Hi everybody,
I have a problem with f:ajax tags in combination of newer Myfaces
versions and IE8.
In my test Ajax call doesn't work in MyFaces versions 2.0.16, 2.1.6 and
2.1.10. It works only when I start IE8 in compatibility mode.
With MyFaces versions 2.0.4 and 2.1.1 works everything fine.
12 matches
Mail list logo
