WebSphere Process Server messages     Operating Systems: All supported

CHKW JSR 109

CHKW6000E: J2EE Web Services validation failed: {0}.
Problem None.
User response None.
CHKW6001E: Access of model from IHelper failed.
Problem An internal error occurred.
User response None.
CHKW6002I: Validating webservices in {0}.
Problem Starting JSR109 validation of module {0}.
User response Information only, no action is required.
CHKW6003E: WSDL file {0} was not found in this module. (JSR109 1.0: 4.2.6)
Problem webservice.xml or webservicesclient.xml referred to file {0} that could not be found in this module.
User response Add a WSDL file named {0} in this module.
CHKW6004E: JAX-RPC mapping file {0} was not found in this module. (JSR109 1.0: 4.2.6)
Problem webservice.xml or webservicesclient.xml referred to file {0} that could not be found in this module.
User response Add a JAX-RPC mapping file named {0} in this module.
CHKW6005E: Service Endpoint Interface {0} was not found in this module. (JSR109 1.0: 4.2.6)
Problem webservice.xml or webservicesclient.xml referred to class {0} that could not be found in this module.
User response Add a Service Endpoint Interface named {0} in this module.
CHKW6006E: Service Endpoint Interface {0} must extend java.rmi.Remote either directly or indirectly. (JSR109 1.0: 5.3.1)
Problem The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping.
User response Change the declaration of interface {0} to extend java.rmi.Remote.
CHKW6007E: Method {0} in Service Endpoint Interface {1} does not throw java.rmi.RemoteException. (JSR109 1.0: 5.3.1)
Problem The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping. They require that all interface methods throw java.rmi.RemoteException.
User response Change the declaration of method {0} in {1} to throw java.rmi.RemoteException.
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)
Problem The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping. They specify that method parameters and return types must be the JAX-RPC supported types.
User response Change the declaration for method {0} in Service Endpoint Interface {1} to use 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)
Problem The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping, which require that all referenced types must be JAX-RPC serializable.
User response Change the declaration for method {0} in Service Endpoint Interface {1} to use JAX-RPC supported types.
CHKW6010E: Constant field {0} in interface {1} is not permitted. (JAX-RPC 1.0: 5.2)
Problem The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping. They specify that the Service Endpoint Interface class must not include constant (as public final static) declarations.
User response Delete field {0} in Interface {1}.
CHKW6011E: Default public constructor for service implementation class {0} was not found. (JSR109 1.0: 5.3.2.1)
Problem Service implementation class {0} must have a default public constructor in order to be a Stateless Session EJB.
User response Add a public default constructor to class {0}.
CHKW6012E: Class {0} does not implement method {1} of the Service Endpoint Interface {2}. (JSR109 1.0: 5.3.2.1)
Problem The implementation class must implement the methods of the Service Endpoint Interface.
User response Implement all the method signatures in the {0} class for the Service Endpoint Interface {2}.
CHKW6013E: The visibility for method {0} in class {1} must be public. (JSR109 1.0: 5.3.2.1)
Problem The business methods of the class must be public.
User response Change the visibility for method {0} in class {1} to public.
CHKW6014E: Method {0} in class {1} must not be final. (JSR109 1.0: 5.3.2.1)
Problem The business methods of the class must not be final.
User response Remove the final modifier for method {0} in class {1}.
CHKW6015E: Method {0} in class {1} must not be static. (JSR109 1.0: 5.3.2.1)
Problem The business methods of the class must not be static.
User response Remove the static modifier for method {0} in class {1}.
CHKW6016E: The visibility for the service implementation class {0} must be public. (JSR109 1.0: 5.3.2.1)
Problem The service implementation class must be public, must not be final and must not be abstract.
User response Change the visibility for the service implementation class {0} to public.
CHKW6017E: The service implementation class {0} must not be declared final. (JSR109 1.0: 5.3.2.1)
Problem The service implementation class must be public, must not be final and must not be abstract.
User response Remove the final modifier for class {0}.
CHKW6018E: Service implementation class {0} must not be declared abstract. (JSR109 1.0: 5.3.2.1)
Problem The service implementation class must be public, must not be final and must not be abstract.
User response Remove the abstract modifier for class {0}.
CHKW6019E: Service implementation class {0} must not contain a finalize() method. (JSR109 1.0: 5.3.2.1)
Problem A service implementation class must not define the finalize() method.
User response Remove finalize() method from service implementation class {0}.
CHKW6020E: The transaction attributes of method {0} in class {1} must not include Mandatory. (JSR109 1.0: 5.3.2.1.3)
Problem An existing Enterprise Java bean may be used as a Service Implementation Bean if the transaction attributes of the SEI methods do not include Mandatory.
User response Remove Mandatory from the transaction attributes of method {0} in class {1}.
CHKW6021E: Service implementation class {0} was not found in this module. (JSR109 1.0: 5.4)
Problem Service implementation class {0} could not be found this module.
User response Add a service implementation class named {0} in this module.
CHKW6022E: Session EJB {0} must be declared as Stateless in ejb-jar.xml. (JSR109 1.0: 7.1.2)
Problem Service implementation classes using a session bean must be defined in the ejb-jar.xml deployment descriptor file using the session element and cannot be declared with a session-type of Stateful.
User response Define the EJB named {0} in ejb-jar.xml 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)
Problem Service Implementations must be defined in the ejb-jar.xml deployment descriptor file using the session element.
User response Define the class named {0} in ejb-jar.xml 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)
Problem The servlet-link must refer to a servlet in web.xml.
User response Add a servlet named {0} or change the servlet definition in web.xml.
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)
Problem If wsdl-file is not specified in webservicesclient.xml, jaxrpc-mapping-file must not be specified.
User response Remove mapping file {0} 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)
Problem The developer must not package generated stubs.
User response Remove all generated stubs from the module.
CHKW6027E: The value of the ejb-link attribute {0} does not correspond to an Enterprise Bean definition in ejb-jar.xml. (JSR109 1.0: 7.1.5)
Problem The value of the ejb-link element must be the ejb-name of an enterprise bean in the same module.
User response Add a Enterprise Bean named {0} or change the ejb-link definition in ejb-jar.xml.
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)
Problem The component-name element defines a link to a component name such as the ejb-name in the module deployment descriptor. Its value must exist in the module level deployment descriptor.
User response Change the component-name element {0} to refer to a ejb-name element in the ejb-jar.xml.
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)
Problem The value of a port-component-link must be the port-component-name of a port-component in the same module or another module in the same application unit.
User response Add a port component named {0} or change the reference in service-ref {1} of webservicesclient.xml.
CHKW6030E: Implementation class {0} referred to by port components {1} and {2}. (JSR109 1.0: 7.1.2)
Problem A servlet must only be linked to by a single port-component. A session EJB must only be linked to by a single port-component.
User response Change either port component {1} or port component {2} so that they do not both reference implementation class {0}.
CHKW6031E: Multiple servlet mappings detected for servlet named {0} in web.xml. (JSR109 1.0: 7.1.2)
Problem No more than one servlet-mapping may be specified for a servlet that is linked to by a port-component.
User response Remove duplicate servlet mappings for servlet named {0} in web.xml.
CHKW6032E: Servlet mapping for servlet {0} must not contain an asterisk in the url-pattern. (JSR109 1.0: 7.1.2)
Problem The url-pattern of the servlet-mapping must be an exact match pattern.
User response Change servlet mapping for servlet {0} so it does not contain an asterisk.
CHKW6033E: Port {0} is not compatible with Service Endpoint Interface {1}. (JSR109 1.0: 8.3)
Problem When providing a binding for a port-component-ref, the deployer must ensure that the port-component-ref is compatible with the port being bound to.
User response Change port {0} to be compatible with Service Endpoint Interface {1}.
CHKW6034E: wsdl-file {0} cannot use both mapping files {1} and {2}. (JSR109 1.0: 7.2.2)
Problem Only one mapping file can be associated with a wsdl-file.
User response Specify a unique mapping file for the wsdl-file in webservicesclient.xml.
CHKW6035E: Missing jaxrpc-mapping-file in webservicesclient.xml. (JSR109 1.0: 7.2.2)
Problem The developer must specify the jaxrpc-mapping-file if wsdl-file is specified.
User response Add a jaxrpc-mapping-file element in webservicesclient.xml.
CHKW6036E: The serviceRefLink {0} specified in ibm-webservicesclient-bnd.xmi is not the name of a service-ref in webservicesclient.xml.
Problem serviceRefLink must name a service-ref in webservicesclient.xml.
User response Correct the serviceRefLink to name a service-ref in webservicesclient.xml.
CHKW6037E: The deployedWSDLFile path {0} specified in ibm-webservicesclient-bnd.xmi does not reference a WSDL file in this module.
Problem deployedWSDLFile must be the relative path within the module of the WSDL file.
User response Correct the path or add the WSDL file at 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}.
Problem defaultMappings must reference a port and portType in the wsdl-file associated with the service-ref.
User response Correct the attributes of the defaultMappings element to refer to a port and portType in {3}.
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}.
Problem portQnameBindings must reference a port in the wsdl-file associated with the service-ref.
User response Correct the portQnameBindings attributes to refer to a port in {2}.
CHKW6040E: The componentNameLink attribute {0} in ibm-webservicesclient-bnd.xmi references a component-name that does not exist in webservicesclient.xml.
Problem The componentNameLink attribute must reference a component-name in webservicesclient.xml.
User response Modify the componentNameLink attribute to match a component-name in webservicesclient.xml.
CHKW6041E: The scope attribute {0} specified for port-component {1} in ibm-webservices-bnd.xmi is not Request, Session, or Application.
Problem The scope attribute must reference must be either Request, Session, or Application.
User response 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.
Problem The pcNameLink attribute must reference a port-component-name in webservices.xml.
User response Modify the pcNameLink attribute to match a port-component-name in webservices.xml.
CHKW6043E: The wsDescNameLink attribute {0} specified in ibm-webservices-bnd.xmi references a webservice-description-name that does not exist in webservices.xml.
Problem The wsDescNameLink attribute must reference a webservice-description in webservices.xml.
User response Modify the wsDescNameLink attribute to match a webservice-description-name in webservices.xml.
CHKW6045E: The routerModules name {0} in ibm-webservices-bnd.xmi references a module that does not exist in the application.
Problem The routerModules name attribute must reference a module in the current application. It is normally added by the endptEnabler
User response 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)
Problem webservicesclient.xml did not specify a value for the required service-interface element.
User response Add a 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)
Problem webservicesclient.xml did not specify a value for the required service-endpoint-interface element.
User response Add a valid value for the service-endpoint-interface element.
CHKW6048E: Service Endpoint Interface {0} in {1} is not an interface. (JSR109 1.0: 3.10)
Problem The class specified in the service-endpoint-interface element must be an interface.
User response 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)
Problem The servlet-link element of webservices.xml can only appear in Web modules.
User response Change the servlet-link element in webservices.xml 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)
Problem The ejb-link element of webservices.xml can only appear in EJB modules.
User response Change the ejb-link element in webservices.xml 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)
Problem A servlet-link element must appear in webservices.xml in Web modules.
User response Add a servlet-link element to webservices.xml.
CHKW6052E: Required ejb-link element was not found for port component {0} in webservices.xml. (JSR109 1.0: 5.3.2.1.3)
Problem A ejb-link element must appear in webservices.xml in EJB modules.
User response Add an ejb-link element to webservices.xml.
CHKW6053E: Parse error in {0}: {1}: {2}. (JSR109 1.0: 7.1, 7.2)
Problem A SAXParseException occurred reading descriptor {0}.
User response Correct the problem reported in {0}.
CHKW6054E: Error in {0}: {1}: {2}.
Problem A exception occurred reading descriptor {0}.
User response Correct the problem reported in {0}.
CHKW6055E: Required service-impl-bean element was not found for port component {0} in webservices.xml. (JSR109 1.0: 5.3.2.1.3)
Problem A service-impl-bean element must appear each port component in webservices.xml.
User response Add a service-impl-bean element to webservices.xml.
CHKW6056E: Required webservice-description-name attribute was not found in webservices.xml. (JSR109 1.0: 7.1.5)
Problem A webservice-description-name attribute must appear for each webservice-description in webservices.xml.
User response Add a webservice-description-name attribute to each webservice-description in webservices.xml.
CHKW6057E: Required webservice-description element was not found in webservices.xml. (JSR109 1.0: 7.1.5)
Problem A webservice-description element must appear in webservices.xml.
User response Add a webservice-description element to webservices.xml.
CHKW6058E: Required wsdl-file element was not found in webservice-description {0} in webservices.xml. (JSR109 1.0: 7.1.5)
Problem A wsdl-file element must appear in each webservice-description webservices.xml.
User response Add a wsdl-file element to each webservice-description element to webservices.xml.
CHKW6059E: Required jaxrpc-mapping-file element was not found in webservice-description {0} in webservices.xml. (JSR109 1.0: 7.1.5)
Problem A jaxrpc-mapping-file element must appear in each webservice-description in webservices.xml.
User response Add a jaxrpc-mapping-file element to each webservice-description element in webservices.xml.
CHKW6060E: Required pcNameLink attribute was not found in ibm-webservices-bnd.xmi.
Problem A pcNameLink attribute must appear in each pcBindings element in ibm-webservices-bnd.xmi.
User response Add a pcNameLink attribute to each pcBindings element in ibm-webservices-bnd.xmi.
CHKW6061E: Required port-component-name element was not found in webservice-description {0} in webservices.xml.(JSR109 1.0: 7.1.5)
Problem A port-component-name element must appear in each webservice-description element in webservices.xml.
User response Add a port-component-name element to each webservice-description element in webservices.xml.
CHKW6062E: Required wsDescNameLink attribute was not found in ibm-webservices-bnd.xmi.
Problem A wsDescNameLink attribute must appear in each wsdescBindings element in ibm-webservices-bnd.xmi.
User response Add a wsDescNameLink attribute to each wsdescBindings element in ibm-webservices.xmi.
CHKW6063E: Required component-name element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Problem The component-name element must appear for each component-scoped-ref in webservicesclient.xml.
User response Add a component-name element to refer to a ejb-name element in the ejb-jar.xml.
CHKW6064E: Required service-ref-name element was not found in service-ref in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Problem The sevice-ref-name element must appear for each service-ref in webservicesclient.xml.
User response Add a service-ref-name element to each service-ref in webservicesclient.xml.
CHKW6065E: Required service-ref element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Problem The sevice-ref element must appear webservicesclient.xml.
User response Add a service-ref element to webservicesclient.xml.
CHKW6066E: Required componentNameLink attribute was not found in ibm-webservicesclient-bnd.xmi.
Problem A componentNameLink attribute must appear in each componentScopedRefs element in ibm-webservicesclient-bnd.xmi.
User response Add a componentNameLink attribute whose value is a component-name in webservices.xml.
CHKW6067E: Error in {0}: {1}: {2}.
Problem A SAXParseException occurred reading binding file {0}.
User response Correct the problem reported in {0}.
CHKW6068E: Required serviceRefLink attribute was not found in serviceRefs element ibm-webservicesclient-bnd.xmi.
Problem A serviceRefLink attribute must appear in each serviceRefs element in ibm-webservicesclient-bnd.xmi.
User response Add a serviceRefLink attribute whose value is a service-ref-name in webservices.xml.
CHKW6069E: Required service-endpoint-interface element was not found in port-component {0} in webservices.xml. (JSR109 1.0: 7.1.5)
Problem The service-endpoint-interface element must appear in each port-component in webservices.xml.
User response Add a service-endpoint-interface element to port-component {0} to webservices.xml.
CHKW6070E: Required component-scoped-refs element or service-ref element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Problem Either a component-scoped-refs or service-ref element must appear in webservicesclient.xml.
User response Add a service-ref element or component-scoped-refs element to webservicesclient.xml.
CHKW6071E: Required port-component element was not found in webservice-description {0} in webservices.xml.(JSR109 1.0: 7.1.5)
Problem A port-component element must appear in each webservice-description element in webservices.xml.
User response Add a port-component element to each webservice-description element in webservices.xml.
CHKW6072I: Type {0} in method {1} in JAX-RPC interface {2} is a non-standard extension to JAX-RPC.
Problem The indicated type is supported by this implementation, but is not part of the JAX-RPC specification.
User response Review usage of the type to ensure 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.
Problem The indicated type is supported by this implementation, but is not part of the JAX-RPC specification.
User response Review usage of the type to ensure 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)
Problem Types implementing java.rmi.Remote are prohibited by the JAX-RPC specification.
User response Modify the type to not implement java.rmi.Remote.
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)
Problem Types implementing java.rmi.Remote are prohibited by the JAX-RPC specification.
User response Modify the type to not implement java.rmi.Remote.
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)
Problem Types implementing javax.xml.rpc.holders.Holder must have a public field named value.
User response Ensure that type {0} 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)
Problem JAX-RPC value types must have a public default constructor.
User response Add a public default constructor to class {0}.
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)
Problem JAX-RPC value types must have a public default constructor.
User response Add a public default constructor to class {3}.
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)
Problem The component-scoped-refs element is required in webservicesclient.xml in EJB modules to specify which EJB is being configured as a Web services client.
User response Add a component-scoped-refs element to webservicesclient.xml with a component-name element specifying the ejb-name of the client EJB.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.websphere.validation.jsr109.resources.jsr109NLS.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)