Express (Distributed operating systems), v8.0 > Reference > Messages
CHKW
CHKW6000E: J2EE Web Services validation failed: {0}.
Explanation None. Action None.
CHKW6001E: Access of model from IHelper failed.
Explanation An internal error occurred. Action None.
CHKW6002I: Validating webservices in {0}.
Explanation Starting JSR109 validation of the specified module. Action Information only, no action is required.
CHKW6003E: WSDL file {0} was not found in this module. (JSR109 1.0: 4.2.6)
Explanation The webservice.xml or webservicesclient.xml file, which is referenced in the WSDL file, cannot be found in this module. Action Add the WSDL file to the module.
CHKW6004E: JAX-RPC mapping file {0} was not found in this module. (JSR109 1.0: 4.2.6)
Explanation The webservice.xml or webservicesclient.xml file, which is referenced in the WSDL file, cannot be found in this module. Action Add the JAX-RPC mapping file to the module.
CHKW6005E: Service Endpoint Interface {0} was not found in this module. (JSR109 1.0: 4.2.6)
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.
CHKW6006E: Service Endpoint Interface {0} must extend java.rmi.Remote either directly or indirectly. (JSR109 1.0: 5.3.1)
Explanation The service endpoint interface must follow the JAX-RPC rules for the WSDL file to Java mapping. Action Change the declaration of the specified interface to extend the java.rmi.Remote interface.
CHKW6007E: Method {0} in Service Endpoint Interface {1} does not throw java.rmi.RemoteException. (JSR109 1.0: 5.3.1)
Explanation The service endpoint interface must follow the JAX-RPC rules for 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.
CHKW6008E: Method {0} in Service Endpoint Interface {1} uses type {2}, which is not a JAX-RPC supported type. (JSR109 1.0: 5.3.1)
Explanation The service endpoint interface must follow the JAX-RPC rules for the 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.
CHKW6009E: Method {0} in Service Endpoint Interface {1} uses type {2}, which is not a JAX-RPC serializable type. (JSR109 1.0: 5.3.1)
Explanation The service endpoint interface must follow the JAX-RPC rules for the 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.
CHKW6010E: Constant field {0} in interface {1} is not permitted. (JAX-RPC 1.0: 5.2)
Explanation The service endpoint interface must follow the JAX-RPC rules for the 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.
CHKW6011E: Default public constructor for service implementation class {0} was not found. (JSR109 1.0: 5.3.2.1)
Explanation The specified class for the service implementation must have a default public constructor to be a stateless session EJB file. Action Add a public default constructor to the class.
CHKW6012E: Class {0} does not implement method {1} of the Service Endpoint Interface {2}. (JSR109 1.0: 5.3.2.1)
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.
CHKW6013E: The visibility for method {0} in class {1} must be public. (JSR109 1.0: 5.3.2.1)
Explanation The business methods of the class must be public. Action Change the visibility for the specified method in the class to public.
CHKW6014E: Method {0} in class {1} must not be final. (JSR109 1.0: 5.3.2.1)
Explanation The business methods of the class must not be final. Action Remove the final modifier for the method specified in the class.
CHKW6015E: Method {0} in class {1} must not be static. (JSR109 1.0: 5.3.2.1)
Explanation The business methods of the class must not be static. Action Remove the static modifier for the method specified in the class.
CHKW6016E: The visibility for the service implementation class {0} must be public. (JSR109 1.0: 5.3.2.1)
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.
CHKW6017E: The service implementation class {0} must not be declared final. (JSR109 1.0: 5.3.2.1)
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.
CHKW6018E: Service implementation class {0} must not be declared abstract. (JSR109 1.0: 5.3.2.1)
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.
CHKW6019E: Service implementation class {0} must not contain a finalize() method. (JSR109 1.0: 5.3.2.1)
Explanation A service implementation class must not define the finalize method. Action Remove the finalize method from the service implementation class.
CHKW6020E: The transaction attributes of method {0} in class {1} must not include Mandatory. (JSR109 1.0: 5.3.2.1.3)
Explanation We can use an existing 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.
CHKW6021E: Service implementation class {0} was not found in this module. (JSR109 1.0: 5.4)
Explanation The Application Server cannot find the service implementation class in this module. Action Add the service implementation class to the module.
CHKW6022E: Session EJB {0} must be declared as Stateless in ejb-jar.xml. (JSR109 1.0: 7.1.2)
Explanation We must define the service implementation classes that use a session bean in the ejb-jar.xml deployment descriptor file using the session element. We cannot declare the classes with a stateful session-type. Action Define the EJB file in the ejb-jar.xml file to have a stateless session type.
CHKW6023E: Enterprise-beans class {0} defined in ejb-jar.xml must be a session bean. (JSR109 1.0: 7.1.2)
Explanation We 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.
CHKW6024E: The value of the servlet-link attribute {0} does not correspond to an servlet definition in web.xml. (JSR109 1.0: 7.1.2)
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.
CHKW6025E: Mapping file {0} must not be specified when no wsdl-file element is specified in webservicesclient.xml. (JSR109 1.0: 4.2.2.6)
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.
CHKW6026W: Stub file {0} should not be packaged in module {1}. (JSR109 1.0: 4.2.6)
Explanation We cannot package generated stubs. Action Remove all of the generated stubs from the module.
CHKW6027E: The value of the ejb-link attribute {0} does not correspond to an Enterprise Bean definition in the module file {1}. (JSR109 1.0: 7.1.5)
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.
CHKW6028E: The component-name element {0} does not refer to an ejb-name element in the ejb-jar.xml. (JSR109 1.0: 7.2.5)
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.
CHKW6029E: Could not find the port component named {0} referenced by port-component-link in service-ref {1} of webservicesclient.xml. (JSR109 1.0: 7.2.5)
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.
CHKW6030E: Implementation class {0} referred to by port components {1} and {2}. (JSR109 1.0: 7.1.2)
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.
CHKW6031E: Multiple servlet mappings detected for servlet named {0} in web.xml. (JSR109 1.0: 7.1.2)
Explanation We 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.
CHKW6032E: Servlet mapping for servlet {0} must not contain an asterisk in the url-pattern. (JSR109 1.0: 7.1.2)
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.
CHKW6033E: Port {0} is not compatible with Service Endpoint Interface {1}. (JSR109 1.0: 8.3)
Explanation When provided a binding for a port-component-ref element, 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.
CHKW6034E: wsdl-file {0} cannot use both mapping files {1} and {2}. (JSR109 1.0: 7.2.2)
Explanation We 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.
CHKW6035E: Missing jaxrpc-mapping-file in webservicesclient.xml. (JSR109 1.0: 7.2.2)
Explanation We 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.
CHKW6036E: The serviceRefLink {0} specified in ibm-webservicesclient-bnd.xmi is not the name of a service-ref in webservicesclient.xml.
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.
CHKW6037E: The deployedWSDLFile path {0} specified in ibm-webservicesclient-bnd.xmi does not reference a WSDL file in this module.
Explanation The deployedWSDLFile element must be the relative path within the module of the WSDL file. Action Correct the path or add the WSDL file in the specified path.
CHKW6038E: The defaultMappings element specified for service-ref {0} in ibm-webservicesclient-bnd.xmi references portType {1} or port {2} that is not present in WSDL file {3}.
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 WSDL file.
CHKW6039E: The portQnameBindings port name {0} specified for service-ref {1} in ibm-webservicesclient-bnd.xmi references a port that is not present in WSDL file {2}.
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.
CHKW6040E: The componentNameLink attribute {0} in ibm-webservicesclient-bnd.xmi references a component-name that does not exist in webservicesclient.xml.
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.
CHKW6041E: The scope attribute {0} specified for port-component {1} in ibm-webservices-bnd.xmi is not Request, Session, or Application.
Explanation The scope attribute reference must be a Request, Session, or Application reference. Action Correct the scope attribute.
CHKW6042E: The pcNameLink attribute {0} specified for webservice-description {1} in ibm-webservices-bnd.xmi references a port-component that does not exist in webservices.xml.
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.
CHKW6043E: The wsDescNameLink attribute {0} specified in ibm-webservices-bnd.xmi references a webservice-description-name that does not exist in webservices.xml.
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.
CHKW6045E: The routerModules name {0} in ibm-webservices-bnd.xmi references a module that does not exist in the application.
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.
CHKW6046E: No Service Interface specified in the service-interface element for service-ref {0} in webservicesclient.xml. (JSR109 1.0: 4.2.2)
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.
CHKW6047E: No Service Endpoint Interface specified in a service-endpoint-interface element in service-ref {0} in webservicesclient.xml. (JSR109 1.0: 7.2.3)
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.
CHKW6048E: Service Endpoint Interface {0} in {1} is not an interface. (JSR109 1.0: 3.10)
Explanation The class specified in the service-endpoint-interface element must be an interface. Action Specify an interface for the service-endpoint-interface element.
CHKW6049E: Servlet-link element {0} in port component {1} in webservices.xml should be ejb-link for EJB modules. (JSR109 1.0: 7.1.2)
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.
CHKW6050E: Ejb-link element {0} in port component {1} in webservices.xml should be servlet-link for Web modules. (JSR109 1.0: 7.1.2)
Explanation The ejb-link element can exist in a webservices.xml file within EJB modules only. Action Change the ejb-link element in the webservices.xml file to a servlet-link element.
CHKW6051E: Required servlet-link element was not found for port component {0} in webservices.xml. (JSR109 1.0: 7.1.2)
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.
CHKW6052E: Required ejb-link element was not found for port component {0} in webservices.xml. (JSR109 1.0: 5.3.2.1.3)
Explanation An ejb-link element must exist in the webservices.xml file within EJB modules. Action Add an ejb-link element to the webservices.xml file.
CHKW6053E: Parse error in {0}: {1}: {2}. (JSR109 1.0: 7.1, 7.2)
Explanation The Application Server encountered a SAXParseException exception when it read the specified descriptor. Action Correct the problem that exists in the file.
CHKW6054E: Error in {0}: {1}: {2}.
Explanation An exception occurred when the Application Server read the specified descriptor. Action Correct the problem that exists in the file.
CHKW6055E: Required service-impl-bean element was not found for port component {0} in webservices.xml. (JSR109 1.0: 5.3.2.1.3)
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.
CHKW6056E: Required webservice-description-name attribute was not found in webservices.xml. (JSR109 1.0: 7.1.5)
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.
CHKW6057E: Required webservice-description element was not found in webservices.xml. (JSR109 1.0: 7.1.5)
Explanation A webservice-description element must exist in the webservices.xml file. Action Add a webservice-description element to the webservices.xml file.
CHKW6058E: Required wsdl-file element was not found in webservice-description {0} in webservices.xml. (JSR109 1.0: 7.1.5)
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.
CHKW6059E: Required jaxrpc-mapping-file element was not found in webservice-description {0} in webservices.xml. (JSR109 1.0: 7.1.5)
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.
CHKW6060E: Required pcNameLink attribute was not found in ibm-webservices-bnd.xmi.
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.
CHKW6061E: Required port-component-name element was not found in webservice-description {0} in webservices.xml.(JSR109 1.0: 7.1.5)
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.
CHKW6062E: Required wsDescNameLink attribute was not found in ibm-webservices-bnd.xmi.
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.
CHKW6063E: Required component-name element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
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.
CHKW6064E: Required service-ref-name element was not found in service-ref in webservicesclient.xml. (JSR109 1.0: 7.2.5)
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.
CHKW6065E: Required service-ref element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Explanation The service-ref element must exist in the webservicesclient.xml file. Action Add a service-ref element to the webservicesclient.xml file.
CHKW6066E: Required componentNameLink attribute was not found in ibm-webservicesclient-bnd.xmi.
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.
CHKW6067E: Error in {0}: {1}: {2}.
Explanation The Application Server encountered a SAXParseException exception when it read the binding file. Action Correct the problem that exists in the file.
CHKW6068E: Required serviceRefLink attribute was not found in serviceRefs element ibm-webservicesclient-bnd.xmi.
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.
CHKW6069E: Required service-endpoint-interface element was not found in port-component {0} in webservices.xml. (JSR109 1.0: 7.1.5)
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.
CHKW6070E: Required component-scoped-refs element or service-ref element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
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.
CHKW6071E: Required port-component element was not found in webservice-description {0} in webservices.xml.(JSR109 1.0: 7.1.5)
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.
CHKW6072I: Type {0} in method {1} in JAX-RPC interface {2} is a non-standard extension to JAX-RPC.
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.
CHKW6073I: Type {0} in method {1} in JAX-RPC interface {2} references type {3} that is a non-standard extension to JAX-RPC.
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.
CHKW6074E: Type {0} in method {1} in JAX-RPC interface {2} must not implement java.rmi.Remote. (JAXRPC 1.0: 5.2.2)
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.
CHKW6075E: Type {3} referenced by type {0} in method {1} in JAX-RPC interface {2} must not implement java.rmi.Remote. (JAXRPC 1.0: 5.2.2)
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.
CHKW6076E: Type {0} in method {1} in JAX-RPC interface {2} implements javax.xml.rpc.holders.Holder, but has no public value field. (JAXRPC 1.0: 4.3.5)
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.
CHKW6077E: JAX-RPC value type {0} in method {1} in JAX-RPC interface {2} must have a public default constructor. (JAXRPC 1.0: 5.4)
Explanation Add a public default constructor to the class. Action Add a public default constructor to class.
CHKW6078E: JAX-RPC value type {3} referenced by type {0} in method {1} in JAX-RPC interface {2} must have a public default constructor. (JAXRPC 1.0: 5.4)
Explanation Add a public default constructor to the class. Action Add a public default constructor to class.
CHKW6079E: The webservicesclient.xml descriptor does not contain a component-scoped-refs element. This element is required for an EJB module. (JSR109 1.0: 7.2.2)
Explanation The component-scoped-refs element is required in the webservicesclient.xml file within 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 EJB module.