On 10/17/2017 04:49 PM, Fabián Mandelbaum wrote:
This is our custom_docbook5.xslt:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:h="http://www.w3.org/1999/xhtml"
xmlns:m="http://www.w3.org/1998/Math/MathML"
xmlns="http://docbook.org/ns/docbook" exclude-result-prefixes="h m">
<xsl:import href="w2x:xslt/docbook5.xslt" />
<!-- Include XSLT that will surround special phrases in <phrase>
tags -->
<xsl:include href="wordmangling2.xslt" />
<!-- Include XSLT that will "massage" the resulting XML even further -->
<xsl:include
href="https://fuentes.calenco.com:9003/workspaces/POC/content/soc-gen-import-massaging.xsl"
/>
<!-- -->
<!-- Preserve text styles. Here we treat titles (2col, paysage,
etc.) -->
<xsl:template match="h:div[starts-with(@class,
'role-section')]/h:h1[@class] | h:div[starts-with(@class,
'role-section')]/h:h2[@class] | h:div[starts-with(@class,
'role-section')]/h:h3[@class] | h:div[starts-with(@class,
'role-section')]/h:h4[@class] | h:div[starts-with(@class,
'role-section')]/h:h5[@class] | h:div[starts-with(@class,
'role-section')]/h:h6[@class]">
<title>
<xsl:attribute name="role">
<xsl:value-of select="concat('sg-', @class)" />
</xsl:attribute>
<xsl:call-template name="processCommonAttributes" />
<xsl:apply-templates/>
</title>
</xsl:template>
<xsl:template match="h:p[@class]">
<para>
<xsl:attribute name="role">
<xsl:value-of select="concat('sg-', @class)" />
</xsl:attribute>
<xsl:call-template name="processCommonAttributes" />
<xsl:apply-templates/>
</para>
</xsl:template>
</xsl:stylesheet>
That file is stored inside the xslt/ folder of the servlet and the
servlet code has been modified to use the proper authentication
mechanisms to be able to connect to https://fuentes...
The wordmangling2.xslt (also stored inside the xslt/ folder of the
servlet) is also requesting a file in https://fuentes... by means of a
parameter definition which loads the file:
<xsl:param name="replacementsFileURI"
select="'https://fuentes.calenco.com:9003/workspaces/POC/content/replacements-SocGen.xml'"
/>
Now, on the server (https://fuentes....) log I do see the successful
(HTTP 200) request for the replacements-SocGen.xml file, but I do not
see any request (successful or otherwise) for the
soc-gen-import-massaging.xsl file.
What am I missing? Does w2x customization support including, or
importing, an XSL file from a remote system? Is there an option to pass
w2x (servlet) to enable this behavior?
No, there is definitely no such option.
I don't think that your issue is related to our product. I would say
that it's a Servlet or a Java problem or (unlikely) a Saxon 6.5.5
problem. For example:
- If https://fuentes.calenco.com:9003/ has a self-signed certificate, I
don't see how this could work.
- If accessing https://fuentes.calenco.com:9003/ requires some user
credentials (which seems to be the case), may be there is a problem with
*your* implementation of user authentication in the context of a Servlet.
Please note that the product you have purchased "XMLmind Word To XML
Server License" just give you the legal rights to deploy XMLmind Word To
XML on a single server, but does not provide you with any technical
means or any technical help to do it.
The sample “Word To XML” Servlet is well...just a *sample* servlet. Its
full source code is included, so you are really on your own to achieve
what you want with it.
Of course, if you find a blatant bug or limitation *by* *reading* *its*
*source* *code* (which is short: 365 lines), we'll be happy to resolve
the problem ASAP.
Really sorry not to be more helpful.
--
XMLmind Word To XML Support List
w2x-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/w2x-support