Explanation | None. |
Action | None. |
Explanation | An internal error occurred. |
Action | None. |
Explanation | Starting JSR109 validation of the specified module. |
Action | Information only, no action is required. |
Explanation | The webservice.xml or webservicesclient.xml file, which is referenced in the Web Services Description Language (WSDL) file, cannot be found in this module. |
Action | Add the WSDL file to the module. |
Explanation | The webservice.xml or webservicesclient.xml file, which is referenced in the Web Services Description Language (WSDL) file, cannot be found in this module. |
Action | Add the JAX-RPC mapping file to the module. |
Explanation | The webservice.xml or webservicesclient.xml references a class, which the Application Server cannot find in this module. |
Action | Add the specified service endpoint interface to the module. |
Explanation | The service endpoint interface must follow the JAX-RPC rules for the Web Services Description Language (WSDL) file to Java mapping. |
Action | Change the declaration of the specified interface to extend the java.rmi.Remote interface. |
Explanation | The service endpoint interface must follow the JAX-RPC rules for Web Services Description Language (WSDL) file to Java mapping. The JAX-RPC rules require that all interface methods create the java.rmi.RemoteException exception. |
Action | Change the declaration of the specified method in the service endpoint interface to create the java.rmi.RemoteException exception. |
Explanation | The service endpoint interface must follow the JAX-RPC rules for the Web Services Description Language (WSDL) file to Java mapping. The JAX-RPC rules specify that the method parameters and return types must be the JAX-RPC supported types. |
Action | Change the declaration for the specified method in the service endpoint interface to use the JAX-RPC supported types. |
Explanation | The service endpoint interface must follow the JAX-RPC rules for the Web Services Description Language (WSDL) file to Java mapping. The JAX-RPC rules require that all referenced types are JAX-RPC serializable. |
Action | Change the declaration for the specified method in the service endpoint interface to use JAX-RPC supported types. |
Explanation | The service endpoint interface must follow the JAX-RPC rules for the Web Services Description Language (WSDL) file to Java mapping. The JAX-RPC rules specify that the service endpoint interface class must not include constant, as public final static, declarations. |
Action | Delete the specified field in the interface. |
Explanation | The specified class for the service implementation must have a default public constructor to be a stateless session Enterprise JavaBeans (EJB) file. |
Action | Add a public default constructor to the class. |
Explanation | The implementation class must implement the methods of the service endpoint interface. |
Action | Implement all of the method signatures in the specified class for the service endpoint interface. |
Explanation | The business methods of the class must be public. |
Action | Change the visibility for the specified method in the class to public. |
Explanation | The business methods of the class must not be final. |
Action | Remove the final modifier for the method specified in the class. |
Explanation | The business methods of the class must not be static. |
Action | Remove the static modifier for the method specified in the class. |
Explanation | The service implementation class must be public, must not be final and must not be abstract. |
Action | Change the visibility for the service implementation class to public. |
Explanation | The service implementation class must be public, must not be final and must not be abstract. |
Action | Remove the final modifier for the service implementation class. |
Explanation | The service implementation class must be public, must not be final and must not be abstract. |
Action | Remove the abstract modifier for the service implementation class. |
Explanation | A service implementation class must not define the finalize method. |
Action | Remove the finalize method from the service implementation class. |
Explanation | You can use an existing Enterprise JavaBeans (EJB) file as a service implementation bean. However, the transaction attributes of the service endpoint interface methods cannot include the Mandatory attribute. |
Action | Remove the Mandatory attribute from the transaction attributes of the specified method in the class. |
Explanation | The Application Server cannot find the service implementation class in this module. |
Action | Add the service implementation class to the module. |
Explanation | You must define the service implementation classes that use a session bean in the ejb-jar.xml deployment descriptor file using the session element. You cannot declare the classes with a stateful session-type. |
Action | Define the Enterprise JavaBeans (EJB) file in the ejb-jar.xml file to have a stateless session type. |
Explanation | You must define service implementations in the ejb-jar.xml deployment descriptor file using the session element. |
Action | Define the class in the ejb-jar.xml file using the session element of enterprise-beans. |
Explanation | The servlet-link element must refer to a servlet in the web.xml file. |
Action | Add the servlet or change the servlet definition in the web.xml file. |
Explanation | If the wsdl-file element is not specified in the webservicesclient.xml file, do not specify the jaxrpc-mapping-file element. |
Action | Remove mapping file or add a wsdl-file element in webservicesclient.xml. |
Explanation | You cannot package generated stubs. |
Action | Remove all of the generated stubs from the module. |
Explanation | The value of the ejb-link element must be the ejb-name element of an enterprise bean in the same module. |
Action | Add the enterprise bean or change the ejb-link definition in the ejb-jar.xml file. |
Explanation | The component-name element defines a link to a component name, such as the ejb-name element, in the module deployment descriptor. Its value must exist in the module-level deployment descriptor. |
Action | Change the component-name element to refer to a ejb-name element in the ejb-jar.xml file. |
Explanation | The value of a port-component-link element must be the port-component-name element of a port-component element in the same module or another module with in the same application unit. |
Action | Add the port component or change the reference in the service-ref element of the webservicesclient.xml file. |
Explanation | A servlet must only be referenced by a single port-component element. A session enterprise bean file must only be referenced by a single port-component element. |
Action | Change either the port component or the port component so that they do not both reference the implementation class. |
Explanation | You cannot specify more than one servlet-mapping element for a servlet that is referenced by a port-component element. |
Action | Remove duplicate servlet mappings for the servlet in the web.xml file. |
Explanation | The url-pattern of the servlet-mapping element must be an exact match pattern. |
Action | Change the servlet mapping for the servlet so that it does not contain an asterisk. |
Explanation | When you provide a binding for a port-component-ref element, you must ensure that the port-component-ref element is compatible with the port to which it is being bound. |
Action | Change the port so that it is compatible with the Service Endpoint Interface. |
Explanation | You can only associate one mapping file with a wsdl-file element. |
Action | Specify a unique mapping file for the wsdl-file element in the webservicesclient.xml file. |
Explanation | You must specify the jaxrpc-mapping-file element if you specified the wsdl-file element. |
Action | Add a jaxrpc-mapping-file element to the webservicesclient.xml file. |
Explanation | The serviceRefLink element must name a service-ref element in the webservicesclient.xml file. |
Action | Correct the serviceRefLink element so that it names a service-ref element in the webservicesclient.xml file. |
Explanation | The deployedWSDLFile element must be the relative path within the module of the Web Services Description Language (WSDL) file. |
Action | Correct the path or add the Web Services Description Language (WSDL) file in the specified path. |
Explanation | The defaultMappings element must reference a port and portType in the wsdl-file element that is associated with the service-ref element. |
Action | Correct the attributes of the defaultMappings element to refer to a port and portType in the Web Services Description Language (WSDL) file. |
Explanation | The portQnameBindings attibutes must reference a port in the wsdl-file element that is associated with the service-ref element. |
Action | Correct the portQnameBindings attributes to refer to a port in the file. |
Explanation | The componentNameLink attribute must reference a component-name element in the webservicesclient.xml file. |
Action | Modify the componentNameLink attribute to match a component-name element in the webservicesclient.xml file. |
Explanation | The scope attribute reference must be a Request, Session, or Application reference. |
Action | Correct the scope attribute. |
Explanation | The pcNameLink attribute must reference a port-component-name element in the webservices.xml file. |
Action | Modify the pcNameLink attribute so that it matches a port-component-name element in the webservices.xml file. |
Explanation | The wsDescNameLink attribute must reference a webservice-description element in the webservices.xml file. |
Action | Modify the wsDescNameLink attribute to match a webservice-description-name element in the webservices.xml file. |
Explanation | The routerModules name attribute must reference a module in the current application. |
Action | Either repair the routerModules name or delete the routerModules element and run the endptEnabler command again on the application. |
Explanation | The webservicesclient.xml file did not specify the value for the required service-interface element. |
Action | Add the valid value for the service-interface element. |
Explanation | The webservicesclient.xml file did not specify the value for the required service-endpoint-interface element. |
Action | Add the valid value for the service-endpoint-interface element. |
Explanation | The class that is specified in the service-endpoint-interface element must be an interface. |
Action | Specify an interface for the service-endpoint-interface element. |
Explanation | The servlet-link element can exist in a webservices.xml file within Web modules only. |
Action | Change the servlet-link element in the webservices.xml file to an ejb-link element. |
Explanation | The ejb-link element can exist in a webservices.xml file within Enterprise JavaBeans (EJB) modules only. |
Action | Change the ejb-link element in the webservices.xml file to a servlet-link element. |
Explanation | The servlet-link element must exist in the webservices.xml file within Web modules. |
Action | Add a servlet-link element to the webservices.xml file. |
Explanation | An ejb-link element must exist in the webservices.xml file within Enterprise JavaBeans (EJB) modules. |
Action | Add an ejb-link element to the webservices.xml file. |
Explanation | The Application Server encountered a SAXParseException exception when it read the specified descriptor. |
Action | Correct the problem that exists in the file. |
Explanation | An exception occurred when the Application Server read the specified descriptor. |
Action | Correct the problem that exists in the file. |
Explanation | A service-impl-bean element must exist for each port component within the webservices.xml file. |
Action | Add a service-impl-bean element to the webservices.xml file. |
Explanation | A webservice-description-name attribute must exist for each webservice-description element in the webservices.xml file. |
Action | Add a webservice-description-name attribute to each webservice-description element in the webservices.xml file. |
Explanation | A webservice-description element must exist in the webservices.xml file. |
Action | Add a webservice-description element to the webservices.xml file. |
Explanation | A wsdl-file element must exist in each webservice-description element in the webservices.xml file. |
Action | Add a wsdl-file element to each webservice-description element in the webservices.xml file. |
Explanation | A jaxrpc-mapping-file element must exist in each webservice-description element in the webservices.xml file. |
Action | Add a jaxrpc-mapping-file element to each webservice-description element in the webservices.xml file. |
Explanation | A pcNameLink attribute must exist in each pcBindings element within the ibm-webservices-bnd.xmi file. |
Action | Add a pcNameLink attribute to each pcBindings element within the ibm-webservices-bnd.xmi file. |
Explanation | A port-component-name element must exist in each webservice-description element within the webservices.xml file. |
Action | Add a port-component-name element to each webservice-description element within the webservices.xml file. |
Explanation | A wsDescNameLink attribute must exist in each wsdescBindings element within the ibm-webservices-bnd.xmi file. |
Action | Add a wsDescNameLink attribute to each wsdescBindings element within the ibm-webservices.xmi file. |
Explanation | The component-name element must exist for each component-scoped-ref element in the webservicesclient.xml file. |
Action | Add a component-name element to refer to a ejb-name element within the ejb-jar.xml file. |
Explanation | The service-ref-name element must exist for each service-ref element in the webservicesclient.xml file. |
Action | Add a service-ref-name element to each service-ref element in the webservicesclient.xml file. |
Explanation | The service-ref element must exist in the webservicesclient.xml file. |
Action | Add a service-ref element to the webservicesclient.xml file. |
Explanation | A componentNameLink attribute must exist in each componentScopedRefs element within the ibm-webservicesclient-bnd.xmi element. |
Action | Add a componentNameLink attribute whose value is a component-name element in the webservices.xml file. |
Explanation | The Application Server encountered a SAXParseException exception when it read the binding file. |
Action | Correct the problem that exists in the file. |
Explanation | A serviceRefLink attribute must exist in each serviceRefs element within the ibm-webservicesclient-bnd.xmi file. |
Action | Add a serviceRefLink attribute whose value is a service-ref-name element in the webservices.xml file. |
Explanation | The service-endpoint-interface element must exist in each port-component element in the webservices.xml file. |
Action | Add a service-endpoint-interface element to the port-component element in the webservices.xml file. |
Explanation | Either a component-scoped-refs or service-ref element must exist in the webservicesclient.xml file. |
Action | Add a service-ref element or component-scoped-refs element to the webservicesclient.xml file. |
Explanation | A port-component element must exist in each webservice-description element within the webservices.xml file. |
Action | Add a port-component element to each webservice-description element within the webservices.xml file. |
Explanation | The indicated type is supported by this implementation. However, the type is not part of the JAX-RPC specification. |
Action | Review the use of the type to verify that standards compliance is not required. |
Explanation | The indicated type is supported by this implementation. However, the type is not part of the JAX-RPC specification. |
Action | Review the use of the type to verify that standards compliance is not required. |
Explanation | JAX-RPC Types that implement the java.rmi.Remote interface are prohibited by the JAX-RPC specification. |
Action | Modify the type so that it does not implement java.rmi.Remote interface. |
Explanation | JAX-RPC Types that implement the java.rmi.Remote interface are prohibited by the JAX-RPC specification. |
Action | Modify the type so that it does not implement java.rmi.Remote interface. |
Explanation | Types that implement the javax.xml.rpc.holders.Holder interface must have a public field named value. |
Action | Ensure that the type has a public field named value. |
Explanation | Add a public default constructor to the class. |
Action | Add a public default constructor to class. |
Explanation | Add a public default constructor to the class. |
Action | Add a public default constructor to class. |
Explanation | The component-scoped-refs element is required in the webservicesclient.xml file within Enterprise JavaBeans (EJB) modules. The element specifies which EJB module is being configured as a Web services client. |
Action | Add a component-scoped-refs element to the webservicesclient.xml file with a component-name element that specifies the ejb-name reference of the client Enterprise JavaBeans (EJB) module. |