Well, then forget about the applet, at least with Firefox on Linux (the 
most unreliable platform for the applet according to our tests).

We definitely have *no* *problem* *at* *all* with a working environment 
very close to yours:

* Java 1.6.0_14.
* Unbuntu 7.04 or SuSE 10.2.
* Firefox 3.0.11 or *3.5.1*.
* The editor2 applet is used to open an XML document stored on a WebDAV 
location.
* Close the tab containing the applet or quit Firefox.

--> The applet always runs fine[*].
--> The document is always locked on the WebDAV server.
--> The lock is always released no matter how you close the editor2 applet.

My only explanation is that you use a remote, slow, WebDAV server while 
are my tests are conducted a local, quick to respond, WebDAV server. 
That is, in your case, the applet is shutdown while it is in the process 
of unlocking the file.

We'll investigate to see how the Web browser could give a ``grace time'' 
to the Java plug-in before killing it.

---
[*] The interactive authentication with the WebDAV server sometimes 
hangs. This is a known, documented, problem 
(http://www.xmlmind.com/xmleditor/known_problems.html).

I used the -auth option as a workaround:
---
<applet name="XXE" id="XXE" mayscript
   code="com.xmlmind.xmleditapp.applet.Applet"
   width="100%" height="600">
   <param name="jnlp_href" value="xxe.jnlp">
   <param name="appClass"
          value="com.xmlmind.xmleditapp.applet.Editor2App">
   <param name="separate_jvm" value="true">
   <param name="classloader_cache" value="false">
   <param name="argument0" value="-auth">
   <param name="argument1" value="XXXXXXXXXXXXXXXXXXXXXX">
   <param name="argument2" value="http://lupo/davd/javadoc/help.xml";>
   Sorry but XMLmind XML Editor requires the Java<sup>TM</sup> Plug-In
   version 1.6.0_10 and above in order to run.
</applet>
---



Philippe Nobili wrote:
> Hussein Shafie wrote:
> 
>>
>> In our experience, this only happens when the Web browser hosting the
>> applet terminates abruptly (e.g. kill the process, shutdown the PC,
>> etc). Note that technically there is no way to release such locks when
>> the Web browser hosting the applet terminates abruptly.
>>
>> In our experience, if you close normally (e.g. by clicking on the (x)
>> button) the window or tab containing the applet, the locks are properly
>> released.
>>
>> If the locks are not released when you close normally the window or tab
>> containing the applet, please tell us what browser you use and how you
>> quit the applet so we can reproduce the problem here at our offices.
>>   
> 
> Dear Mr. Shafie,
> 
> Sorry for the delay; I confirm that the problem occurs even when when 
> the document
> is closed normally (i.e. by clicking on the close tab button). The 
> procedure is very simple:
> 
> 0) Open Firefox, open a new Tab
> 1) Run the editor2 applet on an XML document (from a WebDAV location)
> 2) Close the tab
> 
> Below are some information about my Java/Firefox environment (RedHat-EL 
> 5.2); I hope this can
> help...
> 
> + JDK 1.6.0 Update 12, 32-bit
> + Firefox 3.0.6, last Java plugin installed
> 
> NB: On Firefox 3.5.x, the XXE applets (whatever flavor) do not run and 
> Firefox crashes.
> 


Reply via email to