Invoke method with output parameters

Hello,

Just a quick reply.

Is the r-code up to date?

Is the deployed WAR file up to date?

It would be interesting to see how the invoke method looks like at the REST Adapter level.

The PAAR file in the WEB-INF/adapters subdirectory is a zip file. You can make a copy and rename it to zip to extract its content. The mapping.xml file could give you and idea on what parameters the REST Adapter is expecting for method1 and then compare it to what the Business Entity (and corresponding r-code) has.

(in 11.4 you can query this information by using the URL.)

I hope this helps.

Hello,

Thank you for checking the mapping.xml file.

There are two sections in the mapping.xml file: mapInput and mapOutput.

The text that you posted, which seems to be for mapInput section, seems fine. It shows two input parameters.

The mapOutput section should have a something like the following (two output parameters, one string and one integer):

   <conditional:conditionalRuleSet>

     <conditional:if condition="${(rest.resourcename == 'Class1_method1') and (rest.operationname == 'Class1..method1') and (rest.verb == 'PUT')}">

   <mapping:rule source="${idl.param['output_parameter1']}" target="${json.object['response'].string['output_parameter1']}"/>

   <mapping:rule source="${idl.param['output_parameter2']}" target="${json.object['response'].integervalue['output_parameter2']}"/>

     </conditional:if>

   </conditional:conditionalRuleSet>

Do you have this in your mappinp.xml file?

Thanks.

> Could not locate method '<method-name>' with matching signature in class '<class-name>'. (14457)

The REST Adapter uses the Open Client API to access the method in the AppServer.

The error message that you are getting indicates that "method1" is in the Business Entity but the signature does not match. (Error 12927 would be shown if the method is not found in the class.)

You have already mentioned that the r-code and war file are up to date. Still, it looks like the r-code that is being accessed is not the same one that you expect. Could this be an issue related to the PROPATH?

Some troubleshooting suggestions.

You could remove the r-code and move the code out of the PROPATH to see if I get a different error messages.

Or could try adding a different version of the method, perhaps, one with no parameters to see if that happens to be the matching signature.

Perhaps, the next step would be to contact Technical Support to see if they can take a look at your system.

Thanks.

RE: Invoke method with output parameters

Reply by egarcia

> Could not locate method '<method-name>' with matching signature in class '<class-name>'. (14457)

The REST Adapter uses the Open Client API to access the method in the AppServer.

The error message that you are getting indicates that "method1" is in the Business Entity but the signature does not match. (Error 12927 would be shown if the method is not found in the class.)

You have already mentioned that the r-code and war file are up to date. Still, it looks like the r-code that is being accessed is not the same one that you expect. Could this be an issue related to the PROPATH?

Some troubleshooting suggestions.

You could remove the r-code and move the code out of the PROPATH to see if I get a different error messages.

Or could try adding a different version of the method, perhaps, one with no parameters to see if that happens to be the matching signature.

Perhaps, the next step would be to contact Technical Support to see if they can take a look at your system.

Thanks.

Stop receiving emails on this subject.

Flag this post as spam/abuse.