I have a struts2 action that is invoked by a JavaScript function. The JavaScript function uses uploadify to enable multiple file uploads:
<script type="text/javascript"> $(document).ready(function() { $("#fileupload").uploadify({ 'uploader' : '<%=path%>/js/uploadify-v2.1.4/uploadify.swf', 'script' : 'observationData/Upload.action', ...... }); }); </script>
In the Upload.action method, there's an attempt to retrieve the session object:
public class ObservationDataAction extends ActionSupport{ ...... public String uploadFile() throws Exception { System.out.println("in function uploadFile()"); ...... Map session = ActionContext.getContext().getSession(); System.out.println("Session userID is:"+((SessionUser)session.get("authority.userinfo")).getUserID()); return null; } }
However, when the JavaScript calls the Upload.action, it only prints "in function uploadFile()" but fails to obtain the session userID.
I also tried manually invoking the Upload.action using this URL: "
http://localhost:8080/observationData/Upload.actionI am currently using struts2.1.6.
This is my struts.xml configuration:
<struts> <constant name="struts.enable.DynamicMethodInvocation" value="false"/> <constant name="struts.action.extension" value="action"/> <package name="observationData" namespace="/observationData" extends="struts-default"> <action name="Upload" class="observationDataAction" method="uploadFile"> </action> </package> </struts>
Additionally, I am using org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter as the filter class.
I also attempted to implement the SessionAware interface, but it did not resolve the issue.
If anyone could help identify why the session is not functioning within the uploadFile() method, I would greatly appreciate it.
Extra information: Here is the function used to store the user in the session:
public static final String SESSION_USERINFO = "authority.userinfo";
private static void saveSessionUser(SessionUser sessionUser) {
Map session = ActionContext.getContext().getSession();
session.put(SESSION_USERINFO, sessionUser);
}
Hi! I'm considering a possibility: Could it be that Ajax/JS creates a separate session when calling Upload.action? As a result, we cannot retrieve the user from the new session because we set it in the old session?
Thank you, Xuyuan