Andrew,

 

We you use managed beans and EL, there is an "automatic" translation to getter and setter, which means when you use the EL :

 

#{bCase.updateAttachments} 

 

the method called when you read data (i.e. getter) the method called is the method getUpdateAttachments of the bean bCase. When you use the bean to set data, the method called will be setUpdateAttachments.

 

So from what you show in your code, I suppose your method in the bean is called "updateAttachments". If it's the case, try to change the name of the method in the bean to "getUpdateAttachments" and your EL should work.

 

But then if you use SSJS, you will have to change your code to bCase.getUpdateAttachments()

 

Hope this helps

Renaud 

Thanks for the reply Renaud

 

I understand the translation of the EL name to the bean method name, however this is only necessary when getting and setting properties.

If calling an server side action  from an event handler you can use the exact method name. The beforePageLoad parameter also takes an untranslated method name.

 

e.g. 

    beforePageLoad="#{bCase.validateAttachments}" 

calls

    public void validateAttachments() {

        ....code...
    } 

 

 

Still, in case that was the issue I added an additional method to the bean - however I still get the illegal argument exception

 

    public void getUpdateAttachments() {
        updateAttachments();
    }

 

    public void updateAttachments() {
        ....code...
    }
 

 I can work around this by using the javascript call, but I want to improve my understanding of why this isn't working as expected