Mailing-List: contact dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ws.apache.org
Received-SPF: pass (nike.apache.org: domain of shivendra2u@gmail.com
 designates 74.125.82.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=TocBLkgnL1lL8AdG5y0exuqVqiJDp74qKuPYzm6l+d/WOlyQ1+N1QnsboOGk1uLjHu
         n6PNlLObZjoWhAMk63Dunl8IZwFO8RwXYiFRcKAstcUI7aXEVya+rrG+eCmX24u0mw6k
         4Hjwi2TcWBX5ett78wVpfugNsK6OyXJEIoJ9Y=
MIME-Version: 1.0
In-Reply-To: <BLU142-W18BD70AE8208DDFF5A971FAE8E0@phx.gbl>
References: <BANLkTimjcvUaL-gAae4pyc_OE5HXS_rQJQ@mail.gmail.com>
	<BLU142-W18BD70AE8208DDFF5A971FAE8E0@phx.gbl>
Date: Fri, 20 May 2011 00:08:34 +0530
Message-ID: <BANLkTimCs9Ezwa+qOTCiSsrYuvYoFuFS3Q@mail.gmail.com>
Subject: Re: Why addressing module could not be engaged at service level?
From: shivendra tripathi <shivendra2u@gmail.com>
To: dev@ws.apache.org
Content-Type: multipart/alternative; boundary=0016e6dbea3b0653ba04a3a55050

--0016e6dbea3b0653ba04a3a55050
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Martin!

Let me be more specific about the issue I am facing.

I am reusing the configuration context at the client side. And once I make
axis2 client call with addressing module engaged; subsequent calls to remot=
e
service is going with addressing header even if addressing is not engaged i=
n
ServiceClient object created for second call.

I don't want addressing headers to appear if not engaged in a particular
instance of ServiceClient. And I have to reuse configContext.
One option i could think is setting "disableAddressingForOutMessages" flag.

What do you guys propose?

Thanks,
Shiv

On Thu, May 19, 2011 at 11:39 PM, Martin Gainty <mgainty@hotmail.com> wrote=
:

>
>    1. *Transport Phase* - The handlers are in the phase that processes
>    transport specific information such as validating incoming messages by
>    looking at various transport headers, adding data into message context=
s,
>    etc.
>    2. *Pre-Dispatch Phase*- The main functionality of the handlers in thi=
s
>    phase is to populate message context to do the dispatching. For exampl=
e,
>    processing of addressing headers of the SOAP message, if any, happens =
in
>    this phase. Addressing handlers extract information and put them in to=
 the
>    message context.
>    3. *Dispatch Phase* - The Dispatchers run in this phase and try to fin=
d
>    the correct service and operation this particular message is destined =
for.
>    The post condition of the dispatch phase (any phase can contain a post
>    condition) checks whether a service and an operation were found by the
>    dispatchers. If not, the execution will halt and return a "service not
>    found' error.
>    4. *User Defined Phases* - Users can engage their custom handlers here=
.
>    5. *Message Validation Phase* - Once the user level execution has take=
n
>    place, this phase validates whether SOAP Message Processing has taken =
place
>    correctly.
>    6. *Message Processing Phase* - The Business logic of the SOAP message
>    is executed here. A Message Receiver is registered with each Operation=
.
>    This message receiver (associated to the particular operation) will be
>    executed as the last handler of this phase.
>
>
> addressing is handled at layer2 (pre-dispatch)..addressing handlers extra=
ct
> addresses and populate the message-context in this layer
> the dispatcher on layer 3 will transmit the message (populated by layer2)
> to the registered service
> after the dispatcher dispatches the request the service-modules associate=
d
> the registered service and the service itself are executed
> Martin Gainty
> ______________________________________________
> Jogi =E9s Bizalmass=E1gi kinyilatkoztat=E1s/Verzicht und
> Vertraulichkeitanmerkung/Note de d=E9ni et de confidentialit=E9
>
> Ez az =FCzenet bizalmas.  Ha nem =F6n az akinek sz=E1nva volt, akkor k=E9=
rj=FCk, hogy
> jelentse azt nek=FCnk vissza. Semmif=E9le tov=E1bb=EDt=E1sa vagy m=E1sola=
t=E1nak k=E9sz=EDt=E9se
> nem megengedett.  Ez az =FCzenet csak ismeret cser=E9t szolg=E1l =E9s sem=
mif=E9le jogi
> alkalmazhat=F3s=E1ga sincs.  Mivel az electronikus =FCzenetek k=F6nnyen
> megv=E1ltoztathat=F3ak, ez=E9rt minket semmi felel=F6s=E9g nem terhelhet =
ezen =FCzenet
> tartalma miatt.
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugt=
e
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut =EAtre privil=E9gi=E9. Si vous n'=EAt=
es pas le destinataire pr=E9vu, nous te demandons avec bont=E9 que pour sat=
isfaire informez l'exp=E9diteur. N'importe quelle diffusion non autoris=E9e=
 ou la copie de ceci est interdite. Ce message sert =E0 l'information seule=
ment et n'aura pas n'importe quel effet l=E9galement obligatoire. =C9tant d=
onn=E9 que les email peuvent facilement =EAtre sujets =E0 la manipulation, =
nous ne pouvons accepter aucune responsabilit=E9 pour le contenu fourni.
>
>
>
>
>
>
> ------------------------------
> Date: Thu, 19 May 2011 23:12:10 +0530
> Subject: Why addressing module could not be engaged at service level?
> From: shivendra2u@gmail.com
> To: dev@ws.apache.org
>
>
> Hi,
>
> Just wanted to know, if there is any specific reason behind "addressing
> module could only be engaged at global level", while other module e.g.
> rampart could be enabled at service level?
>
> Why similar check is not present in addressing out handler which could be
> seen in rampartSender?
>
> if (!msgContext.isEngaged(WSSHandlerConstants.SECURITY_MODULE_NAME)) {
>           return InvocationResponse.CONTINUE;
>         }
>
> Appreciate any pointer.
>
> Thanks,
> Shiv
>

--0016e6dbea3b0653ba04a3a55050
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Martin!<div><br></div><div>Let me be more specific about the issue I=
 am facing.</div><div><br></div><div>I am reusing the configuration context=
 at the client side. And once I make axis2 client call with addressing modu=
le engaged; subsequent calls to remote service is going with addressing hea=
der even if addressing is not engaged in ServiceClient object created for s=
econd call.</div>
<div><br></div><div>I don&#39;t want addressing headers to appear if not en=
gaged in a particular instance of ServiceClient. And I have to reuse config=
Context.</div><div>One option i could think is setting &quot;disableAddress=
ingForOutMessages&quot; flag.</div>
<div><br></div><div>What do you guys propose?</div><div><br></div><div>Than=
ks,</div><div>Shiv</div><div><br><div class=3D"gmail_quote">On Thu, May 19,=
 2011 at 11:39 PM, Martin Gainty <span dir=3D"ltr">&lt;<a href=3D"mailto:mg=
ainty@hotmail.com">mgainty@hotmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">


<div>
<ol><li><strong>Transport Phase</strong> - The handlers are in the
phase that processes transport specific information such as
validating incoming messages by looking at various transport
headers, adding data into message contexts, etc.</li><li><strong>Pre-Dispat=
ch Phase</strong>- The main functionality of
the handlers in this phase is to populate message context to do the
dispatching. For example, processing of addressing headers of the
SOAP message, if any, happens in this phase. Addressing handlers
extract information and put them in to the message context.</li><li><strong=
>Dispatch Phase</strong> - The Dispatchers run in this
phase and try to find the correct service and operation this
particular message is destined for.<br>
The post condition of the dispatch phase (any phase can contain a
post condition) checks whether a service and an operation were
found by the dispatchers. If not, the execution will halt and
return a &quot;service not found&#39; error.</li><li><strong>User Defined P=
hases</strong> - Users can engage their
custom handlers here.</li><li><strong>Message Validation Phase</strong> - O=
nce the user level
execution has taken place, this phase validates whether SOAP
Message Processing has taken place correctly.</li><li><strong>Message Proce=
ssing Phase</strong> - The Business logic
of the SOAP message is executed here. A <a>Message
Receiver</a> is registered with each Operation. This message
receiver (associated to the particular operation) will be executed
as the last handler of this phase.</li></ol><br>addressing is handled at la=
yer2 (pre-dispatch)..addressing handlers extract addresses and populate the=
 message-context in this layer<br>the dispatcher on layer 3 will transmit t=
he message (populated by layer2) to the registered service<br>
after the dispatcher dispatches the request the service-modules associated =
the registered service and the service itself are executed<br>Martin Gainty=
 <br>______________________________________________ <br>Jogi =E9s Bizalmass=
=E1gi kinyilatkoztat=E1s/Verzicht und Vertraulichkeitanmerkung/Note de d=E9=
ni et de confidentialit=E9<br>
<div>=A0</div><div>Ez az
=FCzenet bizalmas. =A0Ha nem =F6n az akinek sz=E1nva volt, akkor k=E9rj=FCk=
, hogy
jelentse azt nek=FCnk vissza. Semmif=E9le tov=E1bb=EDt=E1sa vagy m=E1solat=
=E1nak
k=E9sz=EDt=E9se nem megengedett. =A0Ez az =FCzenet csak ismeret cser=E9t sz=
olg=E1l =E9s
semmif=E9le jogi alkalmazhat=F3s=E1ga sincs. =A0Mivel az electronikus =FCze=
netek
k=F6nnyen megv=E1ltoztathat=F3ak, ez=E9rt minket semmi felel=F6s=E9g nem te=
rhelhet
ezen =FCzenet tartalma miatt.<br><br>Diese Nachricht ist vertraulich. Sollt=
en Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um ein=
e Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist u=
nzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen=
 und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Mani=
pulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt ueberne=
hmen.<br>
</div><pre>Ce message est confidentiel et peut =EAtre privil=E9gi=E9. Si vo=
us n&#39;=EAtes pas le destinataire pr=E9vu, nous te demandons avec bont=E9=
 que pour satisfaire informez l&#39;exp=E9diteur. N&#39;importe quelle diff=
usion non autoris=E9e ou la copie de ceci est interdite. Ce message sert =
=E0 l&#39;information seulement et n&#39;aura pas n&#39;importe quel effet =
l=E9galement obligatoire. =C9tant donn=E9 que les email peuvent facilement =
=EAtre sujets =E0 la manipulation, nous ne pouvons accepter aucune responsa=
bilit=E9 pour le contenu fourni.</pre>
<br><br><br><br><br><hr>Date: Thu, 19 May 2011 23:12:10 +0530<br>Subject: W=
hy addressing module could not be engaged at service level?<br>From: <a hre=
f=3D"mailto:shivendra2u@gmail.com" target=3D"_blank">shivendra2u@gmail.com<=
/a><br>
To: <a href=3D"mailto:dev@ws.apache.org" target=3D"_blank">dev@ws.apache.or=
g</a><div><div></div><div class=3D"h5"><br><br>Hi,<div><br></div><div>Just =
wanted to know, if there is any specific reason behind &quot;addressing mod=
ule could only be engaged at global level&quot;, while other module e.g. ra=
mpart could be enabled at service level?=A0</div>

<div><br></div><div>Why similar check is not present in addressing out hand=
ler which could be seen in rampartSender?</div><div><br></div><div><div>if =
(!msgContext.isEngaged(WSSHandlerConstants.SECURITY_MODULE_NAME)) {</div>

<div>=A0 =A0 =A0 =A0 =A0 return InvocationResponse.CONTINUE; =A0 =A0 =A0 =
=A0</div><div>=A0 =A0 =A0 =A0 } =A0 =A0 =A0 =A0</div></div><div><br></div><=
div>Appreciate any pointer.</div><div><br></div><div>Thanks,</div><div>Shiv=
</div> 		 	   		  </div></div></div>

</blockquote></div><br></div>

--0016e6dbea3b0653ba04a3a55050--