4 Replies Latest reply on Sep 9, 2006 12:02 AM by Raja

    ConversationEntry -- Should lastRequestTime equal startTime

    Raja Master

      When a conversation is created, the ConversationEntry object has the starttime equal to the current time and the lastRequesttime set to 0. Should the lastRequestTime be also initialized to the current time stamp? Here is why Im asking this.
      In my application, I start a conversation on a Stateful bean and all Im doing there is displaying the view. A ConversationEntry is created at this point of time. The view has a #{categories} which is a @Factory and it initializes the categories Array. The problem is that this variable(and the rest of them) are not stored during the next request in the conversation. This is because the afterPhase calls Manager.instance().conversationTimeout after the view is rendered and this basically deletes the conversationentry. The logic to delete the conversationentry works for a regular timeout but in this case, the conversation creation has just happened(during the render response phase). If we set the lastREquestTime to be the same as the current time, then the difference(currentime - lastRequesttime) will be less than the conversation timeout and the entry will not be deleted.

      im not sure if im explaining my case clearly, but if its not, please ask me for more information.