Found the issue. Had an AbstractController class that didn't implement
Serializable, which threw MyFaces off. Kudos to Thomas Andraschko for
pointing that out to me via PM.
On 04/30/2014 12:05 AM, Romain Manni-Bucau wrote:
Hi
If it is a @ManagedBean (jsf) it should work fine.
The best to do is surely to ask primefaces then myfaces and us. In all
cases providing a little sample will help.
Le 30 avr. 2014 03:36, "Kay Wrobel" <[email protected]> a écrit :
The issue seems to be bigger than ActionListener not firing as it seems
none of the AJAX events are actually firing. I have to get in touch with
PrimeFaces team. They need to do some testing with TomEE.
On 4/29/14, 3:28 PM, Kay Wrobel wrote:
Hi guys.
Not sure if this is a topic I should post here on in the MyFaces group. I
have a particular problem with my code. I am the developer of the NetBeans
PrimeFaces CRUD Generator, and I'm currently implementing a feature that
I'm testing against various containers and also under CDI and non-CDI
projects. The problem I'm running into with Tomee 1.6.0 Web Profile is as
follows:
I have a PrimeFaces Menu Item that uses an ActionListener in its backing
bean. When I use CDI, the backing bean's action listener method gets called
properly. However, when I don't use CDI, the ActionListener method never
gets called. The code under both circumstances looks exactly the same.
Also, when I create the same exact project targeting GlassFish 3.1.2.2 (old
version that only supports JSF 2.1 and JavaEE 6; similar to TomEE) the same
ActionListener code does get executed properly.
So I wonder if this is a flaw in MyFaces maybe? Does anyone know what
might be causing Apache TomEE not to execute the ActionListener?
Thanks for any help, guys.
Kay
