Also the initial 'loggedIn' parameter needs to be set to false (i did it in the NaluLoginApplicationContextLoginModule constructor) - otherwise there is a null pointer error thrown.
Hi, can you confirm my understanding of the module context behaviour.
I have two parameters initialised in MainContext, one in context and one in applicationContext. Similarly in ModuleContext I have two parameters, one in context and one in applicationContext.
From the Main Application (via MainContext):
-MainContext context: set
-MainContext applicationContext: set
-ModuleContext context: undefined
-ModuleContext applicationContext: undefined
From the Module (via ModuleContext):
-MainContext context: undefined
-MainContext applicationContext: set
-ModuleContext context: set
-ModuleContext applicationContext: undefined
So:
-If a parameter is set in context, then it is only visible within the module it is defined in.
-If a parameter is set in applicationContext in the main application, then it is available in the modules
-If a parameter is set in applicationContext in the module, then it is not available anywhere
The last one does not seem correct. Is this by design, i.e. a module cannot define an application wide context parameter?
So for instance an ‘isLoggedIn’ parameter cannot be defined by the login module for access by other modules?? In this case, would the correct usage to be to fire an ‘UpdateContextEvent’ containing the parameter key and value, and then let the main application handle adding it to the applicationContext?
private final static String USER_ID = "USER_ID";
public String getUserId() {
return (String) super.getApplicationContext()
.get(IolaniContext.USER_ID);
}
public void setUserId(String userId) {
super.getApplicationContext()
.put(IolaniContext.USER_ID,
userId);
} private final static String USER_ID = "USER_ID";
public String getUserId() {
return (String) super.getContext()
.get(IolaniContext.USER_ID);
}
public void setUserId(String userId) {
super.getContext()
.put(IolaniContext.USER_ID,
userId);
} "'loggedIn' from context: "+ this.context.getContext().get("loggedIn") +"; \n" +
"'loggedIn' from applicationContext: "+ this.context.getApplicationContext().get("loggedIn") +"; \n" +Yep. In my module context constructor:
super.getApplicationContext().put("setInModuleContextContructor", "returns undefined");
In my module loader:
this.context.getApplicationContext().put("setInModuleLoader", "returns valid parameter");
In my controllers (login and search):
String contexts =
"loggedIn: "+this.context.getApplicationContext().get("loggedIn")+"; "+ "'setInModuleContextContructor' from context: "+ this.context.getApplicationContext().get("setInModuleContextContructor") +"; \n" +
"'setInModuleLoader' from context: "+ this.context.getApplicationContext().get("setInModuleLoader") ;
Both output:
loggedIn: false; 'setInModuleContextContructor' from context: undefined; 'setInModuleLoader' from context: returns valid parameter
Setting in the Module Context Constructor is not working
