<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>This is great, thanks. If I can try summarizing, for "relatively" short snippets of anything, HTML included, using Spring properties will usually be the better choice.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">For larger stanzas or ones that require dynamism, a dedicated .vm included via the proper choice of include/parse is better. Nice that reference is that easy.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Ultimately, many cases come down to preference, and this also offers nice ways to delegate or split management of pages and text.<br>
<br>
Semt frim mt iPone</div>
<div><br>
On Jul 7, 2016, at 17:59, Brent Putman <<a href="mailto:putmanb@georgetown.edu">putmanb@georgetown.edu</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 7/7/16 7:20 PM, Klingenstein, Nate wrote:<br>
</div>
<blockquote cite="mid:BN1PR01MB1847642A46E03618D0A73DFDE3B0@BN1PR01MB184.prod.exchangelabs.com" type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">We’re looking to include a common footer on multiple pages that is a fairly hefty chunk of HTML in e.g. login.vm and error.vm.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Embedded HTML tags in the Spring properties in /messages will render, but I don’t know if limitations exist in length or formatting or whether there are other practical issues to be encountered.</p>
</div>
</blockquote>
<br>
I don't know about length limitations either.... But aside from that, considering the task of just maintaining stuff over time, if it's a ton of text, multiple paragraphs, images, etc, putting that into various message properties probably isn't the nicest way
to go.<br>
<br>
<blockquote cite="mid:BN1PR01MB1847642A46E03618D0A73DFDE3B0@BN1PR01MB184.prod.exchangelabs.com" type="cite">
<div class="WordSection1">
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is that the best approach? Any deployers with enough experience here to recommend better, if not best, practices?</p>
</div>
</blockquote>
<br>
<br>
The Velocity Template Language (VTL) has its own concept of includes, both unparsed (#include) [1] and parsed (#parse) [2]. So that's probably the way to go for large amounts of content.<br>
<br>
As far as the naming and referencing of the included template(s), you should be able to put a foo.vm in the directory defined by the property idp.views (which defaults to idp.home/views), and then reference it in login.vm etc simply unqualified, like "#parse
( "foo.vm" )".<br>
<br>
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://velocity.apache.org/engine/1.7/vtl-reference.html#include-renders-local-files-that-are-not-parsed-by-velocity">
http://velocity.apache.org/engine/1.7/vtl-reference.html#include-renders-local-files-that-are-not-parsed-by-velocity</a><br>
<br>
[2] <a class="moz-txt-link-freetext" href="http://velocity.apache.org/engine/1.7/vtl-reference.html#parse-renders-a-local-template-that-is-parsed-by-velocity">
http://velocity.apache.org/engine/1.7/vtl-reference.html#parse-renders-a-local-template-that-is-parsed-by-velocity</a><br>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>-- </span><br>
<span>To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
users-unsubscribe@shibboleth.net</a></span></div>
</blockquote>
</body>
</html>