Problem | None. |
User response | None. |
Problem | An internal error occurred. |
User response | None. |
Problem | Starting JSR109 validation of module {0}. |
User response | Information only, no action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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}. |
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}. |
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}. |
Problem | The business methods of the class must be public. |
User response | Change the visibility for method {0} in class {1} to public. |
Problem | The business methods of the class must not be final. |
User response | Remove the final modifier for method {0} in class {1}. |
Problem | The business methods of the class must not be static. |
User response | Remove the static modifier for method {0} in class {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. |
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}. |
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}. |
Problem | A service implementation class must not define the finalize() method. |
User response | Remove finalize() method from service implementation class {0}. |
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}. |
Problem | Service implementation class {0} could not be found this module. |
User response | Add a service implementation class named {0} in this module. |
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. |
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. |
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. |
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. |
Problem | The developer must not package generated stubs. |
User response | Remove all generated stubs from the module. |
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. |
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. |
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. |
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}. |
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. |
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. |
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}. |
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. |
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. |
Problem | serviceRefLink must name a service-ref in webservicesclient.xml. |
User response | Correct the serviceRefLink to name a service-ref in webservicesclient.xml. |
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. |
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}. |
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}. |
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. |
Problem | The scope attribute must reference must be either Request, Session, or Application. |
User response | Correct the scope attribute. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Problem | A servlet-link element must appear in webservices.xml in Web modules. |
User response | Add a servlet-link element to webservices.xml. |
Problem | A ejb-link element must appear in webservices.xml in EJB modules. |
User response | Add an ejb-link element to webservices.xml. |
Problem | A SAXParseException occurred reading descriptor {0}. |
User response | Correct the problem reported in {0}. |
Problem | A exception occurred reading descriptor {0}. |
User response | Correct the problem reported in {0}. |
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. |
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. |
Problem | A webservice-description element must appear in webservices.xml. |
User response | Add a webservice-description element to webservices.xml. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Problem | The sevice-ref element must appear webservicesclient.xml. |
User response | Add a service-ref element to webservicesclient.xml. |
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. |
Problem | A SAXParseException occurred reading binding file {0}. |
User response | Correct the problem reported in {0}. |
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. |
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. |
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. |
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. |
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. |
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. |
Problem | Types implementing java.rmi.Remote are prohibited by the JAX-RPC specification. |
User response | Modify the type to not implement java.rmi.Remote. |
Problem | Types implementing java.rmi.Remote are prohibited by the JAX-RPC specification. |
User response | Modify the type to not implement java.rmi.Remote. |
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. |
Problem | JAX-RPC value types must have a public default constructor. |
User response | Add a public default constructor to class {0}. |
Problem | JAX-RPC value types must have a public default constructor. |
User response | Add a public default constructor to class {3}. |
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. |