|
From: Christoph F. <cf...@fo...> - 2004-10-28 08:36:23
|
Am Donnerstag, den 28.10.2004, 12:36 +1000 schrieb Rinalldo Yasahardja:
> On Wed, 27 Oct 2004, Christoph Froehlich wrote:
>
> > Hi Rinalldo
> >
> > I'm pretty sure that the reason for this is the potential asynchronious
> > behavior of the Preferences implementation.
> >
> > I guess you are still running TMNav-Applet with the -f option? And
> > removed the call to System.exit(int);
> >
> > If so, please try to add a call to sync in TMNav.clearSessionData():
> > After that the try - block should look roughly like this:
> > try {
> > String path = tmnavRootNode.absolutePath();
> > tmnavRootNode.removeNode();
> > tmnavRootNode.sync(); // new call to sync
> > System.out.println("Removed Session Data from path " +
> > ...
>
> using this method causes TMNav to crash even on the first attempt to run
> it (the message is still the same)
>
>
> >
> > If this does not help, try to add the sync call also to
> > TMNav.closeInstance(int), just after the line:
> > session.storeSession();
> >
> > (For the latter case you need to access tmnavRootNode just as in
> > clearSessionData().)
> >
>
>
> using this method still causes TMNav fail to load the second time.
>
>
> > Hope that helps
> > c
> >
>
> any ideas ?
ui. ui.
not really.
What happens,
- if you're running the applet without the -f option?
- if you're removing the line "session.storeSession();" from
TMNav.closeInstance()?
c
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Tm4j-tmnav-dev mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-tmnav-dev
--
Christoph Froehlich <cf...@fo...>
|