Thanks, indeed it looks to work better now, going on with tests :-)
On 22/03/2011 15:27, Hussein Shafie wrote: > On 03/22/2011 02:47 PM, Camille Bégnis wrote: >> OK, so we have been further scrutinizing logs, and this is what we >> noticed: at XXE startup, all jars are loaded in the form .jar.pack.gz >> >> So we get requests like this on the server side: >> >> INFO: 2011-03-18 17:32:40 81.56.151.39 [email protected] >> 88.191.98.16 9001 GET >> /workspaces/Baudouin/xxe/applet/xxe_addon.jar.pack.gz - 200 - >> 0 3 http://demo.calenco.com:9001 Mozilla/4.0 (Linux >> 2.6.33.7-desktop-2mnb) Java/1.6.0_24 - >> >> >> But at some point in time, some jars are reloaded: >> >> INFO: 2011-03-18 17:49:55 81.56.151.39 [email protected] >> 88.191.98.16 9001 GET >> /workspaces/Baudouin/xxe/applet/xxe_addon.jar - 404 439 0 >> 4 http://demo.calenco.com:9001 Mozilla/4.0 (Linux >> 2.6.33.7-desktop-2mnb) Java/1.6.0_24 - >> > Strange, given the fact that all *.jar.pack.gz have already been loaded > eagerly. > > > >> And because we don't serve them unpacked, XXE fails. >> >> I attach the JNLP to the message, what do you recommend? >> > We have found the class loader of the Java plug-in to ``behave very > strangely'', to the point of making the XXE applet unreliable. > > For now, all the problems happened at the applet startup time. See > http://www.xmlmind.com/xmleditor/known_problems.html#applet_problems > What you describe is new for us and makes the situation even worse than > what we imagined. > > The only workaround we have found so far is not use any of the following > deploywebstart options: -jsapplet, -indexjars, -packjars. That is, keep > it as simple as possible. That's what we do for our own demo > (http://www.xmlmind.com/xmleditor/xxe_applet.html) > > More information about the deploywebstart command-line tool: > http://www.xmlmind.com/xmleditor/_distrib/doc/configure/deploy_webstart_tool.html > > If, even after doing that, you still have this kind of problems, then we > recommend giving up the idea of deploying XXE as an applet and to > consider deploying it using Java Web Start. The class loader of Java Web > Start seems to be much less bug-ridden than the the class loader of the > Java plug-in.
<<attachment: camille.vcf>>
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
