axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Schwarz" <schw...@commsult.de>
Subject Re: axis and cryptography ?
Date Wed, 03 Apr 2002 07:53:49 GMT
I need more detail...

what do you exactly mean with "system property" ?

com.acme.SignMessageHandler is the handler class created by you ?

what means "to use a delegate" ?

I hope, I'm not to stupid...

----- Original Message ----- 
From: <matt@smallleap.com>
To: <axis-user@xml.apache.org>
Cc: <axis-user@xml.apache.org>
Sent: Tuesday, April 02, 2002 3:47 PM
Subject: Re: axis and cryptography ?


> For brevity:
> 
> Set the system property "axis.ClientConfigFile" to the
> location of your WSDD client side file. For us, the
> WSDD file looked something like this - 
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment name="defaultClientConfig"
>             xmlns="http://xml.apache.org/axis/wsdd/"
>            
> xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> 
>  <globalConfiguration>
>   <requestFlow> 
>     <handler type="java:com.acme.SignMessageHandler"/>
>   </requestFlow> 
>  </globalConfiguration>
> 
>  <transport name="http"
> pivot="java:org.apache.axis.transport.http.HTTPSender"/>
>  <transport name="local"
> pivot="java:org.apache.axis.transport.local.LocalSender"/>
> </deployment>
> 
> We then use a delegate in the web tier that calls the
> stub. The stub fires up the Axis engine which invokes
> the handler chain. This means that our sign handler
> gets called before the transport handler which means we
> are signing the message after the stub has created it
> and just before transport sends it. If you need anymore
> details, just let me know.
> 
> -Matt
> 
> 
> "Michael Schwarz" wrote
> 
> > 
> > Do you have a code example ?
> > 
> > ----- Original Message -----
> > From: "Matt Baldree" <matt@smallleap.com>
> > To: <axis-user@xml.apache.org>
> > Sent: Tuesday, April 02, 2002 2:33 PM
> > Subject: Re: axis and cryptography ?
> > 
> > 
> > > What we did was override the client side deployment
> descriptor file to
> > > define a global handler that signs the request. I
> don't recommend
> > modifying
> > > the stubs since you have to remember to modify them
> every time.
> > >
> > > -Matt
> > >
> > > ----- Original Message -----
> > > From: "Mark Volkmann" <volkmann2@charter.net>
> > > To: <axis-user@xml.apache.org>
> > > Sent: Tuesday, April 02, 2002 5:31 AM
> > > Subject: Re: axis and cryptography ?
> > >
> > >
> > > > I see two options.
> > > > 1) modify the generated stub to do this
> > > > 2) use an Axis engine on the client-side with a
> request handler that
> > > > encrypts and a response handler that decrypts
> (I've never used
> > client-side
> > > > handlers before, only read about them.)
> > > >
> > > > ----- Original Message -----
> > > > From: "Michael Schwarz" <schwarz@commsult.de>
> > > > To: <axis-user@xml.apache.org>
> > > > Sent: Tuesday, April 02, 2002 1:39 AM
> > > > Subject: axis and cryptography ?
> > > >
> > > >
> > > > > Hello! (sorry for the bad english)
> > > > >
> > > > > I have a question concerning the transmission
> of the client request.
> > the
> > > > > client uses the stub, created by wsdl2java
> (from axis).
> > > > > I need to en-, decrypt the serialized objects
> (method paramters) of
> > the
> > > > > SOAPPart, befor the Request is transmitted (
> Call.invoke( ... ) ).
> > > > >
> > > > > any idea ?
> > > > >
> > > > > Black
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> 
> 


Mime
View raw message