Hi Thinking more about it, check if both composite components define the attribute with method-signature. In theory, if there is a bug, it should be possible to reproduce it excluding primefaces and using actionListener or valueChangeListener instead. But first try the syntax using "targets" instead the cc EL expression.
regards, Leonardo 2012/7/23 l.pe...@senat.fr <l.pe...@senat.fr>: > On 23/07/2012 18:22, l.pe...@senat.fr wrote: >> >> On 23/07/2012 17:53, Leonardo Uribe wrote: >>> >>> Hi >>> >>> Look the javadoc for composite:attribute "targets" property. It says >>> something like this: >> >> Well, I did that and the bug still occurs. >> >> I am trying to use jboss-el to avoid it... > > I finally used glashfish el 2.2 implementation, following standard procedure > (remove original el-api.jar file, copy api and impl jar file in server lib > dir, modify web.xml...) and I still have the very same bug. > > So, maybe it is not an el implementation bug ? > > Best regards, > > > Ludovic > | > | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. > | >
