Hi,
The requirement is to have Stateful mediation configuration. Each
service request from the client will be passed through the
Synapse and need to do basic verification like Session checking and
Funcational Access Profile checking(FAP) before the request
sent to the EPR's deployed on different hosts.
Have utilized the synapse example (sample_380.xml) to test this and used
the HTTP port 8080
<sequence name="main" onError="fault">
<class name="samples.mediators.SessionMediator"/>
2008-01-16 14:43:38,407 [172.18.48.209-SGNHTY3H1S] [main] INFO
HttpCoreNIOListener HTTPS Listener starting on port : 8443
2008-01-16 14:43:38,407 [172.18.48.209-SGNHTY3H1S] [main] INFO
ServerManager Starting transport https on port 8443
2008-01-16 14:43:38,469 [172.18.48.209-SGNHTY3H1S] [main] DEBUG
HttpCoreNIOListener Starting Listener...
2008-01-16 14:43:38,485 [172.18.48.209-SGNHTY3H1S] [main] INFO
HttpCoreNIOListener HTTP Listener starting on port : 8080
2008-01-16 14:43:38,485 [172.18.48.209-SGNHTY3H1S] [main] INFO
ServerManager Starting transport http on port 8080
With Regards
Kumaran
________________________________
From: Asankha C. Perera [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 16, 2008 12:24 PM
To: synapse-dev@ws.apache.org
Cc: Venkatesan, Kumaran
Subject: Re: Custom mediator - Not able to get HttpServletRequest
Hi Kumaran
I notice that you have not yet subscribed to the synapse-dev mailing
list.. As per the page at http://ws.apache.org/synapse/mail-lists.html,
you first need to "subscribe" to the mailing list by sending an email to
"[EMAIL PROTECTED]", and you will then get membership
to post to this list, and will receive any replies to your questions and
other discussion items taking place.
As you may notice from the mail archives, I approved your mail to the
synapse-dev as the moderator, and myself and Paul have replied to it
already (See http://marc.info/?l=synapse-dev&m=120040701518927&w=2)
Hope to see you joining the mailing list soon, and we welcome you to the
Synapse community and look forward to helping you solve your issues
asankha
Venkatesan, Kumaran wrote:
Please any updates on this.
The requirement is to use the custom mediators to validate the session
before sending it to the service end points(EPR).
_____________________________________________
From: Venkatesan, Kumaran
Sent: Tuesday, January 15, 2008 2:25 PM
To: 'synapse-dev@ws.apache.org'
Subject: Custom mediator - Not able to get HttpServletRequest
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_SE
RVLETREQUEST);
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.
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.
