Need Help on Secure SOAP Request on WebLogic

[Dheeraj <dh...@optimyz.com>]

Hi All,

I am getting the following error

One or more references failed to validate: <Reference
URI="#Created-58de78a0-51f2-11d8-b837-53f697fa7fef" /> <Reference
URI="#Created-58f3fc70-51f2-11d8-b837-53f697fa7fef" />

When I try to send the secure (Signed and Encrypted) request to a secure web
service on WebLogic. Please let me know any clue to solve this problem.

TIA
Dheeraj Goswami

----- Original Message ----- 
From: "Martin Gainty" <mg...@hotmail.com>
To: <so...@ws.apache.org>
Cc: <Ci...@doa.state.wi.us>
Sent: Wednesday, January 28, 2004 4:27 PM
Subject: Re: SOAP fault on WAS 5 z/0s


> Cindy
> I would add DeployedServices.ds to your war then ear and redeploy
> -M
> ----- Original Message -----
> From: "Gramann, Cindy" <Ci...@doa.state.wi.us>
> To: <so...@ws.apache.org>
> Sent: Wednesday, January 28, 2004 5:42 PM
> Subject: SOAP fault on WAS 5 z/0s
>
>
> > I'm having a problem running the Apache SOAP StockQuoteService sample
> > application on Websphere 5 for z/0s. I used the wizards in WSAD to
> generate
> > the web service for both server and client. Everything runs fine under
> > localhost. I then change the ports to run on z/0s. When I run the
service
> on
> > z/0s, it fails on the SOAP call with the following error:
> >
> > exception: [SOAPException: faultCode=SOAP-ENV:Server;
> >
>
msg=rO0ABXNyADVjb20uaWJtLndlYnNwaGVyZS5tYW5hZ2VtZW50LmV4Y2VwdGlvbi5BZG1pbkV4
> >
>
Y2VwdGlvbkeKepmuCDHrAgAAeHIAIGNvbS5pYm0ud3MuZXhjZXB0aW9uLldzRXhjZXB0aW9uS4Pu
> >
>
bt1K6D0CAAFMAAdpdkNhdXNldAAVTGphdmEvbGFuZy9UaHJvd2FibGU7eHIAE2phdmEubGFuZy5F
> >
>
eGNlcHRpb27Q/R8+GjscxAIAAHhyABNqYXZhLmxhbmcuVGhyb3dhYmxl1cY1Jzl3uMsCAAFMAA1k
> >
>
ZXRhaWxNZXNzYWdldAASTGphdmEvbGFuZy9TdHJpbmc7eHB0AFBBRE1DMDAwNUU6IFNPQVAgVVJJ
> >
>
IHZpb2xhdGlvbiwgdGhlIGNvcnJlY3QgVVJJIHNob3VsZCBzaG91bGQgYmUgdXJpOkFkbWluU2Vy
> > dmljZXEAfgAG]
> > It seems that there is some kind of delivery error, but the fault
message
> is
> > not helpful at all. I've tried running monitors and traces to help debug
> the
> > problem, but that has not helped. Any suggestions?
> >
> >