Following up on your suggestions, I contacted the current maintainer of the XXE 
plugin, and he and I spent an hour on the phone and in jabber investigating 
this. In the end, he had me rename xmlmimd.app and the support directory 
~/Library/Application\ Support/XMLmind, and reinstall the application from 
scratch. That in fact corrected the issue. I have no idea what became corrupted 
or how (I can, however, tell you that the plug-in was not corrupted), but I can 
tell you that re-installing the application with the plug-in results in it 
correctly working.

To answer your several questions, yes, I had re-downloaded Jabber 1.8 version 
201 from the Oracle site, I was in fact running XMLMind 8.3, and I see no 
evidence that the plug-in was faulty given that it is unchanged from what it 
was previously, and it now works. Whatever the issue was, it was fixed by 
re-installing the application and the plug-in.

> On Apr 8, 2019, at 12:49 AM, Hussein Shafie <huss...@xmlmind.com> wrote:
> 
> On 04/08/2019 02:09 AM, Fred Baker wrote:
>> I have been using XMLMind for ages, with the XXE plugin used for RFC and 
>> Internet Draft development. Suddenly (with in a month or two) it has 
>> developed a problem that it hasn't had before: it won't open a .xml file 
>> that it would previously open. I know the information is getting to the 
>> application because if I tell it (via the XML2RFC "edit in" tab) to open the 
>> file it can't open using a text editor such as TextWrangler, it opens it. 
>> Therefore, the file exists and is generally usable. But the XML Editor won't 
>> open it, and gives me no diagnostic to say why.
>> 
> 
> Are you sure the plugin you are using (which is not our work and which we 
> have never tested) has been updated in order to make it compatible with 
> XMLmind XML Editor v8.3?
> 
> 
> 
> 
>> Things I have tried:
>>  - open an existing file or template (the difference being that templates 
>> are read-only)
>>  - duplicate such a file and open that
>>  - create a new file using an existing template
> 
> 
> XMLmind XML Editor v8.3 has been thoroughly tested on latest (non-beta) macOS 
> Mojave. It's almost certainly an issue caused by an outdated plugin.
> 
> 
> 
> 
>> 
>> Any clues?
>> 
> 
> In principle you should contact the authors of the plugin to get some answers.
> 
> However what follows is the generic answer to learn more about what happens:
> 
> 1) Not 100% sure that this will work but it's worth giving it a try.
> 
> Let's suppose you have installed 
> http://www.xmlmind.com/xmleditor/_download/xxe-perso-8_3_0.dmg
> 
> Please open a terminal and cd to XMLmind.app/Contents/MacOS/.
> 
> Start XXE using the shell-script called "xxe-mac.sh"
> 
> Opening a RFC in XXE will almost certainly print a lot of errors messages 
> (Java "stack traces") on the terminal. Please send us a copy of all these 
> error messages.
> 
> OR
> 
> 2) Please download and unzip the ".zip" distribution of XMLmind XML Editor 
> v8.3,
> 
> http://www.xmlmind.com/xmleditor/_download/xxe-perso-8_3_0.zip
> 
> then please open a terminal and start XXE using XXE_install_dir/bin/xxe.
> 
> This should work provided you have a Java 1.8+ runtime installed on you 
> computer. 
> (https://www.oracle.com/technetwork/java/javase/downloads/index.html#JDK8)
> 
> Opening a RFC in XXE will almost certainly print a lot of errors messages 
> (Java "stack traces") on the terminal. Please send us a copy of all these 
> error messages.

--------------------------------------------------------------------------------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu

Attachment: signature.asc
Description: Message signed with OpenPGP

--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to