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 105686 - RM Headers are getting added by default in input/output policy
Summary: RM Headers are getting added by default in input/output policy
Status: RESOLVED WONTFIX
Alias: None
Product: webservices
Classification: Unclassified
Component: WSIT (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-05 07:52 UTC by shyam_rao
Modified: 2007-07-18 15:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description shyam_rao 2007-06-05 07:52:47 UTC
I am using wsit plugin v 2.34. I see, RM headers are getting added into
input/output policy by default, though i am not using "Reliable Message
Delivery" option. 

Presence of RM headers does not break anything, but it could just provide a
little performance imporvement when trying to Sign the Message as well as when
Trying to do PolicyVerification  of the Incoming Message.

Input / Output Policy Snippet :
===============================
   <wsp:Policy wsu:Id="NewWebServicePortBinding_echo_Input_Policy">
       <wsp:ExactlyOne>
           <wsp:All>
               <sp:EncryptedParts>
                   <sp:Body/>
               </sp:EncryptedParts>
               <sp:SignedParts>
                   <sp:Body/>
                   <sp:Header Name="To"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="From"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="FaultTo"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="ReplyTo"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="MessageID"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="RelatesTo"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="Action"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="AckRequested"
Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                   <sp:Header Name="SequenceAcknowledgement"
Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                   <sp:Header Name="Sequence"
Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
               </sp:SignedParts>
           </wsp:All>
       </wsp:ExactlyOne>
   </wsp:Policy>
   <wsp:Policy wsu:Id="NewWebServicePortBinding_echo_Output_Policy">
       <wsp:ExactlyOne>
           <wsp:All>
               <sp:EncryptedParts>
                   <sp:Body/>
               </sp:EncryptedParts>
               <sp:SignedParts>
                   <sp:Body/>
                   <sp:Header Name="To"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="From"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="FaultTo"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="ReplyTo"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="MessageID"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="RelatesTo"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="Action"
Namespace="http://www.w3.org/2005/08/addressing"/>
                   <sp:Header Name="AckRequested"
Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                   <sp:Header Name="SequenceAcknowledgement"
Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                   <sp:Header Name="Sequence"
Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
               </sp:SignedParts>
           </wsp:All>
       </wsp:ExactlyOne>
   </wsp:Policy>
Comment 1 Martin Grebac 2007-07-18 15:00:24 UTC
The fix is kind of complex and the gain from it is not a big deal. On the other side, it might break more than fix,so I
do not plan to apply it. The behaviour after the change seems less clear to me than the current one.