On 03/18/2011 01:31 PM, Manuel Collado wrote:
> Please confirm if the following assumption is really the intended XXE
> behavior:
>
> 1- There two different configurations A and B with a duplicate command
> name X
> 2- XXE is started and both configuration are loaded
>
> 3- Open a document bound to configuration A
> 4- Invoking command X executes X from configuration A - OK
>
> 5- Open a document bound to configuration B
> 6- Reselect the document A
> 7- Invoking command X executes X from configuration B - WRONG
>
> (disabling the schema cache doesn't help, and the order A,B or B,A is
> irrelevant)
>
>
> In brief, is it really necessary to invent always different names for
> commands in different configurations that may eventually be used at the
> same time?
Yes, you should always use globally unique command names in your custom
configurations.
Here at XMLmind, we do this by adding a short "XXX." prefix to the
actual name of the command. Doing the same in your custom configurations
is strongly recommended.
Actual examples:
---
<command name="dita.editIndexTerm">
<class>com.xmlmind.xmleditext.dita.EditIndexTerm</class>
</command>
<command name="docb.editIndexTerm">
<class>com.xmlmind.xmleditext.docbook.EditIndexTerm</class>
</command>
<command name="db5.editIndexTerm">
<class>com.xmlmind.xmleditext.docbook.EditIndexTerm</class>
</command>
---
Of course, in the above examples, all the commands serve the same
purpose, but have different implementations (or db5.editIndexTerm, the
DocBook 5 instance will have a slightly different behavior from
docb.editIndexTerm, the DocBook 4 instance).
> I.e., if sample documents for both configurations are opened
> in the same session.
>
> If what I describe is a possible bug,
No, it's not a bug in XXE.
> I could do further tests and
> eventually prepare a simple test case.
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
