Frontman2 HttpSession

[Howard Watson]

import org.bibeault.frontman.Command;
import org.bibeault.frontman.CommandContext;
import javax.servlet.ServletException;
import java.io.IOException;

import javax.servlet.http.HttpSession;

public class initApp implements Command {

   public void execute(CommandContext commandContext) throws ServletException, IOException {

// ??? Am I setting up session wrong for frontman ???

 // get current session state
      HttpSession session = commandContext.getRequest().getSession(false);

      // invalidate any existing sessions
      if (session != null) {

         session.invalidate();

      }

      //and create a new one
      session = commandContext.getRequest().getSession(true);

/*
* At this point I have two choices to set a session value
* not including - import org.bibeault.frontman.ScopedContext;
*
* It makes me think I should not need -
* import javax.servlet.http.HttpSession;
*
* But, I can not make it work any other way
*
*/

 commandContext.getSession().setAttribute("userDN", userDN);

      // OR

      session.setAttribute("userDN", userDN);

   }
}

[Bear Bibeault]

It doesn't matter. The session is the session and which you get it is immaterial.

[Howard Watson]

// ??? Am I setting up session wrong for frontman ???

So I do need (import javax.servlet.http.HttpSession;)

I thought I was missing something in utilizing Frontman.

[Bear Bibeault]

No. Frontman is a very lightweight addition to, not replacement for, the normal Servlet environment. Everything about the servlet environment stays the same and can be used as normal.

[Howard Watson]

Then it is working as advertised. Thank you for your time.


From doc:

No hiding or getting in the way of how the servlet API works.
Generally usable, but designed with Model 2 applications using scriptless JSP 2 pages in mind.
No required on-page impact: no required declarations, directives or tags.
No unnecessary bells and whistles.

[Bear Bibeault]