Explanation | The service-ref element must contain a service-interface element. |
Action | Add the service-interface element and redeploy the application. |
Explanation | The service-interface element specifies a class that cannot be found or loaded. |
Action | Ensure the class is in the application class path. |
Explanation | The service-interface element must specify a subclass of the javax.xml.ws.Service class. |
Action | Specify a subclass of the javax.xml.ws.Service class in the service-interface element. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | If @WebServiceRef or @Resource annotation is found at the class-level, the type attribute must be identified. It may be specified within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the missing type attribute. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of the javax.xml.ws.Service class. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the class member type is Object, the type attribute must be specified and cannot be Object. You can specify the class member type within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify a type attribute other than Object. |
Explanation | The type attribute must be compatible with the class member type. You can specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify an appropriate type attribute that is compatible with the class member type. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of javax.xml.ws.Service. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the lookup attribute of the @WebServiceRef annotation is specified, then no other attributes are allowed. |
Action | Remove the lookup attribute or the other attributes. |
Explanation | If a @WebServiceRef annotation is found at the class level, the name and type attributes must be specified. |
Action | Specify the missing name or type attribute. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | For JAX-WS service references, if the @WebServiceRef annotation is specified on a method, the method name must follow the standard JavaBeans convention, such as setHelloWorld or getHelloWorld. |
Action | Ensure the method name follows the standard JavaBeans conventions. |
Explanation | If the class member type is Object, the type attribute of the @WebServiceRef annotation must be specified and cannot be Object. |
Action | Specify a type attribute other than Object. |
Explanation | The type attribute must be compatible with the class member type. |
Action | Ensure that the type attribute is compatible with the class member type. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | The handler chain definition file cannot be found from the file attribute of handlerChain annotation. |
Action | Specify the path of an existing handler chain definition file. The path can be an absolute file path or relative to the class annotated with the handlerChain annotation. |
Explanation | The naming space of the root element is not equal to "http://java.sun.com/xml/ns/javaee" or the local name of the root element is not equal to "handler-chain". |
Action | Modify the naming space of the root element to be either "http://java.sun.com/xml/ns/javaee" or the local name of the root element to "handler-chain", then try again. |
Explanation | An unexpected exception was encountered when parsing the handler chain file. |
Action | Verify that the format of the handler file is correct and check the ffdc log in the appropriate logs/ffdc directory of the server for more details. |
Explanation | A file property is required in the handlerChain annotation. |
Action | Specify the appropriate file name in the handlerChain annotation. |
Explanation | An IOException occurred when loading the catalog file. |
Action | Ensure that the JAX-WS catalog file exists and its syntax conforms to the XML Catalog specification. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | An IOException occurred when writing the full WSDL definition to the stream. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | Cannot create or initialize the handler. |
Action | Make sure that the handler class is in the class path of the application or the handler class provides an empty constructor. |
Explanation | The return type of the preDestory method must be void and the resources that are used by the the handler must be released. |
Action | Make sure that the return type of the preDestory method is void and all the resources that are used by the handler class are released. Check the log file in server_name/logs/ffdc directory for more details. |
Explanation | The service class was not found in the class path of the application. |
Action | Ensure that the service class is in the class path of the application. |
Explanation | It is required to use relative URL for WSDL location, which will not force the JAX-WS implementation to retrieve remote locations. |
Action | Update the WSDL location with relative URL via annotations or deployment plans. |
Explanation | The WSDL file specified for the implementation class cannot be found. |
Action | Specify an existing WSDL file to the web service. |
Explanation | If the binding type is specified using BindingType annotation or from deployment descriptor, its value must match the one in the WSDL document. |
Action | Update the value of the binding type to match the one in the WSDL document. |