Re: Problem invoking WSE 2.0 enabled WebService
- From: "dev" <dev209@xxxxxxxxx>
- Date: 19 Sep 2006 13:46:21 -0700
Thanks Pablo,
The only problem is let's say company A implemented few secure
webservices using WSE. One of the vendor is not yet ready to (or can't)
make the change to thier client (namely adding wse framework). In this
situation they want be able to connect to Comany A's web service.
I agree with what you said. If you are going to manually pass all the
secutiry headers why not just add wse.
Thanks a lot.
Best Regards,
Dev209
.
- References:
- Problem invoking WSE 2.0 enabled WebService
- From: dev
- Re: Problem invoking WSE 2.0 enabled WebService
- From: Pablo Cibraro [MVP]
- Re: Problem invoking WSE 2.0 enabled WebService
- From: dev
- Re: Problem invoking WSE 2.0 enabled WebService
- From: Pablo Cibraro [MVP]
- Problem invoking WSE 2.0 enabled WebService
- Prev by Date: Re: WSE 3.0 UsernameOverTransport Problem
- Next by Date: Re: UsernameOverTransportSecurity+SSL Confusion, please help
- Previous by thread: Re: Problem invoking WSE 2.0 enabled WebService
- Next by thread: WS Security patterns, PerimiterServiceRouter & SoapActor
- Index(es):
Relevant Pages
|
Loading