Saxon » SaxonJS

X-He-Spam-Score: -2.2

Return-Path: <gary.cornelius@rapport.net>

Delivered-To: dropbox@plan.io

Received: from m.launch.gmbh ([127.0.0.1])

by m.launch.gmbh with LMTP id yNGgFY1PcWGCJwAAJzdhvw

for <dropbox@plan.io>; Thu, 21 Oct 2021 13:31:25 +0200

X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on m.launch.gmbh

X-Spam-Level:

X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,

DKIM_VALID,DKIM_VALID_AU,DMARC_PASS,HTML_MESSAGE,SPF_HELO_NONE,

SPF_PASS autolearn=ham autolearn_force=no version=3.4.2

X-Spam-Report:

* -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%

* [score: 0.0000]

* -0.1 DMARC_PASS DMARC check passed

* -0.1 SPF_PASS SPF check passed

* 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record

* 0.0 HTML_MESSAGE BODY: HTML included in message

* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily

* valid

* -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from

* author's domain

* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature

X-Spam-Score: -2.2

Envelope-to: inbox+saxonica+f38e+saxon-js@plan.io

Authentication-Results: m.launch.gmbh; dmarc=pass (p=quarantine dis=none) header.from=rapport.net

Authentication-Results: m.launch.gmbh; spf=pass smtp.mailfrom=gary.cornelius@rapport.net

Authentication-Results: m.launch.gmbh;

dkim=pass (2048-bit key; unprotected) header.d=rapport.net header.i=@rapport.net header.b="VHCM/0me";

dkim-atps=neutral

Received: from mail.rapport.net (mail.rapport.net [18.130.73.62])

(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))

(No client certificate requested)

by m.launch.gmbh (Postfix) with ESMTPS id 1963E86836

for <inbox+saxonica+f38e+saxon-js@plan.io>; Thu, 21 Oct 2021 13:31:25 +0200 (CEST)

Received: from localhost (localhost [127.0.0.1])

by mail.rapport.net (Postfix) with ESMTP id B369523900FA

for <inbox+saxonica+f38e+saxon-js@plan.io>; Thu, 21 Oct 2021 11:31:24 +0000 (UTC)

Received: from mail.rapport.net ([127.0.0.1])

by localhost (rapport.net [127.0.0.1]) (amavisd-new, port 10032)

with ESMTP id JZl5r94Mu41N for <inbox+saxonica+f38e+saxon-js@plan.io>;

Thu, 21 Oct 2021 11:31:24 +0000 (UTC)

Received: from localhost (localhost [127.0.0.1])

by mail.rapport.net (Postfix) with ESMTP id 3161823900FB

for <inbox+saxonica+f38e+saxon-js@plan.io>; Thu, 21 Oct 2021 11:31:24 +0000 (UTC)

DKIM-Filter: OpenDKIM Filter v2.10.3 mail.rapport.net 3161823900FB

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rapport.net;

s=00110110-CA95-11EA-A47A-6BAF5C33E0C3; t=1634815884;

bh=WLkxY/AcYcW94hyZDSXi9412CkK1sWDNMnViIKfIe8c=;

h=Date:From:To:Message-ID:MIME-Version;

b=VHCM/0meiG1c48qxowSQX2jQje1DUoCDTCkn7Y+ZkDcMy1EFE9I4vkFmSXJoxDFf6

QQbFRVDRZXvNYmmVPIKzWPkfp/jwIiMfEqz1+j6nX3fwyZVD0eVndYEdA/3UgflTUY

kN+fuWCJYupX0Y13UMFPrEjkj550zvuDpUQA01hmcTL/eHqC0apiGw2dadtDGsbt8A

q4h4vZSrVQnbhZiqajFG9MPB5KBQilyevoQRZGF3Jgrk8vyqpBGgr5MkiZwcr4CK7W

wKstV2R42RG9DO5OG0pUOVAqv3VNaGvZOZEsMseacMFoGcN1GWsDj/WMoPzcQ5zwCY

BzTN8NzjH/stA==

X-Virus-Scanned: amavisd-new at rapport.net

Received: from mail.rapport.net ([127.0.0.1])

by localhost (rapport.net [127.0.0.1]) (amavisd-new, port 10026)

