Hi Kumaran
This is to be expected as Synapse by default uses a high performance
non-blocking http/s transport implementation instead of a servlet
runtime based transport. Thus typically you do not have a
HttpServletRequest around. Are you trying to build a 'stateful'
mediation configuration? One possibility would be to implement your
required logic within your custom mediator - which is able to store
state, and also replicate it within a clustered environment. If you can
elaborate the business requirement you are trying to achieve by
accessing the http session, we could suggest a technical alternative to
achieve the same over the NIO-http/s transport
asankha
Venkatesan, Kumaran wrote:
Hi,
We have planned to use the synapse as mediation layer for our service
based architecture.
There is a requirement to get the handle of the HttpServletRequest
object under the custom mediator(SessionMediator.java) to tackle the
session management.
Have tried the below but giving null value for the
“HttpServletRequest” object.
*public** class* SessionMediator* implements* Mediator {
* private** static** final* Log/ log/ =
LogFactory./getLog/(DiscountQuoteMediator.*class*);
* public* SessionMediator(){}
* public** boolean* mediate(MessageContext mc) {
Axis2MessageContext axis2mc = (Axis2MessageContext)mc;
org.apache.axis2.context.MessageContext axis2MessageCtx =
axis2mc.getAxis2MessageContext();
HttpServletRequest request =
(HttpServletRequest)axis2MessageCtx.getProperty(HTTPConstants./MC_HTTP_SERVLETREQUEST/);
Pls help how to get the “HttpServletRequest”
With Regards
Kumaran
This email is confidential. If you are not the addressee tell the sender
immediately and destroy this email
without using, sending or storing it. Emails are not secure and may suffer
errors, viruses, delay,
interception and amendment. Standard Chartered PLC and subsidiaries ("SCGroup")
do not accept liability for
damage caused by this email and may monitor email traffic.
