Walid,
I think you misunderstood my American slang comment and took it the wrong way (it's kind of an expression); I am not saying that YOUR question was stupid. If you look below you will see I am asking the 'stupid' question which was "did you check to see if the client sent you a message id?". If it hadn't, you looking for something that didn't exist and there was never anything wrong with your logic or code! Now if I understand you correctly, the client did NOT have a message ID and you were able to add one. So now you are getting the message id at least on the incoming. But NOT on the outgoing. Is that correct? If so, the outgoing maybe a lot more difficult. I have had some issues with the ws addressing headers on the response. I do not know if it affecting your results. Can you show the sent/incoming SOAP message? That would help answer some of the other questions I asked. Brian From: Walid Benkhelouf [mailto:[email protected]] Sent: Friday, August 02, 2013 3:17 PM To: [email protected] Subject: Re: retrieving message_id Sorry for my stupid question ,the thing is that i'm not an expert in axis or java programming ,i was using SOAPUI to simulate the client, i can see now that i can add messageID from SOAPUI ,it's addressing my problem for the incoming,but i just wanna ask one more stupid question :) : -->is there any property in common between the incoming and outgoing message ,that i can use as primary key in my database that is used to store incoming messages.(and when a response occur without a problem ,this message will be drooped) . 2013/8/2 Brian Reinhold <[email protected]> A stupid question: you are sure that the message id field is sent by the client . Is this null response only on the incoming message? And what version? Sending secure or unsecure? Is 'must understand' set by the client? I know I had to do some messing around with the addressing modules to get the ws addressing headers to appear in the response. But it's been a long time so I don't recall the details. Brian From: Walid Benkhelouf [mailto:[email protected]] Sent: Friday, August 02, 2013 2:33 PM To: [email protected] Subject: Re: retrieving message_id hi Martin, yes i did this and i'm getting a null value in both incoming and outgoing, even if "ws-addressing" is engaged. 2013/8/2 Martin Gainty <[email protected]> try mc.getMessageID() (case matters) does this help? Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung 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. _____ Date: Fri, 2 Aug 2013 18:55:18 +0200 Subject: Re: retrieving message_id From: [email protected] To: [email protected] I need to know if there is a property shared between the two messages(IN/OUT) , I was thinking that this property is the message_id contained in "messageContext.getmessageID()" ,but i'm getting a null value when trying to retrieve it (ws-addressing module is engaged) 2013/8/2 Brian Reinhold <[email protected]> Not sure I understand the problem ... is what you are trying to do is retrieve the ws:addressing message id? Brian -----Original Message----- From: Walid Benkhelouf [mailto:[email protected]] Sent: Thursday, August 01, 2013 7:09 PM To: [email protected] Subject: retrieving message_id Hello, I'm developping a module that handler in/out message from axis2 engine and store them in a database. I have two handlers :one for the incoming and one for the outgoing. I need to store the incoming ,and drop the outgoing messages. The problem is that i need to have the same message_id so i can access to the database in the second time(the two messages needs to have the same key). Thanks; --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3392 / Virus Database: 3209/6543 - Release Date: 08/01/13 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3392 / Virus Database: 3209/6545 - Release Date: 08/02/13 _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3392 / Virus Database: 3209/6545 - Release Date: 08/02/13
