Oracle ADF Basic: Making use of the ApplicationModule Session

Written By: Pascal Alma on May 3, 2008 No Comment

If you have to use a where-clause being based on session-scoped parameters in several viewobjects, it might be good to know you also have a session scope in Oracle's ADF BC Application Module. You get access to it by simply calling getSession() in your ApplicationModule. On the Session object which you then receive, you can perform a getUserData() which will give you a Hashtable object. In this object you can store the session parameters you like. This way you don't have to pass the parameters out of the Servlet Session object to the ApplicationModule for each call to a viewobject.
You might even overwrite the viewobject's executeQuery and check for a named bind variable to be available in the getUserdata() Hashtable. You will get something like this:

PLAIN TEXT

JAVA:

@Override
public void executeQuery()
{
Variable[] vars = ensureVariableManager().getVariables();
for (Variable var: vars)
{
if (getNamedWhereClauseParam(var.getName()) == null ||
StringUtils.isEmpty(getNamedWhereClauseParam(var.getName()).toString()))
{
setNamedWhereClauseParam(var.getName(),
getApplicationModule().getSession().getUserData().get(var.getName()));
}
}
super.executeQuery();
}

You can put this method in your base ViewObject so all your viewobjects that extends this base class will then get the filtering functionality without any extra effort.
What we did was getting the necessary information from the database (based on the loggedIn userName) and store it in the hashtable.
We did this by overriding the prepareSession() of the Application Module. As long as you don't break the naming convention by giving the bindVariables in your viewobject exactly the same name as the corresponding attribute in your Userdata table this works very nice.