with ESMTP id lYuSZHmMQB87 for <inbox+saxonica+f38e+saxon-js@plan.io>;

Thu, 21 Oct 2021 11:31:24 +0000 (UTC)

Received: from rapport.net (rapport.net [172.31.16.136])

by mail.rapport.net (Postfix) with ESMTP id E634E23900FA

for <inbox+saxonica+f38e+saxon-js@plan.io>; Thu, 21 Oct 2021 11:31:23 +0000 (UTC)

Date: Thu, 21 Oct 2021 11:31:23 +0000 (UTC)

From: Gary Cornelius <gary.cornelius@rapport.net>

Reply-To: Gary Cornelius <gary@cornelius.me>

To: inbox+saxonica+f38e+saxon-js <inbox+saxonica+f38e+saxon-js@plan.io>

Message-ID: <118151308.865.1634815883702.JavaMail.zimbra@rapport.net>

Subject: [#5136][f7dd4b]

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="=_3f524656-461e-4b2c-b8b7-e2006ebb7a37"

X-Originating-IP: [172.31.16.136]

X-Mailer: Zimbra 9.0.0_GA_3990 (ZimbraXWebClient - GC94 (Windows)/9.0.0_GA_3990)

Thread-Index: a4m4vGHJeKR4GUBIZ5OgG+QafcaHLA==

Thread-Topic: [f7dd4b]

--=_3f524656-461e-4b2c-b8b7-e2006ebb7a37

Content-Type: text/plain; charset=utf-8

Content-Transfer-Encoding: quoted-printable

Amazing, this works, you nailed it. So many thanks! 'body': string($bo=

dy)

This would also explain how I thought it had worked previously too so I r=

eally appreciate not having to go back and test with all previous saxon-js =

versions. I guess I sort of understood this was a completely separate resul=

t document being created by XSLT but moving into this context inside a map =

gets a bit outside my comfort zone and it sort of feels to like I am loosin=

g all the top level xsl controls of documents I know like with xsl:output. =

xsl:document, xsl:result-document. Also when I googled for saxon-js POST ma=

p examples I get lots of very complex examples from Martin-honnen which I f=

ollowed and all had some serializing or document node creating and were als=

o encoding my database queries in wrong way similar to my code too.=C2=A0 =

=20

--=_3f524656-461e-4b2c-b8b7-e2006ebb7a37

Content-Type: text/html; charset=utf-8

Content-Transfer-Encoding: 7bit

<html><body><div style="font-size: 12pt; font-family: arial, helvetica, sans-serif; color: rgb(0, 0, 0);"><div style="font-size: 12pt; font-family: 'arial' , 'helvetica' , sans-serif; color: #000000;">

<div style="font-size: 12pt; font-family: 'arial' , 'helvetica' , sans-serif; color: #000000;">

<div style="font-size: 12pt; font-family: 'arial' , 'helvetica' , sans-serif; color: #000000;">

<div style="color: #000000; font-family: arial, helvetica, sans-serif; font-size: 12pt;">Amazing, this works, you nailed it. So many thanks!</div>

<div id="signature-content-a7078f86-8dbc-4af1-a47b-4fb8b07984aa">

<div style="color: #000000; font-family: arial, helvetica, sans-serif; font-size: 12pt;">

<pre><code>'body': string($body)<br><br></code></pre>

</div>

<span style="font-size: 12pt;">This would also explain how I thought it had worked previously too so I really appreciate not having to go back and test with all previous saxon-js versions. I guess I sort of understood this was a completely separate result document being created by XSLT but moving into this context inside a map gets a bit outside my comfort zone and it sort of feels to like I am loosing all the top level xsl controls of documents I know like with xsl:output. xsl:document, xsl:result-document. Also when I googled for saxon-js POST map examples I get lots of very complex examples from Martin-honnen which I followed and all had some </span>serializing<span style="font-size: 12pt;"> or document node creating and were also encoding my database </span>queries<span style="font-size: 12pt;"> in wrong way similar to my code too.&nbsp;</span></div>

</div>

</div>

</div></div></body></html>

--=_3f524656-461e-4b2c-b8b7-e2006ebb7a37--