OpenSAML user discussion

I think found a workaround using a RPC SOAPHandler.
The samlRequest is sent 'unsigned' to the clientapplication building the 
soapmessage.
A soaphandler intervenes when the soap is allready generated.
It takes out the samlRequest in the soapbody, signs it with opensaml api, 
puts it back and gives control back to the client that sends the soap to the 
webservice.
That way, the xml in the soapbody is the same (including namespaces) as the 
xml at the time the signature is set.

It seems to work just fine.

Frederik