Hello David,
Unfortunately I cannot reproduce the problem you described. When I
import a new file in the master file, this is validated automatically in
the master file context.
I tested with Oxygen XML Editor 22.1, build 2020100710.
The master files graph is updated automatically when you save a file
from the editing area. Therefore, when you add the "xsl:import"
instruction in the master file, the module should be added in the graph
and validated correctly.
If a module is not detected correctly, you can also try to refresh the
Master Files folder from the Project view. For this you can use the
"Refresh" action from the Project view contextual menu.
Best Regards,
Octavian
--
Octavian Nadolu
<oXygen/> XML Editor
http://www.oxygenxml.com
On 08.11.2020 19:57, David Birnbaum wrote:
Dear oxygen-user list,
I've configured an XSLT transformation using master-file support, where
there is one master XSLT file (a.xsl), which imports (with <xsl:import>)
a file of functions (lib.xsl) and a set of files that contain only
templates (b.xsl, c.xsl, etc.). The imported template files use
functions defined in lib.xsl but don't import those functions directly.
Since the imported template files are never run on their own, and used
only by being imported into a.xsl, the functions from lib.xsl are
available to the imported template files when they are used, and the
transformation runs successfully.
I have specified a.xsl as a master file, and <oXygen/> validates it
successfully. For the most part (the four scariest words in debugging!)
the imported template files do not raise real-time validation errors
about unknown functions, even though they would have access to the
functions they use only because both they and those functions are
imported into a.xsl together. So far, so good.
My issue is that when I create a new template file to be imported into
a.xsl, <oXygen/> doesn't seem to know that it should be validated with
the understanding that it is being imported into a.xsl, which is also
importing lib.xsl. This means that when I create a new template file,
<oXygen/> raises real-time validation errors about unknown functions,
even though it does not raise those errors for other imported template
files that use similar function calls.
At some point <oXygen/> seems to learn that the new imported template
files should be checked with access to master-file information, that is,
that they will have access to the functions in question when they are
used, at which point the imported template files no longer raise
validation errors when I have them open in <oXygen/>. I have not,
however, been able to identify what exactly enables <oXygen/> to learn
this about new imported files as I am creating them, or how to notify
<oXygen/> explicitly about them when I first begin to author them. Can
someone please advise?
Thanks,
David
djbp...@gmail.com <mailto:djbp...@gmail.com>
_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
