Explanation | The specified service cannot be located |
Action | Verify that you have defined a service with the specified name in the RpcAdapterConfig.xml file. |
Explanation | The HTTP method, which invoked the method, is not supported. |
Action | Invoke the method for the service using the HTTP method that is specified in the RPCAdapterConfig.xml file. This method is the same method that is specified in the error message. The RPCAdapterConfig.xml file is located in the WEB-INF directory of your application Web archive (WAR) file. |
Explanation | This error occurs when you specify only some of the parameters, either all or none must be specified. |
Action | Open the RpcAdapterConfig.xml file, which is located in the WEB-INF directory of your application Web archive (WAR) file. Specify all of the parameters for the method. |
Explanation | The specified method cannot be located. |
Action | Verify that you have defined a method with the specified name in the RpcAdapterConfig.xml file. |
Explanation | The RpcAdapterConfig.xml file is not present in the WEB-INF directory within your application Web archive (WAR) file or it is not well formed. |
Action | Validate the RpcAdapterConfig.xml file against its schema and fix the errors. |
Explanation | The RPC Adapter cannot instantiate an object of the specified validator class. |
Action | Verify that the class is in the format that is required by the RPC Adapter. For example, the class should extend the com.ibm.websphere.rpcadapter.Validator class. Also, the class should have a public constructor with no parameter arguments. |
Explanation | The specified POJO entity model cannot be instantiated. |
Action | Examine the POJO entity model for errors that can prevent it from being instantiated. For example, an error cannot occur if the POJO entity model does not have a default constructor. |
Explanation | The Remote Procedure Call does not contain the correct number of parameters. |
Action | Make the Remote Procedure Call with the correct number of parameters. |
Explanation | The specified method parameter failed the validation process. |
Action | Verify that the specified parameter for the method is valid. |
Explanation | Either the method is on the black list and unsupported or is not present for the service class. |
Action | Verify that the method is present for the service class. If it is present, then verify that the method is supported. |
Explanation | This error can occur because the schema is not present or a validating XML parser does not exist in the class path. |
Action | Verify that a validating XML parser exists in the class path. |
Explanation | This error occurs when the invocation of the exposed Plain Old Java Object (POJO) method results in an exception. |
Action | Check the stackTrace variable of the error object for the stack trace of the error that occurred. |
Explanation | The specified EJB file cannot be instantiated. |
Action | Examine the EJB file for errors that can prevent it from being instantiated. |
Explanation | The method failed to lookup the specified EJB file. |
Action | Verify that the specified remote and home names are correct. Also, verify that the specified jndi-name value for the lookup is correct. If you are using Enterprise JavaBeans (EJB) file Version 2.1, make sure that there is an entry for EJB modules in web.xml file. |
Explanation | The method failed to invoke the create method. |
Action | Verify the parameters, which are specified for create node in the RPCAdapterConfig.xml file, are correct. Also, verify that the create method is available in the Enterprise JavaBeans (EJB) module. The RPCAdapaterConfig.xml file exists in the WEB-INF directory within your application Web archive (WAR) file. |
Explanation | One or more of the methods under a service are not configured correctly. |
Action | Check the methods that are configured with the implementation of the class. Ensure that the parameter types for any overloaded methods are listed correctly. |
Explanation | The class specified in the init-param code of the web.xml file cannot be found. This error also can occur when the annotated elements in the class comply with the design. |
Action | Check the stackTrace variable of the error object for the stack trace of the error that occurred. |
Explanation | The web.xml file is configured for annotations, but the RPCAdapter-annotation.jar file cannot be located in the class path. |
Action | Update the class path to include the location of the RPCAdapter-annotation.jar file. |