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 under
PARENT_FIRST for both, add manifest entries for the WAR
and EJB modules to the 2 CODI jsf jars (Tested OK)
in brief we need to configure WebSphere to use only one classloader
for the whole modules of the application (ejb+jpa+war+dependent jars)
2012/12/10 Denis Forveille :
Thanks Thomas for the poin
in brief we need to configure WebSphere to use only one classloader
for the whole modules of the application (ejb+jpa+war+dependent jars)
2012/12/10 Denis Forveille :
> Thanks Thomas for the pointer
> Yes it is a classloader problem
> After lots of tries I finally managed to have it w
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 Web
Thanks Thomas for the pointer
Yes it is a classloader problem
After lots of tries I finally managed to have it working
(FI our EAR projects are all split into a JPA module, an EJB module
and a WAR module)
How I did it:
- in ear/lib, define codi (api+impl) and message-module (api+impl)
- in web/WEB-
5 matches
Mail list logo