Re: [Trinidad] using multiple triggers

[Renzo Tomaselli]

Matthias, in this case I had some names forced by outer components - which included the current one - because they needed to know them for own partial triggering. Nevertheless your suggestion doesn't work either (just tried), same error. I feel that using EL for partial triggers fails, since the resolved value turns out to be a string, while a string[] is expected. -- Renzo Matthias Wessendorf wrote: Hi On Jan 28, 2008 12:54 PM, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: Hi, while using multiple triggers where a few names are achieved from EL, I get an exception from ELSupport.coerceToType(obj, type). E.g. while: partialTriggers="multiSelect multiAdd multiRemove multiUpdate" works fine, partialTriggers="multiSelect #{multiAdd} multiRemove #{multiUpdate}" does not work (having set multiAdd="multiAdd" in the component including the current one. In coerceToType call, I see obj="multiSelect multiAdd multiRemove multiUpdate", and type=java.lang.String[]. While it would be easy to patch ELSupport to split the incoming string so that matching succeeds - I wonder if I'm doing anything else wrong. why not doing this: partialTriggers="#{stringArrayThatContainsAllMyTriggers}" instead of "multi el" ? -M -- Renzo