in Appfactory we have a requirement for intercept http sessions being
created and invalidated. in a typical web application this could be done by
having following settings in web.xml:
<web-app ...>
<listener>
<listener-class>org.wso2.carbon.sample.MyHttpSessionListener</listener-class>
</listener></web-app>
Could we have something similar in jaggery too?
currently having following in jaggery.conf doesn't seems to do anything:
"listener":
{
"listener-class":"org.wso2.carbon.sample.MyHttpSessionListener"
}
Thoughts Please?
P.S.: we are using Jaggery v 0.9.0.ALPHA4.wso2v1
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
