Bill Fenner wrote:
>   I installed 2.9 over the weekend, and found that one of my most-used
> accelerators broke in my xml2rfc configuration.  Just like the xhtml
> configuration, I have a insert-\n-or-split:
> 
>   <command name="xml2rfc.splitOrInsertNewLine">
>     <macro>
>       <choice>
>         <command name="insertControlChar" parameter="\n"/>
> 
>         <sequence>
>           <command name="selectNode"
>                    parameter="ancestorOrSelf[implicitElement] t"/>
> 
>           <command name="split"/>
>         </sequence>
>       </choice>
>     </macro>
>   </command>
> 
> Unfortunately, in 2.9, this results in the <t> node being selected but
> not split.  The Edit menu's Split option is grayed out, as well.
> 
> In fact, xxe 2.9 seems to have lost significant amounts of
> functionality for the xml2rfc configuration.  The "Insert
> Before"/"Insert"/"Insert After" etc. buttons are all grayed out
> (although command-B, command-I, command-J do work).  None of my
> toolbar buttons, which use a java helper much like xhtml.AddBlock,
> work.  All of these worked as expected in 2.8p1.
> 
> The configuration is available at
> http://rtg.ietf.org/~fenner/ietf/xml2rfc-xxe/ , if needed for
> inspection.  The sample document that you get with "New..." is enough
> to demonstrate these problems.
> 
> Is there anything I can do to get my configuration working again?

Here's what I get when I do "File|New..." and choose "xml2rfc|New 
Internet-Draft"

---
~$ java.lang.NoSuchMethodError: 
com.xmlmind.xmledit.doctype.ElementType.getChildElementFields(Lcom/xmlmind/xmledit/xmlutil/Name;)Lcom/xmlmind/xmledit/doctype/FieldList;
         at 
com.att.research.fenner.xmleditapp.xml2rfc.AddBlock.canContain(AddBlock.java:123)
         at 
com.att.research.fenner.xmleditapp.xml2rfc.AddBlock.prepareCommand(AddBlock.java:73)
         at 
com.xmlmind.xmleditapp.command.MacroCommand$Invocation.doPrepare(MacroCommand.java:195)
         at 
com.xmlmind.xmleditapp.command.MacroCommand$Item.prepare(MacroCommand.java:48)
         at 
com.xmlmind.xmleditapp.command.MacroCommand$Sequence.doPrepare(MacroCommand.java:329)
         at 
com.xmlmind.xmleditapp.command.MacroCommand$Item.prepare(MacroCommand.java:48)
         at 
com.xmlmind.xmleditapp.command.MacroCommand.prepareCommand(MacroCommand.java:1017)
         at 
com.xmlmind.xmleditapp.app.EditAction.updateEnabled(EditAction.java:59)
         at 
com.xmlmind.xmleditapp.app.AppToolBar.editingContextChanged(AppToolBar.java:274)
         at 
com.xmlmind.xmleditapp.app.AppToolBar.editorChanged(AppToolBar.java:162)
         at com.xmlmind.xmleditapp.app.App.editorChanged(App.java:2536)
---

There is no bug here (on your side and on our side).

APIs related to com.xmlmind.xmledit.doctype.DocumentType, ElementType, 
etc, have changed between V2.8p1 and V2.9 (supporting RELAX NG was not 
an easy thing to do!).

You simply need to get latest sources and update your AddBlock like we 
did for xhtml.AddBlock. This should be quick and easy.

Note that in principle,
* All ``plug-ins'' should be recompiled and tested  each time a new 
version of XXE is released.
* The user should not install a plug-in compiled for V2.8 on V2.9.

See http://www.xmlmind.com/xmleditor/plugins.shtml#install
---
However it [Installing in XXE user preferences directory] is not 100% 
safe to do so because XMLmind never checks that, for example, the 
javadoc_format plug-in compiled for XXE V2.7 or V2.8 also runs with 
latest version of XXE. Installing the plug-in within the XXE 
distribution simply ensures that it will be overwritten when a new XXE 
release is installed.
---

95% of the time ``plug-ins'' are compatible between versions. This time, 
you were unlucky. Sorry for that.


Reply via email to