Re: AW: client handler chaining with different actors (Solved)

[Mailindra <ma...@gmx.net>]

Hai Werner,
Thank you very much. It works like a Charm :-)

Kind Regards,

Mailindra

Dittmann Werner wrote:

>Malindra,
>
>all but the last handler in the chain must have 
>"NoSerialization" as the last keyword in the
>"action" parameter. Plase refer to the description
>of the WSHandlerConstants.java file.
>
>Regards,
>Werner
>
>  
>
>>-----Ursprüngliche Nachricht-----
>>Von: Mailindra [mailto:mailindra@gmx.net] 
>>Gesendet: Donnerstag, 14. Oktober 2004 12:34
>>An: fx-dev@ws.apache.org
>>Betreff: client handler chaining with different actors
>>
>>
>>Hai All,
>>I try to use Handler chaining on client side but still have 
>>no success.
>>Having searched in Milis archive, I found this post: 
>>http://nagoya.apache.org/eyebrowse/ReadMsg?listName=fx-dev@ws.
>>apache.org&msgId=1856460
>>which is exactly the problem I am experiencing.
>>It seems that this bug is already patched ( 
>>http://issues.apache.org/jira/browse/WSFX-33 )
>>So, May be I am missing something.
>>
>>Here is my wsdd on client side:
>><deployment xmlns="http://xml.apache.org/axis/wsdd/"
>>            
>>xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
>><service name="SecurePurchaseService">
>>  <requestFlow>
>>   <handler name="DoSecurity4Merchant" 
>>type="java:org.apache.ws.axis.security.WSDoAllSender" >
>>    <parameter name="actor" value="merchant"/>
>>    <parameter name="user" 
>>value="c82f74d031dabf9d7546f40ad07c32c0_1e149434-9d3a-4adc-928
>>4-4cfdc595012f"/>
>>    <parameter name="passwordCallbackClass" 
>>value="com.mailindra.ws.purchase.security.util.PWCallback"/>
>>    <parameter name="action" value="Encrypt Signature"/>
>>    <parameter name="encryptionPropFile" value="crypto.properties" />
>>    <parameter name="signaturePropFile" value="crypto.properties" />
>>    <parameter name="encryptionKeyIdentifier" 
>>value="X509KeyIdentifier" />
>>    <parameter name="encryptionParts" 
>>value="{Content}{http://schema.mailindra.com/ws/Payment.xsd}Pa
>>    
>>
>ymentInfo" />
>  
>
>>    <parameter name="encryptionUser" 
>>value="1fb7623be7b2f4831ffc3f3741fa09dd_1e149434-9d3a-4adc-928
>>4-4cfdc595012f" 
>>/>
>>   </handler>
>>  
>>   <handler name="DoSecurity4Shipper" 
>>type="java:org.apache.ws.axis.security.WSDoAllSender" >
>>    <parameter name="actor" value="shipper"/>
>>    <parameter name="user" 
>>value="c82f74d031dabf9d7546f40ad07c32c0_1e149434-9d3a-4adc-928
>>4-4cfdc595012f"/>
>>    <parameter name="passwordCallbackClass" 
>>value="com.mailindra.ws.purchase.security.util.PWCallback"/>
>>    <parameter name="action" value="Encrypt Signature"/> 
>>    <parameter name="encryptionPropFile" value="crypto.properties" />
>>    <parameter name="signaturePropFile" value="crypto.properties" />
>>    <parameter name="encryptionKeyIdentifier" 
>>value="X509KeyIdentifier" 
>>/>  
>>    <parameter name="encryptionParts" 
>>value="{Content}{http://schema.mailindra.com/ws/PurchaseOrder.
>>xsd}DeliveryTo" 
>>/>
>>    <parameter name="encryptionUser" 
>>value="1fb7623be7b2f4831ffc3f3741fa09dd_1e149434-9d3a-4adc-928
>>4-4cfdc595012f" 
>>/>
>>   </handler>
>>  </requestFlow>
>></service>
>></deployment>
>>
>>The Signing and Encryption process work fine. But  I only get ONE 
>>security header with the with the second handler actor (shipper).
>>What I expect is to have 2 security headers with diffent actor.
>>
>>FYI: I have tried the latest cvs
>>
>>Could somebody help me regarding this issue ?
>>Many Thanks
>>
>>regards
>>
>>Mailindra
>>
>>    
>>
>
>
>  
>