axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <>
Subject Re: Service specific configuration of Client-config.wsdd
Date Sun, 17 Apr 2005 21:30:11 GMT
See ws-fx\wss4j\interop\org\apache\ws\axis\oasis\Client_deploy.wsdd.
It has samples for service specific configuration. see the
corresponding sample client code as well.

-- dims

On 4/17/05, Brian Nielsen <> wrote:
> I'm having a problem creating a 'client-config.wsdd' with service specific
> handlers, that'll get executed. When I use the global
> requestFlow/responseFlow there is no problem but when I want to move them
> into the section under a specific service, they are not called. The one I'm
> trying to use was created by first generating the server side stubs to get
> the deploy.wsdd (even though I'm only generating a client). I then run the
> ...utils.Admin with the client flag to get the client-config.wsdd, where I
> add my flows and handlers.
> It's a problem that I've wasted time on before and always given up
> (different versions of axis as well). I've earlier made a related posting
> that unfortunately didn't get any response [1]. In fact I'm quite surprised
> that there isn't more information on client side configuration: how to
> create it and the differences between client-side and server-side. The only
> wsdd reference I can find isn't at the apache site but at[2]
> - cool that they have it but I think the axis site should have some more
> information as well, and I for sure am not the one to enlighten others :-).
> The best piece I've found is in the architecture guide [3].
> I can see that I'm not alone with this problem [4], [5] and [6]. I sure hope
> some of you has the answer or an answer! Maybe I'm missing something or else
> the only reason I can think of, is the seldom usage of service specific
> handlers for clients, since all the examples I can find typically is 'just'
> with the usage of handlers on the global flows. I at least expect this to
> change sooner or later as wss4j, addressing and all the other ws-* specs get
> implemented. Any comments?
> [1]
> 00801c4ab1c$1df7ce70$7300000a@vatican%3e
> [2]
> [3]
> [4]
> [5]
> [6]
> Best regards
> Brian Nielsen

Davanum Srinivas -

View raw message