Contradictory soap handler guidelines

Question

why does bea say this: "...Message handlers should <b>not</b> be used to implement security or encryption..." (Specifying SOAP Handlers for a Web Service).
but then turns around and contradicts the above with this:
"...A simple example of using handlers is to encrypt and decrypt secure data in the body of a SOAP message..." (Using SOAP Message Handlers to Intercept the SOAP Message).
and this: "...you might design an Encryption handler whose handleRequest() method decrypts secure data in the SOAP request and handleResponse() method encrypts the SOAP response..." (Designing the SOAP Message Handlers and Handler Chains).
does anybody know what BEA's position is on this issue?
many thanks.

Answer 1

If i understand your requirement correctly then you can do following to register SOAP handlers
QName portName = new QName( "http://tutorial/sample4/",
"ServicePort");
HandlerRegistry registry = service.getHandlerRegistry();
List handlerList = new ArrayList();
handlerList.add( new HandlerInfo( ClientHandler.class, null, null ) );
registry.setHandlerChain( portName, handlerList )
http://e-docs.bea.com/wls/docs81/webserv/interceptors.html