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 remote service is going with addressing header even if addressing is not engaged in 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 <[email protected]> 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 contexts, > etc. > 2. *Pre-Dispatch Phase*- 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. > 3. *Dispatch Phase* - The Dispatchers run in this phase and try to find > 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 taken > 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 extract > 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 associated > the registered service and the service itself are executed > Martin Gainty > ______________________________________________ > Jogi és Bizalmassági kinyilatkoztatás/Verzicht und > Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy > jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése > nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi > alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen > megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet > tartalma miatt. > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > 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 être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire informez > l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci > est interdite. Ce message sert à l'information seulement et n'aura pas > n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité 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: [email protected] > To: [email protected] > > > 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 >
