On 11/09/2011 11:55 AM, Benoit Maisonny wrote: > We've implemented this in our document management system: a button in > the Web application allows to edit an XML file. In fact, it points to a > JNLP file, which instructs XXE to download the XML file from our WebDAV > server. This way, XXE knows where to save the document.
Good idea. > The only issue > we find is the fact that editors must login twice: in the browser to > access the document mgmt system and in XXE to access the WebDAV server. > > In fact, when XMLMind released the applet version of XXE, I was hoping > that it would solve this dual login, but unfortunately this is not the > case (because, to give the user's password to the applet, the server > application needs to know that password, which is not the case when > using container-based authentication). The Editor2 or XXE applets have this problem because these applet variants will directly save the file to a WebDAV backend. The Editor1 applet, which is more or less an XML area with no save capabilities of its own. should not have this problem. May be you should give it a try. More information in: http://www.xmlmind.com/xmleditor/xxe_applet.html JavaScript API: http://www.xmlmind.com/xmleditor/_distrib/doc/configure/integrating_the_applet.html#applet_scripting > > Note, when XXE is started via Java Web Start, you cannot have a tight > Javascript-based integration, since XXE is started as a separate > application from the browser. Thank you for this interesting information. -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
