Hi Nandana, mmm thanks again, I totally get it if the security is not well setup there is no point in trying to secured the error message, the misunderstanding emerge when I was told the OWSM handled this smoothly and it was required for me to do so in axis2. but after this and a little chat with the oracle web services manager guys everything was cleared.
Thanks Nandana, I really appreciate your help ___________________________ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. SCDJWS on Going... On Thu, Jul 9, 2009 at 1:25 AM, Nandana Mihindukulasooriya < nandana....@gmail.com> wrote: > Hi Marcus, > Rampart expect only service faults to be secured. Security faults > are not expected to be secured. You can find more details in this JIRA [1]. > Can you also post the response message ? > > regards, > Nandana > > [1] - https://issues.apache.org/jira/browse/RAMPART-90 > > > On Thu, Jul 9, 2009 at 2:22 AM, m4rkuz <m4r...@gmail.com> wrote: > >> >> Hi Everyone, >> >> Here again, now I think I have a question instead of a problem, you see >> I'm consuming a ws from an oracle web services manager, this ws is secured >> (signed and authenticated) but when I get an error from OWSM this messages >> comes with out security headers with a description of the fault, but my >> axis client is always expecting a secured response so it crash... is this a >> normal behavior ? is there a work around? any ideas? >> >> looking forward for your input, >> >> >> Marcus Sánchez Díaz. >> Enterprise Developer. >> SCJP - SCWCD. >> SCDJWS on Going... >> >> PD: hope I made myself understood, if not.. just ask me anything you want >> :) >> > > > >
