- CWLAV0001E: The interface map component has multiple interfaces.
- Explanation: Because an interface map mediates between one interface and one target reference, only one of each is required.
- User Action: In the assembly diagram editor, remove all except one interface from this interface map component.
- CWLAV0002E: The interface map component has multiple references.
- Explanation: Because an interface map mediates between one interface and one target reference, only one of each is required.
- User Action: In the assembly diagram editor, remove all except one references from this interface map component.
- CWLAV0003E: The interface map component refers to multiple interfaces.
- Explanation: An interface map component must not have more than one interface in its reference.
- User Action: In the assembly diagram editor, remove all except one of the referenced interfaces from this interface map component.
- CWLAV0004E: The {0} interface map (.ifm) file does not exist.
- Explanation:
- User Action: Choose an existing interface map file as the component implementation or generate a new implementation.
- CWLAV0005E: Interface qualifiers cannot be verified.
- Explanation: The outgoing (target) interface cannot be resolved because the target component, the interfaces for the target component (which are defined in a .wsdl file), or both cannot be found.
- User Action: Put the target component in the same module or in a library that the module depends on.
- CWLAV0006E: Reference qualifiers cannot be verified.
- Explanation: The incoming (source) interface cannot be resolved because the source component, the interfaces for the source component (which are defined in a .wsdl file), or both cannot be found.
- User Action: Put the source interface component in the same module or in a library that the module depends on.
- CWLAV0007E: The value for the {0} PreferredInteractionStyle attribute does not match the {1} value for the same attribute in the {2} component.
- Explanation: The value of the PreferredInteractionStyle attribute for the interface map component must be the same as the value for that attribute in the source or target component.
- User Action: Set the PreferredInteractionStyle attribute to "sync", "async", or "any". Set the same value for the attribute in the mediation component and the source or target component.
- CWLAV0008E: The {0} Reliability qualifier is not compatible with {1} in the {2} component.
- Explanation: The Reliability qualifier on the source or target component must match the value of the qualifier on the mediation component.
- User Action: In the assembly diagram editor, change the value of the Reliability qualifier on either component so that the values on both components match.
- CWLAV0009E: The transaction qualifier for the interface map component is not set to "global".
- Explanation: The transaction qualifier must be set to "global" so that the work completed under interface mediation can be rolled back in case of failures.
- User Action: In the assembly diagram editor, select the interface map component. In the Properties view, set the transaction qualifier on the mediation component to "global".
- CWLAV0010E: The deliverAsyncAt qualifier is not set to commit for the interface map component.
- Explanation: To ensure that all transactional work performed by the interface map component is aligned with the global transaction, the deliverAsyncAt qualifier for the interface map component must be set to commit.
- User Action: In the assembly editor, select the interface map component. In the Properties view, set the deliverAsyncAt qualifier to "commit".
- CWLAV0011E: The {0} operation mediates to itself.
- Explanation: An interface operation must not mediate to itself. Interface mapping must occur only between operations from different interfaces.
- User Action: In the interface map editor, select an operation from the other interface to create an operation mapping.
- CWLAV0012E: The source operation is bound more than once.
- Explanation: The specified source operation does not exist in the source interface.
- User Action: In the interface map editor, remove the operation binding for the source operation that does not exist in the source interface. Alternatively, in the interface editor, add the operation to the source interface.
- CWLAV0014E: The {0} target operation was not found.
- Explanation: The specified target operation does not exist in the target interface.
- User Action: Remove the operation mappings for the target operation that does not exist in the target interface or reconnect the mappings to existing operations.
- CWLAV0015E: The {0} target operation returns output or a fault when the multiplicity qualifier on the interface map components reference is 0..n.
- Explanation: When the multiplicity qualifier on the interface map components reference is 0..n, the invocation will be one-way and all of the referenced targets will be invoked. Therefore, the target should not have outputs or faults.
- User Action: In the assembly diagram editor, select the interface map component and change the multiplicity qualifier on the interface map components reference to 1..1.
- CWLAV0016E: The interface map or interface map component does not have a source interface.
- Explanation: No component uses this interface mapping as its implementation.
- User Action: In the assembly editor, create a component that uses the specified interface mapping file for its implementation.
- CWLAV0018E: The {0} parameter does not exist in the {1} operation.
- Explanation: If a parameter is specified in the interface mapping file, it must exist in the source or target interface.
- User Action: Using the interface map editor, open the interface map. The specified parameter will be grayed out, meaning that it has been removed from the operation. You will need to either add it back to the interface operation or modify the parameter mapping that it connects to a different parameter.
- CWLAV0019E: The {0} parameter in {1} fault type does not exist in the {2} operation.
- Explanation: The fault parameter specified in the interface mapping file must exist in the source or target interface.
- User Action: Using the interface map editor, open the interface map. The specified parameter will be grayed out, meaning that it has been removed from the operation. You will need to either add it back to the interface operation or modify the parameter mapping that it connects to a different parameter.
- CWLAV0020E: The {0} source output parameter is bound more than once for a normal return.
- Explanation: The source output parameter must be bound only once. If it is bound more than once, the output value is indeterminate.
- User Action: Open the interface map in the interface map editor and remove the unnecessary connections of this output parameter.
- CWLAV0021E: The {0} source fault parameter is bound more than once for a fault return.
- Explanation: The source fault parameter must be bound only once. If it is bound more than once, the source fault value is indeterminate in the return path.
- User Action: Open the interface map in the interface map editor and remove the unnecessary connections of this fault parameter.
- CWLAV0022E: The {0} target input parameter is bound more than once.
- Explanation: The target input parameter must be bound only once. If it is bound more than once, the target input value is indeterminate in the source to target mediation path.
- User Action: Open the interface map in the interface map editor and remove the unnecessary connections of this input parameter.
- CWLAV0023E: The {0} target fault type is bound more than once.
- Explanation: The target fault parameter must be bound only once. If it is bound to more than one source fault, the source fault value is indeterminate in the return path, which is not allowed.
- User Action: Open the interface map in the interface map editor and remove the unnecessary connections of this fault parameter.
- CWLAV0024E: An input of type {0} does not exist in map {1}.
- Explanation: The parameter that is connected to data map input must be of the same type as the input.
- User Action: Open the interface map in the interface map editor and connect the map input to the correct parameter. Alternatively, in the Properties view, select a different data map.
- CWLAV0025E: The {0} map input is bound more than once.
- Explanation: The data map input can be bound to only one interface parameter during parameter mapping. If the data map input is bound more than once, the data map value is indeterminate at run time because it will be populated with values from various incoming parameters.
- User Action: Open the interface map in the interface map editor and remove all except one connection from this parameter mapping.
- CWLAV0026E: Input, output, and fault parameter types are combined in one parameter mapping.
- Explanation: For each parameter mapping, the source parameter must be of the same type as target parameter. Therefore, both parameters should be of type input, output, or fault.
- User Action: Open the interface map in the interface map editor and make the connections of this parameter mapping the same type.
- CWLAV0027E: The parameter mapping was created incorrectly.
- Explanation: The source of this parameter mapping should be an operation parameter of type input. For each parameter mapping, the source parameter must be of the same type as the target parameter. Therefore, both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, open the interface map and reconnect the source end of the parameter mapping to matching types.
- CWLAV0028E: The parameter mapping was created incorrectly.
- Explanation: The source of this parameter mapping should be a target operation parameter of type output or fault. For each parameter mapping, the source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, open the interface map and reconnect the source end of the parameter mapping to matching types.
- CWLAV0029E: The parameter mapping was created incorrectly.
- Explanation: The target of this mapping should be a target operation parameter of type input. For each parameter mapping, the source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, open the interface map and reconnect the target end of the parameter mapping to matching types.
- CWLAV0030E: The paramType value is not "input".
- Explanation: When the location attribute in the parameter binding is "intermediate", the parameter mapping uses a data map; so the paramType value must be "input". This situation would have happened only if the interface map file has been edited in the text editor.
- User Action: Open the interface map file in a text editor and set the paramType value to "input".
- CWLAV0031E: The parameter mapping was created incorrectly.
- Explanation: The target of this mapping should be a source operation parameter of type output or fault. For each parameter mapping, the source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, open the interface map and reconnect the target end of the parameter mapping to matching types.
- CWLAV0032E: The parameter is bound from and bound to the same location.
- Explanation: Binding between the same locations is indeterminate.
- User Action: Open the file using the interface map editor and use an interface map to bind the parameter between different source and target locations.
- CWLAV0033E: The types of target parameters bound in the same parameter mapping are different.
- Explanation: Because the parameter binding specifies mapping to a single destination, the value of the "to" attribute must be the same on a single parameter binding.
- User Action: Open the interface mapping file and delete and then recreate the parameter mapping.
- CWLAV0034E: The paramType value is not "output".
- Explanation: Because a parameter binding operation from an intermediate location is considered the output from the data map, the paramType value must be "output".
- User Action: In a parameter binding operation from an intermediate location, change the paramType value to "output".
- CWLAV0035E: The data map definition for {0} cannot load.
- Explanation: Either the data map is missing in the module or, if it is located in a library, there is no dependency between the module and library.
- User Action: If the data map does not exist, create it from Properties view of the interface map editor. If the data map exists in a library, in the dependency editor, create a dependency between the module and this library. If the data map has been moved to a different module, refactor the data map to move it back to the original location within the scope of the module containing the interface map.
- CWLAV0036E: The parameter mapping is incorrect.
- Explanation: For map parameter mapping, fault-to-output or output-to-fault mapping is not supported. For each parameter mapping, the source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, reconnect the target or source end of the map parameter mapping to make it a mapping between two outputs or two faults.
- CWLAV0037E: The map parameter mapping is not connected to operation parameters.
- Explanation: The connections between a map parameter mapping and parameters enables the passing of parameters to data map inputs as well as the passing of data map outputs to parameters.
- User Action: In the interface map editor, connect the ends of the map parameter mapping.
- CWLAV0038E: The connections between the source operation parameter and the map and between the map and target operation parameter are missing.
- Explanation: For a parameter mapping of type map between a parameter of the source operation and a parameter of the target operation, the source operation parameter should connect to a data map input and a data map output should connect to the target operation parameter.
- User Action: In the interface map editor, reconnect the ends of the map parameter mapping.
- CWLAV0039E: The connections between target operation parameter and the map and between the map and source operation parameter are missing.
- Explanation: For parameter mapping of type "map" between a parameter of the target operation and a parameter of the source operation, the target operation parameter should connect to a data map input and a data map output should connect to the source operation parameter.
- User Action: In the interface map editor, reconnect ends of the map parameter mapping.
- CWLAV0040E: The fault parameter mapping is incorrect.
- Explanation: For a fault parameter mapping that uses a data map, the attributes srcFaultType and tgtFaultType must be specified to correlate with the correct fault in multiple-fault scenarios.
- User Action: Specify the srcFaultType and tgtFaultType attributes in the multiple-fault scenarios.
- CWLAV0041E: The source location in a move parameter mapping cannot be intermediate.
- Explanation: Each parameter mapping can have one of the following sources: input parameter of the source operation, output parameter of the target operation, or fault parameter of the target operation.
- User Action: In the interface map editor, reconnect the source end of the parameter mapping.
- CWLAV0042E: The target location in a move parameter mapping cannot be intermediate.
- Explanation: Parameter mappings always start from one end with the other end(destination) being either input parameter of the target operation, output parameter of the source operation, or fault parameter of the source operation.
- User Action: In the interface map editor, reconnect the target end of the parameter mapping.
- CWLAV0043E: The parameter type of the source does not match the parameter type of the target.
- Explanation: For each parameter mapping, the source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, reconnect the target or source end of the parameter mapping.
- CWLAV0044E: The attributes srcFaultType and tgtFaultType are not specified.
- Explanation: For fault parameter mappings of the type "move", the srcFaultType and tgtFaultType attributes are needed to correlate with the correct fault in a multiple-fault scenario.
- User Action: Specify the srcFaultType and tgtFaultType attributes for the multiple-fault scenario.
- CWLAV0045E: The Java parameter mapping has an incorrect source.
- Explanation: Each parameter mapping can have one of the following sources: input parameter of the source operation, output parameter of the target operation, or fault parameter of the target operation.
- User Action: In the interface map editor, reconnect the source end of the parameter mapping.
- CWLAV0046E: The parameter mapping has destinations that are not valid.
- Explanation: Parameter mappings always start from one end with the other end (destination) being either the input parameter of the target operation, the output parameter of the source operation, or the fault parameter of the source operation.
- User Action: In the interface map editor, reconnect the target end of the parameter mapping.
- CWLAV0047E: The attributes srcFaultType and tgtFaultType are not specified.
- Explanation: For fault parameter mappings of the type "Java", the attributes srcFaultType and tgtFaultType are needed to correlate with the correct fault in a multiple-fault scenario.
- User Action: Specify the srcFaultType and tgtFaultType attributes for the multiple-fault scenario.
- CWLAV0048E: For parameter mappings of the type "Java", the parameter type of the source does not match the parameter type of the target.
- Explanation: For each parameter mapping, the source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface map editor, reconnect the target or source end of the parameter mapping.
- CWLAV0049E: The constant value of the assignment is missing.
- Explanation: The constant value in an assign parameter mapping specifies a value that is assigned to the destination.
- User Action: In the interface map editor, in the Properties view, specify the constant value for the assign parameter mapping.
- CWLAV0050E: For parameter mappings of the type "extract", a fault-to-output mapping is not supported.
- Explanation: The source parameter must be of the same type as target parameter, which means that both parameters should be of type input, output, or fault.
- User Action: In the interface editor, reconnect the target or source end of the extract parameter mapping to make it a mapping between two outputs or two faults.
- CWLAV0051E: An extract parameter mapping cannot have intermediate as its target location. An extract parameter mapping can have one of the following targets: input parameter of the target operation, output parameter of the source operation, fault parameter of the source operation.
- Explanation: Parameter mappings always start from one end with the other end (destination) being either input parameter of the target operation, output parameter of the source operation, or fault parameter of the source operation.
- User Action: In the interface map editor, reconnect the target end of the parameter mapping.
- CWLAV0052E: The attributes srcFaultType and tgtFaultType are missing.
- Explanation: For fault parameter mappings of the type "extract", the srcFaultType and tgtFaultType attributes are needed to correlate with the correct fault in a multiple-fault scenario.
- User Action: Specify the srcFaultType and tgtFaultType attributes in the multiple-fault scenario.
- CWLAV0053E: The {0} input parameter in the {1} target operation is not bound.
- Explanation: An input to a target must be bound in an interface mapping.
- User Action: In the interface map editor, create a parameter mapping between the input parameter of the target operation and an input parameter of the source operation.
- CWLAV0054E: The {0} fault type in the {1} target operation is not bound.
- Explanation: All faults from the target must be bound.
- User Action: In the interface map editor, create a parameter mapping between the fault parameter of the target operation and a fault parameter of the source operation.
- CWLAV0055E: The {0} output parameter in the {1} source operation is not bound.
- Explanation: Because the source output must receive the response from the target, the source output must be bound.
- User Action: In the interface map editor, create a parameter mapping between the output parameter of the target operation and an output parameter of the source operation.
- CWLAV0056E: The {0} fault parameter in the {1} source operation is not bound.
- Explanation: Because the source fault must receive the response from the target fault, the source fault must be bound.
- User Action: In the interface map editor, create a parameter mapping that will connect the source fault with the target fault.
- CWLAV0057E: The {0} fault parameter of the {1} fault type in the {2} source operation is not bound.
- Explanation: All source faults must be bound.
- User Action: In the interface map editor, create a parameter mapping between the fault parameter of the source operation and a fault parameter of the target operation.
- CWLAV0058E: The response map output is not a subset of the request map input.
- Explanation: For identity relationships to correlate effectively, the response map output must a subset of the request map input.
- User Action: In the identity relationship, make the response map output a subset of the request map input.
- CWLAV0059E: The response map input is not a subset of the request map output.
- Explanation: For identity relationships to correlate effectively the response map input must be a subset of the request map output.
- User Action: In the identity relationship, make the response map input a subset of the request map output.
- CWLAV0060E: The {0} parameter type does not match {1}.
- Explanation: For a move parameter mapping, the source and target parameters must be the same type.
- User Action: In the interface map editor, change the type of the parameter mapping to one that is different than the move parameter mapping, or reconnect the move parameter mapping to two different source and target parameters that are of the same type.
- CWLAV0061E: The {0} parameter type is bound to data map input of type {1}.
- Explanation: For a map parameter mapping, the parameter type cannot be bound to data map input of the specified type. The data map inputs and outputs must be bound to interface parameters of the same type.
- User Action: In the interface map editor, switch the connections between the interface parameters and the map parameter mapping.
- CWLAV0062E: The {0} value in an XPath is of different type than type {1} of the extract mapping target parameter.
- Explanation: For an extract parameter mapping, the value extracted from the XPath must be the same type as the target parameter.
- User Action: In the interface map editor, select the extract parameter mapping. In the Properties view, make the the XPath point to an attribute that is of the same type as the target parameter.
- CWLAV0063E: The {0} Java class in the Java parameter mapping does not extend the JavaMediation or JavaMediationDataObject class in the com.ibm.wbiserverspi.mediation package.
- Explanation: For a Java parameter mapping, the class must extend the JavaMediation or JavaMediationDataObject class in the com.ibm.wbiserverspi.mediation package.
- User Action: In the interface map editor, select the Java parameter mapping. In the Properties view, select a Java class that extends the JavaMediation or JavaMediationDataObject class in the com.ibm.wbiserverspi.mediation package.
- CWLAV0064E: The {0} class name in the Java parameter mapping was not found.
- Explanation: For a Java parameter mapping, the specified Java class is missing in the workspace or is not available from the location of the interface map.
- User Action: If the class does not exist, in the interface map editor select the Java parameter mapping and, in the Properties view, create the class. If the class exists, in the Properties view, correct the class path.
- CWLAV0065E: The interface map does not define an operation mapping.
- Explanation: Interface maps must have at least one source and target operation pair bound as an operation mapping.
- User Action: In the interface map editor, create at least one operation mapping by dragging one of the source operations to a target operation.
- CWLAV0066E: The Java class for the Java parameter mapping is not specified.
- Explanation:
- User Action: In the interface map editor, select the Java parameter mapping and, in the Properties view, select a Java class that performs the actual parameter mapping.
- CWLAV0067E: The {0} input of the {1} data map is not connected in the {2} interface map.
- Explanation: For a data map, all incoming inputs must be bound to at least one parameter in an interface map parameter mapping. If not all inputs are bound, the map might fail at run time.
- User Action: In the interface map editor, connect the specified map input to an interface parameter.
- CWLAV0068E: The {0} XPath expression cannot be validated because of a Java interface.
- Explanation: XPath expressions cannot validate Java interfaces. The XPath expression must apply to the business object at run time. If it does not, the interface map might fail at run time.
- User Action: No user action required. You might want to use Web Services Description Language (WSDL) interfaces.
- CWLAV0069E: The {0} XPath expression cannot be validated because of a Java reference.
- Explanation: XPath expressions validate Java references The XPath expression must apply to the business object at run time. If it does not, the interface map might fail at run time.
- User Action: No user action required. You might want to use Web Services Description Language (WSDL) references instead of Java references.
- CWLAV0070E: The {0} type is not supported for assigning a constant value to the {1} target parameter.
- Explanation: Only String, Long, Float, Int, Double, Boolean, Short, Byte or BigInteger are acceptable types for assigning a constant value to the target parameter.
- User Action: In the interface map editor, select the assigned parameter mapping with the error marker and, in the Properties view, enter a value that is one of the supported types.
- CWLAV0071E: The {1} interface on the {0} interface map component does not match the {2} interface of the interface map implementation.
- Explanation: An interface map component and its implementation must have the same interface.
- User Action: To synchronize the component and the interface map interfaces, in the assembly diagram editor, select the interface map component, delete its interface, and add an interface that is the same as the one that the corresponding implementation file has.
- CWLAV0072E: The {1} reference on the {0} interface map component does not match with the {2} reference of the interface map implementation.
- Explanation: An interface map component and its implementation must have the same reference.
- User Action: To synchronize the component and the interface map reference, in the assembly diagram editor, select the interface map component, delete its reference, and add a reference that is the same as the one that the corresponding implementation file has.
- CWLAV0073E: There are more than one parameter mappings with the target fault type {0} and the source fault type {1}
- Explanation: Having more than one fault parameter map with the same target fault type and the source fault type, makes the mapping indeterminate at runtime, since only one of the fault mapping can be executed.
- User Action: Open the Interface Map editor and delete the multiple parameter mapping between faults when the source and target types are the same . This is done to ensure that there is only one fault parameter mapping with the same source and target types.
- CWLAV0074E: The interface map or interface map component does not have a target reference.
- Explanation: The interface map component, the interface map .ifm file, or both do not define the target references.
- User Action: In the interface map editor, add the target interface to the implementation.
- CWLAV0075E: The {0} parameter type resulting from the XPath Expression in the Extract does not match the type {1} to which it is being mapped.
- Explanation: For a Extract parameter mapping, the source parameter resulting from applying the Xpath Expression should be the same as the target parameter.
- User Action: In the interface map editor, edit the xpath expression being applied to the source, so that the resulting type is the same as the target to which it is being mapped.
- CWLAV0076E: The data map is not specified.
- Explanation: No data map is set in the 'Business Object Map' filed from the parameter mapping Properties view.
- User Action: Specify the data map name in the interface map Parameter mappings Properties view. If the data map does not exist, create it from Properties view of the interface map editor. If the data map exists in a library, in the dependency editor, create a dependency between the module and this library. If the data map has been moved to a different module, refactor the data map to move it back to the original location within the scope of the module containing the interface map.
- CWLAV0501E: The directory where the J2W Mapper implementation should be created was not specified.
- Explanation:
- User Action: Specify the directory name where the J2W Mapper implementation is created.
- CWLAV0502E: The directory where the J2W Mapper artifacts should be created was not specified.
- Explanation:
- User Action: Specify the directory name where the WSDL and component files is created.
- CWLAV0503E: The Java class or interface name is missing.
- Explanation: The Java Class or interface name must be specified.
- User Action: Specify the Java Class or Java Interface name.
- CWLAV0504E: The {0} Java Class argument is incorrect.
- Explanation: The Java Class argument must be a valid Java Interface or a Java Class that implements one interface.
- User Action: Specify a Java interface or a Java Class that implements one interface.
- CWLAV0505E: The {0} Java Class argument has overloaded methods.
- Explanation: A Java Class argument cannot have overloaded methods.
- User Action: Specify a Java Class argument that does not have overloaded methods.
- CWLAV0506E: The {0} directory cannot be created.
- Explanation: Most likely, there are incorrect permissions on the directory.
- User Action: Please change the permissions so that the directory can be created.
- CWLAV0507E: More than one portType is defined in the WSDL file.
- Explanation: The WSDL file cannot have more than one Port Type. Most likely, a Java Interface with overloaded method is used to generate the J2W mapper.
- User Action: Specify a Java interface or a Java Class that implements one interface.
- CWLAV0508E: The method cannot be generated because the operation name is null.
- Explanation: Most likely, the J2W Mapper did not generate the WSDL file correctly.
- User Action: Please allow write permission on the directory where the WSDL will be generated.
- CWLAV0509E: The method cannot be generated because the WSDL definition is issing.
- Explanation: Most likely, the J2W Mapper did not generate the WSDL file correctly.
- User Action: Please allow write permission on the directory where the WSDL will be generated.
- CWLAV0510E: The {0} operation cannot be found.
- Explanation: Most likely, the J2W Mapper did not generate the WSDL file correctly.
- User Action: Please allow write permission on the directory where the WSDL will be generated.
- CWLAV0511E: The input element qualified Name (QName) cannot be read from WSDL
- Explanation: The Operation in WSDL does not have an input message.
- User Action: In the WSDL file, specify a valid input element qualified name (QName) for the Operation.
- CWLAV0512E: The output element qualified Name (QName) cannot be read from WSDL
- Explanation: The Operation in WSDL does not have an output message.
- User Action: In the WSDL file, specify a valid output element qualified name (QName) for the Operation.
- CWLAV0513E: The operation in the WSDL file declares {0} arguments and the Java Interface declares {1} arguments for the method.
- Explanation: The number of arguments for the operation must match the number of arguments for the method in the Java Interface.
- User Action: In the WSDL file, specify arguments for the operation that matches that of the Java Interface.
- CWLAV0514E: The {0} return type cannot be converted to the {1} return type.
- Explanation: The Operation return type cannot be converted to the matching Java return type.
- User Action: Make the return types of the Java method and the operation in the WSDL file compatible by editing the WSDL file.
- CWLAV0517E: The WSDL {0} message type cannot be converted to the {1} Java type.
- Explanation: The message types must be compatible.
- User Action: Specify a compatible Java Type in the Java Interface for which the J2W Mapper is generated.
- CWLAV0518E: The operation has multiple return values for the qualified name (QName) {0}.
- Explanation: An operation must not have multiple return types specified.
- User Action: In the WSDL file, specify a single return type for the operation.
- CWLAV0519E: The input message for the {0} operation is not defined.
- Explanation: The operation must have an input message.
- User Action: Specify a valid input message for the operation in the WSDL.
- CWLAV0520E: The output message for the {0} operation is not defined.
- Explanation: The operation must have an output message.
- User Action: Specify a valid output message for the operation in the WSDL.
- CWLAV0521E: The {0} input message for the {1} operation has no parts.
- Explanation: The input message for the operation must have parts.
- User Action: Specify valid parts for the input message in the WSDL.
- CWLAV0522E: The {1} message for the {2} operation has multiple parts.
- Explanation: The specified message must have only one part.
- User Action: In the WSDL file, remove all except one part from the message.
- CWLAV0523E: The {0} message for the {1} operation does not have a part.
- Explanation: The message must have one part defined.
- User Action: In the WSDL file, add one part to the message.
- CWLAV0524E: The {0} method cannot be found in the {1} Java class.
- Explanation: The Java class does not contain this method.
- User Action: Check that the Java Class has the method in it.
- CWLAV0525E: The {0} method cannot be found in the {1} Java class.
- Explanation: The Java class does not contain this method.
- User Action: Specify a Java Class argument that does not have overloaded methods.
- CWLAV0526E: The output element qualified Name (QName) cannot be read from WSDL
- Explanation: The Operation in WSDL does not have an output message.
- User Action: In the WSDL file, specify a valid input element qualified name (QName) for the Operation.