API: "The identifier string has no binding"

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

For reference, as I cannot find anything related to this API error message on Google or in the ME+ manual: 

When trying to execute the following statement in Java, I got the SOAP-Fault message "The identifier string has no binding":

port.setValueAt(meOop, 1, new MEAny("string", "'To display: test'"));

Appearantly, it means that the identifier 'string'  is not recognized as one of the types that MEAny can have ("String" is though). This would be much clearer if there had been some quotes around the identifier name. Also, it would be very helpful to have a bit longer description, with a reference (numerical fault-code) as to why this fault occurred. In general, this may be lacking in the API.

In this specific case, perhaps the fault itself may be extended by stating the valid options for the bindings.

I hope these suggestions can be used in some future release.

Edited by JoostVanPinxten - 08.Aug.2012 at 13:11

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
JoostVanPinxten Members Profile Send Private Message Find Members Posts Add to Buddy List Member Joined: 01.Aug.2012 Location: Netherlands Points: 8	Post Options Post Reply Quote JoostVanPinxten Report Post Thanks(0) Quote Reply Topic: API: "The identifier string has no binding" Posted: 08.Aug.2012 at 12:46
	For reference, as I cannot find anything related to this API error message on Google or in the ME+ manual: When trying to execute the following statement in Java, I got the SOAP-Fault message "The identifier string has no binding": port.setValueAt(meOop, 1, new MEAny("string", "'To display: test'")); Appearantly, it means that the identifier 'string' is not recognized as one of the types that MEAny can have ("String" is though). This would be much clearer if there had been some quotes around the identifier name. Also, it would be very helpful to have a bit longer description, with a reference (numerical fault-code) as to why this fault occurred. In general, this may be lacking in the API. In this specific case, perhaps the fault itself may be extended by stating the valid options for the bindings. I hope these suggestions can be used in some future release. Edited by JoostVanPinxten - 08.Aug.2012 at 13:11