But rampart does all the wsse header stuff in the moment you send the message
so i think its easier because i have to remove things from these methods
because i dont want them to do SOAP headers or envelope ( this is done by
axis ) or WSSE headers ( this is done by rampart ) 
In fact i need NotificationConsumerClient.notify(NotificationMessage[]) to
get rid off SOAP stuff and directly post to AXIS engine the WSNotification
Body with the SOAP:action described in the wsdl 

I am right? 

If i am, ¿ i need to download MUSE source and delete from
NotificationConsumerClient the lines that do SOAP stuff and then find the
way ( should be easy  ) to give the WS-notification message  to AXIS2 to
leave him do all the SOAP and WSSE stuff ?

thanks.



Vinh Nguyen (vinguye2) wrote:
> 
> Hi,
> I'm not familiar with Rampart, but it looks like in your code below, you
> are starting in the right direction.  The general callflow is:
> 
> NotificationProducer.publish(QName,Element[])
>  > SubscriptionManager.publish(NotificationMessage)
>    > NotificationConsumerClient.notify(NotificationMessage[])
> 
> NotificationProducer.publish() only takes in data that will go into the
> notification body.  Also, NotificationMessage itself represents the
> message body, so from your capability classes, currently there's no way to
> specify custom header properties to send along with the message.
> 
> NotificationConsumerClient.notify() is the key method that constructs the
> actual XML payload and sends it out.  So you could try to override this
> method and add your custom WSSE header properties to the payload.
> 
> Overall, I think to include custom header properties in outgoing
> notification messages, you need to:
> 
> 1) Extend all 3 classes above
> 2) Add additional methods that takes in customer header properties along
> with the usual body elements.
> 3) Have these classes call each other instead of the default Muse classes.
> 4) Update your new NotificationConsumerClient.notify() method to add the
> custom header properties to the xml payload.
> 5) From your capabilities, call your custom NotificationProducer.
> 
> -Vinh
> 
> 

-- 
View this message in context: 
http://www.nabble.com/axis2-deployment-and-configuration-tp9736934p14406575.html
Sent from the Muse User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to