Mailing-List: contact synapse-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: synapse-dev@ws.apache.org
Received-SPF: pass (nike.apache.org: domain of pzfreo@gmail.com designates
 64.233.162.233 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=dGAXMe9jyG4HopHEw3ZzdzufW9BpMyfrHm/WXZ0ucPjMh3Bq9Ky3c9a+X9cQzPYoNo3HFFoIzB1vRkjCXiG44wI9I6qSxjCrnLCmB25srr+yQALK+jIuRlIVgUWJOuQ9Mjvdq5akkwVwgdxzE5f4GWP1q/Ry2azKXIW5ScmQynY=
Message-ID: <88f5d710709052156l789ad18fq84df37e78cbe8ed6@mail.gmail.com>
Date: Thu, 6 Sep 2007 05:56:25 +0100
From: "Paul Fremantle" <pzfreo@gmail.com>
To: synapse-user@ws.apache.org, synapse-dev@ws.apache.org
Subject: Re: Possible to control the WS-Policy soap faults in inSequence of
 proxy in Synapse?
In-Reply-To: <672a01200709051905q5258ae5dhf53dbda416298543@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c2fb3a880709051521q67e86625hb3cb537e99721894@mail.gmail.com>
	 <672a01200709051905q5258ae5dhf53dbda416298543@mail.gmail.com>

Maybe we need to change the way we integrate with Axis2 to ensure that
we get these faults irrespective of where they occur?

For example maybe we could have a handler right at the end of the outflow?

Paul

On 9/6/07, Ruwan Linton <ruwan.linton@gmail.com> wrote:
> Hi John,
>
> See my comments in line,
>
> On 9/6/07, J Bouck <bouck.dev@gmail.com> wrote:
> >
> > I am looking to use Synapse as a proxy for a web service in a simlar
> > fashion to Synapse sample#103.
> > When a WS-policy violation occurs in the proxy inSequence is there a
> > way to return a custom fault rather than the axisFault that is
> > generated in the soapenv namespace?
> >
>
> Hmmm... This policy validation will be done before the message comes in to
> Synapse and hence synapse does not have control over this validation.
> Basically Apache Rampart will be handling security within Axis2 before the
> message comes inside in to Synapse proxy. So I don't think this is easy
> .....
>
> <soapenv:Fault>
> >    <faultcode>soapenv:Server</faultcode>
> >    <faultstring>Missing wsse:Security header in request</faultstring>
> >    <detail />
> > </soapenv:Fault>
> > I can get my custom soap faults to be returned for the proxy by
> > configuring the faultSequence for the proxyService, but they aren't
> > returned when the WS-Policy is violated in the inSequence (e.g.
> > missing or invalid wsse headers).  The proxy faultSequence only seems
> > to be sent when the outSequence fails (e.g.endpoint server port is not
> > open).
>
>
> No, it works fine with the inSequence as well. But what matters is in your
> case Fault is not generated by Synapse, it is before any of the Synapse
> actions. That is why the fault Sequence is not executed.
>
> I tried adding an onError attribute to inSequence for the proxyService
> > but that didn't work.  Any ideas?  I am willing to write a custom
> > mediator if need be.
>
>
> Any ideas from others?
>
> Thanks,
> Ruwan
>
> I would really like to be able to strictly control the soap faults
> > that could ever be returned for security concerns.
> > ~john
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-user-help@ws.apache.org
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>


-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org