This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 131124

Summary: Add validation rule to check message type compatibility for redelivery configuration
Product: soa Reporter: Jun Qian <jqian>
Component: Composite ApplicationAssignee: Venkat Chellasamy <vchellasamy>
Status: NEW ---    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description Jun Qian 2008-03-26 03:21:32 UTC 
Philip Varghese wrote:
> Senthil,
> In your project the message type of the operation to the file redirect-endpoint and the actual endpoint are not the same.
>
> 1. Message QName for the actual endpoint(httpbc) is: {http://j2ee.netbeans.org/wsdl/DummyWsdl}DummyWsdlOperationRequest.
> 2. Message QName for the redirect endpoint(filebc) is :
{http://j2ee.netbeans.org/wsdl/OutputToFile}DummyWsdlOperationRequest.
>
> when the ME to the actual endpoint(http-bc) fails the same message (1) is redirected to the
redirect-endpoint(file-bc), where it fails with the error
>
> The WSDL definition provided does not contain a definition for the normalized message
{http://j2ee.netbeans.org/wsdl/DummyWsdl}DummyWsdlOperationRequest
> at com.sun.jbi.nms.wsdl11wrapper.impl.WrapperParserImpl.parse(WrapperParserImpl.java:83).
>
> This is an user configuration issue. The redelivery requirements page
http://soabi.stc.com:8080/JSPWiki/Wiki.jsp?page=CAPS.common.library.redelivery should mention that the message type of
the actual endpoint and the redirect endpoint has to be the same.
>
> Changing the message type in the OutputToFile wsdl to point to the message defined in the DummyWsdl file made the
redirect to the file to work as they are now of the same message type.
>
> Jun & Venkat
> would it be possible to provide design time validation in the comp app project to ascertain that the message types of
the actual endpoint and the redirect endpoint are the same ? This would be a nice, as it would capture such user errors
at design time and not wait for runtime failure.
>
>Thanks
>-Philip
Comment 1 Jun Qian 2008-03-26 03:28:07 UTC 
The message type to the redirect endpoint doesn't have to be exactly the same as the message type to the actual
endpoint. However, the former has to be a "super" type of the latter.

The connections in CASA today are at the interface level, not at the operation level, so it doesn't make too much sense
to do the validation today. When we have some other view showing connections at the operation level, we will add this
type of validation.