If you come from developing servlets/JSPs then your first question will be: How do JAXFront sessions relate to HTTP sessions?


JAXFront DOM handlers are living in sessions, which are administratered inside the JAXFront runtime environment. The sessions are kept in parallel to HTTP sessions, i.e. HTTP sessions may be used by other servlets/JSPs that may be part of your web application - but JAXFront itself does not require them. It is no problem to reach HTTP sessions from a DOM hanlder object via an API.


Why is JAXFront not using straight HTTP sessions? Well, the ugly problem is that HTTP sessions are sometimes the same for multiple browser instances. If you, in Internet Explorer, open up a new browser from an existing one then the corresponding session object on the server is shared between the browsers. In the JAXFront session management, each instance of a browser has its own clearly assigned session.

 

Each JAXFront session holds a DOM handler object (DefaultDOMHandler) which initializes the underlying DOM based on the url params. Interactions with the DOM is done through this handler. If one needs to right some specific interaction code for loading,storing or releasing a DOM, see next caption.
 
The proper start of a JAXFront session is to open a JAXFront page via the following JAXFrontServer servlet: http://localhost:8080/jaxfront/... or by dispatching a servlet request to the JAXFrontServletAdapter. 
 

A JAXFront session normally ends if the page which was opened with the JAXFrontServer servlet is closed. This happens for example if the user shuts down the browser or if the user is loading a new page into the frame in which previously the JAXFrontServer servlet was called.
If a JAXFront session is without user interaction for a long time, then the session is timed out on the server. Should the user come back to continue interaction then a corresponding message pops up. The default timeout is 20 minutes. 

 

  • Keine Stichwörter