Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Received-SPF: pass (athena.apache.org: domain of pradeepfn@gmail.com
 designates 209.85.220.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=YondIlWPpDBCIcsw9+1jb3gIylY2sixSXpMf1tctcODElaVQUwSTtW2FZf2+mi5CrE
         vSrkkj24sWzW5W7il2RqCLU3ZgxwliGuG0KN8eLPsd+wXZ1nX6r7xYWgY/AYUXHOgIRq
         0TJO9HScZbKTj9bxKY5Mtb6pE11IFbdtZ/ZRc=
MIME-Version: 1.0
From: Pradeep Fernando <pradeepfn@gmail.com>
Date: Tue, 21 Jun 2011 11:39:04 +0530
Message-ID: <BANLkTik+aUcN8tj_rocQin25dX-kA7iOrQ@mail.gmail.com>
Subject: MulipleEntryHashMap s' get operation removes the value from the map
To: axis2-developer <axis-dev@ws.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi devs,


In the axis2 x-form-url-encoded builder it stores HTTP post request
values (in the message body) in MultipleEntryHashMap and attach to the
axis2MessageContext using a property. So when I send a POST request
with a key,value pairs in the message body, axis2 builds a SOAP env
with an empty body, while the properties themselves are stored as a
property in the messageContext.

However this the values stored in the above map are not available,
when i try to access those using a synapse mediator. Since the get
implementation of the map is destroy and read, it must have got
consumed during a axis2 dispatching phase (not sure).

Is there any particular reason  for implementing get operation of the
MultipleEntryHashMap in this manner. ?


Thanks,
-- 
Pradeep Fernando.
http://pradeepfernando.blogspot.com/

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