RE: Session Tracking question. -- Use og EJB

2001-08-10 Thread Laurent Letellier
and I'm afraid the problem you're talking about could happen. Thanks, Laurent -Message d'origine- De : Morten J Nielsen [mailto:[EMAIL PROTECTED]] Envoyé : vendredi 10 août 2001 10:35 À : [EMAIL PROTECTED] Objet : RE: Session Tracking question. -- Use og EJB Hi Venkat, Just

RE: Session Tracking question. -- Use of EJB

2001-08-10 Thread Morten J Nielsen
cc: ontoo.comSubject: RE: Session Tracking question. -- Use og EJB

RE: Session Tracking question. -- Use of EJB

2001-08-10 Thread Laurent Letellier
PROTECTED]] Envoyé : vendredi 10 août 2001 11:51 À : [EMAIL PROTECTED] Objet : RE: Session Tracking question. -- Use of EJB Hi Laurent, Regarding the out of synch for objects stored in the servlet session, this is of course only interesting for Entity EJB's. The problem is related

RE: Session Tracking question. -- Use of EJB

2001-08-10 Thread nielsenk
@frcc: (bcc: Keith Nielsen/digitalesp) ontoo.com Subject: RE: Session Tracking question. -- Use of EJB

RE: Session Tracking question.

2001-08-02 Thread Christian Cerny
-- Thanks for the reply. ~Venkat -Original Message- From: Christian Cerny [mailto:[EMAIL PROTECTED]] Sent: Monday, July 30, 2001 1:40 AM To: '[EMAIL PROTECTED]' Subject: RE: Session Tracking question. Hi, Apache Soap 2.2 is able to track a HttpSession. As long as you are working with the same

RE: Session Tracking question.

2001-08-01 Thread venkat reddy
: Monday, July 30, 2001 1:40 AM To: '[EMAIL PROTECTED]' Subject: RE: Session Tracking question. Hi, Apache Soap 2.2 is able to track a HttpSession. As long as you are working with the same Call-object on the client-side your HttpSession is tracked using cookies. (this behavior is on per default

RE: Session Tracking question.

2001-07-30 Thread Christian Cerny
Hi, Apache Soap 2.2 is able to track a HttpSession. As long as you are working with the same Call-object on the client-side your HttpSession is tracked using cookies. (this behavior is on per default) Futhermore the value of the scope Parameter in your DeploymentDescripter for your Class should