RE: [xmlblaster] session object erased????

["Eduardo Catarino" <eduardo.catarino at edisoft.pt>]

Hi Marcel,

	I will try and will forward the results. Thanks again.

Best Regards,
Eduardo Catarino

-----Original Message-----
From: owner-xmlblaster at server.xmlBlaster.org
[mailto:owner-xmlblaster at server.xmlBlaster.org] On Behalf Of Marcel Ruff
Sent: segunda-feira, 19 de Dezembro de 2005 16:09
To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] session object erased????

Eduardo Catarino wrote:
>
> Hi Marcel and to all XmlBlaster Team,
>
> Thanks again for answering me so quickly. However I think I didn't put

> well my question. The problem is that when starting the applet a new 
> object session (Browser) is created and all the data application is 
> lost. I think is the xmlblater servelet that changes the session 
> object. I read in the requirements that the xmlbaster servelet should 
> be called before any other servelet to prevent this kind of problems.
>
> My question is, what should I do in order to xmlblaster applet do not 
> change the session object when it is initialized?
>
We use in AppletServlet.java this code:

boolean invalidate = getParameter(req, "xmlBlaster/invalidate", false);

Try to replace the '.' with a '/', this should help,

regards
Marcel
>
> Best regards to all,
>
> Eduardo Catarino
>
>
------------------------------------------------------------------------
>
> *From:* owner-xmlblaster at server.xmlBlaster.org 
> [mailto:owner-xmlblaster at server.xmlBlaster.org] *On Behalf Of *Eduardo

> Catarino
> *Sent:* sexta-feira, 16 de Dezembro de 2005 13:43
> *To:* xmlblaster at server.xmlBlaster.org
> *Subject:* [xmlblaster] session object erased????
>
> Hello to all,
>
> I've developed an applet using the xmlblaster lib for applets I'm now 
> facing a problem. When the applet is integrated in the real 
> environment that uses the session object to store application data the

> applet seems to create a new session object and erases all the data 
> that was previously stored. I have been searching in the requirements 
> and tried to use the following code:
>
> session.putValue("xmlBlaster.invalidate", "false");
>
> session.putValue("xmlBlaster.loginName", "eduardo");
>
> session.putValue("xmlBlaster.passwd", "secret");
>
> in order to prevent this from happening. However this didn't solve the

> problem.
>
> Can someone give me a tip how to solve this?
>
> Merry Christmas and a Happy new year for all the xmlblaster team.
>