You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by bu...@apache.org on 2024/07/15 16:42:21 UTC
svn commit: r1086984 - in /websites/production/santuario/content: ./ cache/
Author: buildbot
Date: Mon Jul 15 16:42:20 2024
New Revision: 1086984
Log:
Production update by buildbot for santuario
Removed:
websites/production/santuario/content/c-source-repository.html
websites/production/santuario/content/c10releasenotes.html
websites/production/santuario/content/c11releasenotes.html
websites/production/santuario/content/c120releasenotes.html
websites/production/santuario/content/c121releasenotes.html
websites/production/santuario/content/c130releasenotes.html
websites/production/santuario/content/c131releasenotes.html
websites/production/santuario/content/c140releasenotes.html
websites/production/santuario/content/c150releasenotes.html
websites/production/santuario/content/c151releasenotes.html
websites/production/santuario/content/ccredits.html
websites/production/santuario/content/cfaq.html
websites/production/santuario/content/cindex.html
websites/production/santuario/content/cinstallation.html
websites/production/santuario/content/cprogramming.html
websites/production/santuario/content/creleasenotes.html
websites/production/santuario/content/ctools.html
Modified:
websites/production/santuario/content/cache/main.pageCache
websites/production/santuario/content/contributing.html
websites/production/santuario/content/download.html
Modified: websites/production/santuario/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/santuario/content/contributing.html
==============================================================================
--- websites/production/santuario/content/contributing.html (original)
+++ websites/production/santuario/content/contributing.html Mon Jul 15 16:42:20 2024
@@ -45,7 +45,7 @@ Apache Santuario -- contributing
<td id="cell-1-1"> </td>
<td id="cell-1-2">
<!-- Banner -->
-<div class="banner" id="banner"><div class="table-wrap"><table class="wrapped confluenceTable" style="width: 100.0%;" border="0" cellpadding="0" cellspacing="0"><colgroup span="1"><col span="1"><col span="1"></colgroup><tbody><tr><td align="left" colspan="1" rowspan="1" class="confluenceTd" style="border: none;"><a shape="rect" class="external-link" title="Apache Santuario" href="http://santuario.apache.org/"> <span style="font-weight: bold;font-size: 170.0%;color: white;">Apache Santuario</span> </a></td><td align="right" colspan="1" rowspan="1" class="confluenceTd" style="border: none;"><div class="content-wrapper"><a shape="rect" class="external-link" href="http://www.apache.org/" title="The Apache Software Foundation"> <span class="confluence-embedded-file-wrapper image-right-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-external-resource image-right" alt="The Apache Software Foundation" width="214" src="https://apache.org/img/asf_logo
.png" data-image-src="https://apache.org/img/asf_logo.png"></span> </a></div></td></tr></tbody></table></div></div>
+<div class="banner" id="banner"><div class="table-wrap"><table class="wrapped confluenceTable" style="width: 100.0%;" border="0" cellpadding="0" cellspacing="0"><colgroup span="1"><col span="1"><col span="1"></colgroup><tbody><tr><td align="left" colspan="1" rowspan="1" class="confluenceTd" style="border: none;"><a shape="rect" class="external-link" href="http://santuario.apache.org/" title="Apache Santuario"> <span style="font-weight: bold;font-size: 170.0%;color: white;">Apache Santuario</span> </a></td><td align="right" colspan="1" rowspan="1" class="confluenceTd" style="border: none;"><div class="content-wrapper"><a shape="rect" class="external-link" href="http://www.apache.org/" title="The Apache Software Foundation"> <span class="confluence-embedded-file-wrapper image-right-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-external-resource image-right" draggable="false" alt="The Apache Software Foundation" width="214" src="https://apach
e.org/img/asf_logo.png" data-image-src="https://apache.org/img/asf_logo.png"></span> </a></div></td></tr></tbody></table></div></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -82,7 +82,7 @@ Apache Santuario -- contributing
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3 id="Navigation-ApacheSantuario">Apache Santuario</h3><ul><li><a shape="rect" href="index.html">Home</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="secadv.html">Security Advisories</a></li><li><a shape="rect" href="faq.html">FAQ</a></li><li><a shape="rect" href="team.html">Team</a></li><li><a shape="rect" href="contributing.html">Contributing</a></li><li><a shape="rect" href="mailing.html">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="https://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html">History</a></li><li><a shape="rect" href="oldnews.html">Old News</a></li></ul><h3 id="Navigation-Java">Java</h3><ul><li><a shape="rect" href="javaindex.h
tml">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="javareleasenotes.html">Release Notes</a></li><li><a shape="rect" href="java-source-repository.html">Source repository</a></li><li><a shape="rect" href="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="streaming-xml-security.html">Streaming API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul><h3 id="Navigation-C++">C++</h3><ul><li><a shape="rect" href="cindex.html">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="creleasenotes.html">Release Notes</a></li><li><a shape="rect" href="c-source-repository.html">Source repository</a></li><li><a shape="rect" href="cinstallation.html">Installation</a></li><li><a shape="rect" href="cfaq.html">FAQ</a></li><li><a shape="rect" href="ctools.html">Tools</a></li><li><a shape="rect" href="cprogramming.html">Progra
mming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul><h3 id="Navigation-ASF">ASF</h3><ul><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/thanks.html">Thanks</a></li></ul><p><a shape="rect" class="external-link" href="https://www.apache.org/events/current-event.html"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-external-resource" height="125" src="https://www.apache.org/events/current-event-125x125.png" data-image-src="https://www.apache.org/events/current-event-125x125.png"></span></a></p></div>
+<div id="navigation"><h3 id="Navigation-ApacheSantuario">Apache Santuario</h3><ul><li><a shape="rect" href="index.html">Home</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="secadv.html">Security Advisories</a></li><li><a shape="rect" href="faq.html">FAQ</a></li><li><a shape="rect" href="team.html">Team</a></li><li><a shape="rect" href="contributing.html">Contributing</a></li><li><a shape="rect" href="mailing.html">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="https://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html">History</a></li><li><a shape="rect" href="oldnews.html">Old News</a></li></ul><h3 id="Navigation-Java">Java</h3><ul><li><a shape="rect" href="javaindex.h
tml">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="javareleasenotes.html">Release Notes</a></li><li><a shape="rect" href="java-source-repository.html">Source repository</a></li><li><a shape="rect" href="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="streaming-xml-security.html">Streaming API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul><h3 id="Navigation-C++">C++</h3><ul><li><a shape="rect" class="unresolved" href="#">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" class="unresolved" href="#">Release Notes</a></li><li><a shape="rect" class="unresolved" href="#">Source repository</a></li><li><a shape="rect" class="unresolved" href="#">Installation</a></li><li><a shape="rect" class="unresolved" href="#">FAQ</a></li><li><a shape="rect" class="unresolved" href="#">Tools</a></li><li><a shape="rect" cl
ass="unresolved" href="#">Programming</a></li><li><a shape="rect" class="unresolved" href="#">Credits</a></li></ul><h3 id="Navigation-ASF">ASF</h3><ul><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/thanks.html">Thanks</a></li></ul><p><a shape="rect" class="external-link" href="https://www.apache.org/events/current-event.html"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-external-resource" draggable="false" height="125" src="https://www.apache.org/events/current-event-125x125.png" data-image-src="https://www.apache.org/eve
nts/current-event-125x125.png"></span></a></p></div>
<!-- NavigationBar -->
</div>
</div>
@@ -92,7 +92,7 @@ Apache Santuario -- contributing
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="contributing-ContributingtoApacheSantuario™">Contributing to Apache Santuario™</h1><h3 id="contributing-Introduction">Introduction</h3><p>The Apache Santuario™ Project is an Open Source volunteer project released under a very open (Apache) license. This means there are many ways to contribute to the project - either with direct participation (coding, documenting, answering questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by resource donations (money, time, publicity, hardware, software, conference presentations, speeches, etc...).</p><p>To begin with, we suggest you to subscribe to the Apache Santuario <a shape="rect" href="mailing.html">mailing list</a> (follow the link for information on how to subscribe and to access the mail list archives). Listen-in for a while, to hear how others make contributions.</p><h3 id="contributing-Sourcerepositories">Source repositories</h3><p>For information on how to ac
cess the source repositories for Apache Santuario, please refer to the following project-specific pages:</p><ul><li><a shape="rect" href="java-source-repository.html">Apache Santuario XML Security for Java</a></li><li><a shape="rect" href="c-source-repository.html">Apache Santuario XML Security for C++</a></li></ul><h3 id="contributing-HelpWantedHere">Help Wanted Here</h3><p>We would also be glad to have extra help in any of the following areas:</p><ul><li>Answering questions on the mailing list - there is often a problem of having too many questioners and not enough experts to respond to all the questions.</li><li>Testing the package (especially its less-frequently-used features) on various configurations and reporting back.</li><li>Debugging - producing reproducible test cases and/or finding causes of bugs. Some known bugs are informally listed on To Do, and some are recorded in Jira (see explanation below).</li><li>Specifying/analysing/designing new features - and beyond. (If you
wish to get involved with this, please join the mailing list, install and try out xml-security and read some of the <a shape="rect" href="mailing.html">mail archives</a>. You should have a strong "fluency" in XML technologies especially XMLDSig and XML Encryption, Java or C++ and a basic understanding of the architecture of this package.</li></ul><h3 id="contributing-ProcedureforRaisingDevelopmentIssues">Procedure for Raising Development Issues</h3><p>There are two methods for discussing development and submitting patches. So that everyone can be productive, it is important to know which method is appropriate for a certain situation and how to go about it without confusion. This section explains when to use the developer <a shape="rect" href="mailing.html">mailing list</a> or the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">bug database</a>.</p><p>Research your topic thoroughly before beginning to discuss a new development issue. Searc
h and browse through the email archives - your issue may have been discussed before. Prepare your post clearly and concisely.</p><p>Most issues will be discovered, resolved, and then patched quickly via the developer mailing list. Larger issues, and ones that are not yet fully understood or are hard to solve, are destined for Jira. Santuario uses Jira for issue tracking. To report a issue, or to submit a patch, go <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">here</a>.</p><p>Experienced developers use Jira directly, as they are very sure when they have found a bug and when not. However, less experienced users should first discuss it on the user or developer mailing list (as appropriate). Impatient people always enter everything into Jira without caring if it is a bug of our package or their own installation/configuration mistake - please do not do this.</p><p>As a rule-of-thumb, discuss an issue on the developers mailing list first to wo
rk out any details. After it is confirmed to be worthwhile, and you are clear about it, then submit the bug description or patch via Bug Tracking.</p><p>Perhaps you do not get any answer on your first reply, so just post it again until you get one. (But please not every hour - allow a few days for the list to deal with it.) Do not be impatient - remember that the whole world is busy, not just you. Bear in mind that other countries will have holidays at different times to your country and that they are in different time zones. You might also consider rewriting your initial posting - perhaps it was not clear enough and the readers eyes glazed over.</p><h3 id="contributing-ContributionNotesandTips">Contribution Notes and Tips</h3><p>This is a collection of tips for contributing to the project in a manner that is productive for all parties.</p><ul><li>Every contribution is worthwhile. Even if the ensuing discussion proves it to be off-beam, then it may jog ideas for other people.</li><l
i>Use sensible and concise email subject headings. Search engines, and humans trying to browse a voluminous list, will respond favourably to a descriptive title.</li><li>Start new threads with a new Subject for new topics, rather than reusing the previous Subject line.</li><li>Keep each topic focused. If some new topic arises then start a new discussion. This leaves the original topic to continue uncluttered.</li><li>Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.</li><li>Prepend your email subject line with a marker when that is appropriate, e.g. <a shape="rect" class="unresolved" href="#">Patch</a>, <a shape="rect" class="unresolved" href="#">Proposal</a>, <a shape="rect" class="unresolved" href="#">RT</a> (Random Thought which quickly blosso
m into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/runv8i/8703/4mhn8a/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)">, <a shape="rect" class="unresolved" href="#">STATUS</a> (development status of a certain facility).</li><li>When making changes to XML documentation, or any XML document for that matter, use a <a shape="rect" class="external-link" href="http://www.oasis-open.org/cover/" rel="nofollow">validating parser</a> (one that is tried and true is <a shape="rect" class="external-link" href="http://openjade.sourceforge.net/" rel="nofollow">OpenSP/onsgmls</a>). This procedure will detect errors without having to go through the whole build docs process to find them. Do not expect Forrest or the build system to detect the validation errors for you - they can do it, but that is not their purpose. (Anyway, nsgmls validation error messages are more informative.)</li><li>Remember that most people are part
icipating in development on a volunteer basis and in their "spare time". These enthusiasts will attempt to respond to issues. It may take a little while to get your answers.</li><li>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.</li><li>Try to at least offer a partial solution and not just a problem statement.</li><li>Take the time to clearly explain your issue and write a concise email message. Less confusion facilitates fast and complete resolution.</li><li>Do not bother to send an email reply that simply says "thanks". When the issue is resolved, that is the finish - end of thread. Reduce clutter.</li><li>If an issue starts to get bogged down in list discussion, then it may be appropriate to go into private off-list discussion with a few interested other people. Spare the l
ist from the gory details. Report a summary back to the list to finalise the thread.</li><li>Become familiar with the mailing lists. As you browse and search, you will see the way other people do things. Follow the leading examples.</li></ul></div>
+<div id="ConfluenceContent"><h1 id="contributing-ContributingtoApacheSantuario™">Contributing to Apache Santuario™</h1><h3 id="contributing-Introduction">Introduction</h3><p>The Apache Santuario™ Project is an Open Source volunteer project released under a very open (Apache) license. This means there are many ways to contribute to the project - either with direct participation (coding, documenting, answering questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by resource donations (money, time, publicity, hardware, software, conference presentations, speeches, etc...).</p><p>To begin with, we suggest you to subscribe to the Apache Santuario <a shape="rect" href="mailing.html">mailing list</a> (follow the link for information on how to subscribe and to access the mail list archives). Listen-in for a while, to hear how others make contributions.</p><h3 id="contributing-Sourcerepositories">Source repositories</h3><p>For information on how to ac
cess the source repositories for Apache Santuario, please refer to the following project-specific pages:</p><ul><li><a shape="rect" href="java-source-repository.html">Apache Santuario XML Security for Java</a></li></ul><h3 id="contributing-HelpWantedHere">Help Wanted Here</h3><p>We would also be glad to have extra help in any of the following areas:</p><ul><li>Answering questions on the mailing list - there is often a problem of having too many questioners and not enough experts to respond to all the questions.</li><li>Testing the package (especially its less-frequently-used features) on various configurations and reporting back.</li><li>Debugging - producing reproducible test cases and/or finding causes of bugs. Some known bugs are informally listed on To Do, and some are recorded in Jira (see explanation below).</li><li>Specifying/analysing/designing new features - and beyond. (If you wish to get involved with this, please join the mailing list, install and try out xml-security an
d read some of the <a shape="rect" href="mailing.html">mail archives</a>. You should have a strong "fluency" in XML technologies especially XMLDSig and XML Encryption, Java or C++ and a basic understanding of the architecture of this package.</li></ul><h3 id="contributing-ProcedureforRaisingDevelopmentIssues">Procedure for Raising Development Issues</h3><p>There are two methods for discussing development and submitting patches. So that everyone can be productive, it is important to know which method is appropriate for a certain situation and how to go about it without confusion. This section explains when to use the developer <a shape="rect" href="mailing.html">mailing list</a> or the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">bug database</a>.</p><p>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Prepare your
post clearly and concisely.</p><p>Most issues will be discovered, resolved, and then patched quickly via the developer mailing list. Larger issues, and ones that are not yet fully understood or are hard to solve, are destined for Jira. Santuario uses Jira for issue tracking. To report a issue, or to submit a patch, go <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">here</a>.</p><p>Experienced developers use Jira directly, as they are very sure when they have found a bug and when not. However, less experienced users should first discuss it on the user or developer mailing list (as appropriate). Impatient people always enter everything into Jira without caring if it is a bug of our package or their own installation/configuration mistake - please do not do this.</p><p>As a rule-of-thumb, discuss an issue on the developers mailing list first to work out any details. After it is confirmed to be worthwhile, and you are clear about it, then submi
t the bug description or patch via Bug Tracking.</p><p>Perhaps you do not get any answer on your first reply, so just post it again until you get one. (But please not every hour - allow a few days for the list to deal with it.) Do not be impatient - remember that the whole world is busy, not just you. Bear in mind that other countries will have holidays at different times to your country and that they are in different time zones. You might also consider rewriting your initial posting - perhaps it was not clear enough and the readers eyes glazed over.</p><h3 id="contributing-ContributionNotesandTips">Contribution Notes and Tips</h3><p>This is a collection of tips for contributing to the project in a manner that is productive for all parties.</p><ul><li>Every contribution is worthwhile. Even if the ensuing discussion proves it to be off-beam, then it may jog ideas for other people.</li><li>Use sensible and concise email subject headings. Search engines, and humans trying to browse a v
oluminous list, will respond favourably to a descriptive title.</li><li>Start new threads with a new Subject for new topics, rather than reusing the previous Subject line.</li><li>Keep each topic focused. If some new topic arises then start a new discussion. This leaves the original topic to continue uncluttered.</li><li>Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.</li><li>Prepend your email subject line with a marker when that is appropriate, e.g. <a shape="rect" class="unresolved" href="#">Patch</a>, <a shape="rect" class="unresolved" href="#">Proposal</a>, <a shape="rect" class="unresolved" href="#">RT</a> (Random Thought which quickly blossom into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluen
ce/s/3bdr34/8804/10mvnxf/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)">, <a shape="rect" class="unresolved" href="#">STATUS</a> (development status of a certain facility).</li><li>When making changes to XML documentation, or any XML document for that matter, use a <a shape="rect" class="external-link" href="http://www.oasis-open.org/cover/" rel="nofollow">validating parser</a> (one that is tried and true is <a shape="rect" class="external-link" href="http://openjade.sourceforge.net/" rel="nofollow">OpenSP/onsgmls</a>). This procedure will detect errors without having to go through the whole build docs process to find them. Do not expect Forrest or the build system to detect the validation errors for you - they can do it, but that is not their purpose. (Anyway, nsgmls validation error messages are more informative.)</li><li>Remember that most people are participating in development on a volunteer basis and in their "spare time". These enthusiasts will a
ttempt to respond to issues. It may take a little while to get your answers.</li><li>Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.</li><li>Try to at least offer a partial solution and not just a problem statement.</li><li>Take the time to clearly explain your issue and write a concise email message. Less confusion facilitates fast and complete resolution.</li><li>Do not bother to send an email reply that simply says "thanks". When the issue is resolved, that is the finish - end of thread. Reduce clutter.</li><li>If an issue starts to get bogged down in list discussion, then it may be appropriate to go into private off-list discussion with a few interested other people. Spare the list from the gory details. Report a summary back to the list to finalise the thread.</li><li>Beco
me familiar with the mailing lists. As you browse and search, you will see the way other people do things. Follow the leading examples.</li></ul></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/download.html
==============================================================================
--- websites/production/santuario/content/download.html (original)
+++ websites/production/santuario/content/download.html Mon Jul 15 16:42:20 2024
@@ -62,7 +62,7 @@ Apache Santuario -- download
<td>
<div align="left">
<!-- Breadcrumbs -->
-<a href="index.html">Index</a> > <a href="cindex.html">c_index</a> > <a href="download.html">download</a>
+<a href="index.html">Index</a> > <a href="javaindex.html">java_index</a> > <a href="download.html">download</a>
<!-- Breadcrumbs -->
</div>
</td>
@@ -91,7 +91,7 @@ Apache Santuario -- download
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3 id="Navigation-ApacheSantuario">Apache Santuario</h3><ul><li><a shape="rect" href="index.html">Home</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="secadv.html">Security Advisories</a></li><li><a shape="rect" href="faq.html">FAQ</a></li><li><a shape="rect" href="team.html">Team</a></li><li><a shape="rect" href="contributing.html">Contributing</a></li><li><a shape="rect" href="mailing.html">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="https://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html">History</a></li><li><a shape="rect" href="oldnews.html">Old News</a></li></ul><h3 id="Navigation-Java">Java</h3><ul><li><a shape="rect" href="javaindex.h
tml">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="javareleasenotes.html">Release Notes</a></li><li><a shape="rect" href="java-source-repository.html">Source repository</a></li><li><a shape="rect" href="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="streaming-xml-security.html">Streaming API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul><h3 id="Navigation-C++">C++</h3><ul><li><a shape="rect" href="cindex.html">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="creleasenotes.html">Release Notes</a></li><li><a shape="rect" href="c-source-repository.html">Source repository</a></li><li><a shape="rect" href="cinstallation.html">Installation</a></li><li><a shape="rect" href="cfaq.html">FAQ</a></li><li><a shape="rect" href="ctools.html">Tools</a></li><li><a shape="rect" href="cprogramming.html">Progra
mming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul><h3 id="Navigation-ASF">ASF</h3><ul><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/thanks.html">Thanks</a></li></ul><p><a shape="rect" class="external-link" href="https://www.apache.org/events/current-event.html"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-external-resource" draggable="false" height="125" src="https://www.apache.org/events/current-event-125x125.png" data-image-src="https://www.apache.org/events/current-event-125x125.png"></span><
/a></p></div>
+<div id="navigation"><h3 id="Navigation-ApacheSantuario">Apache Santuario</h3><ul><li><a shape="rect" href="index.html">Home</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="secadv.html">Security Advisories</a></li><li><a shape="rect" href="faq.html">FAQ</a></li><li><a shape="rect" href="team.html">Team</a></li><li><a shape="rect" href="contributing.html">Contributing</a></li><li><a shape="rect" href="mailing.html">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="https://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html">History</a></li><li><a shape="rect" href="oldnews.html">Old News</a></li></ul><h3 id="Navigation-Java">Java</h3><ul><li><a shape="rect" href="javaindex.h
tml">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" href="javareleasenotes.html">Release Notes</a></li><li><a shape="rect" href="java-source-repository.html">Source repository</a></li><li><a shape="rect" href="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="streaming-xml-security.html">Streaming API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul><h3 id="Navigation-C++">C++</h3><ul><li><a shape="rect" class="unresolved" href="#">Index</a></li><li><a shape="rect" href="download.html">Download</a></li><li><a shape="rect" class="unresolved" href="#">Release Notes</a></li><li><a shape="rect" class="unresolved" href="#">Source repository</a></li><li><a shape="rect" class="unresolved" href="#">Installation</a></li><li><a shape="rect" class="unresolved" href="#">FAQ</a></li><li><a shape="rect" class="unresolved" href="#">Tools</a></li><li><a shape="rect" cl
ass="unresolved" href="#">Programming</a></li><li><a shape="rect" class="unresolved" href="#">Credits</a></li></ul><h3 id="Navigation-ASF">ASF</h3><ul><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/foundation/thanks.html">Thanks</a></li></ul><p><a shape="rect" class="external-link" href="https://www.apache.org/events/current-event.html"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-external-resource" draggable="false" height="125" src="https://www.apache.org/events/current-event-125x125.png" data-image-src="https://www.apache.org/eve
nts/current-event-125x125.png"></span></a></p></div>
<!-- NavigationBar -->
</div>
</div>
@@ -101,7 +101,7 @@ Apache Santuario -- download
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>After discussion with the Santuario PMC, it has been decided to address the long term lack of support for the C++ library by formally retiring the code here at Apache. The Java code of course remains well supported and will continue to be developed.</p><p>As of now, the C++ code is frozen here. The current sole maintainer will be transferring the source code to the Shibboleth Project and it will be maintained by that team for some period of time because it is a dependency of that software, but it will not be supported for any third-party use. It is estimated that the code will be fully retired some time before 2030. The code will be publically hosted and accessible after the transition, and the license is not changing.</p><p>Once th
e code transition occurs, which may not be for some time yet, we will update more of the site as is appropriate to reflect the transition. In the event a significant issue arises with the library prior to the transition, we will endeavor to address it here.</p></div></div><h1 id="download-ObtaintheApacheSantuario™distribution">Obtain the Apache Santuario™ distribution</h1><p>The <strong>Apache Santuario™</strong> project is aimed at providing implementation of the primary security standards for XML. Two libraries are currently available.</p><ul><li>Apache XML Security for Java - This library includes a mature Digital Signature and Encryption implementation. It also includes the standard JSR 105 (Java XML Digital Signature) API. Applications can use the standard JSR 105 API or the Apache Santuario API to create and validate XML Signatures.</li><li>Apache XML Security for C++ - This library includes a mature Digital Signature and Encryption implementation using a pro
prietary C++ API on top of the Xerces-C XML Parser's DOM API. It includes a pluggable cryptographic layer, but support for alternatives to OpenSSL are less complete and less mature.</li></ul><h3 id="download-Howtodownload">How to download</h3><p>Use the links below to download a distribution of Apache Santuario from one of our mirrors. It is good practice to verify the integrity of the distribution files. Apache Santuario releases are available under the <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> - see the LICENSE.txt and NOTICE.txt files contained in each release artifact.</p><h3 id="download-Currentofficialrelease(closestmirrorsiteselectedautomatically)">Current official release (closest mirror site selected automatically)</h3><ul><li>The current stable Java release is Apache XML Security for Java 4.0.2: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/4_0_2/xmls
ec-4.0.2-source-release.zip">xmlsec-4.0.2-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/4_0_2/xmlsec-4.0.2-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/4_0_2/xmlsec-4.0.2-source-release.zip.sha512">SHA-512</a>)</li><li>The current stable Java release is Apache XML Security for Java 3.0.4: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/3_0_4/xmlsec-3.0.4-source-release.zip">xmlsec-3.0.4-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/3_0_4/xmlsec-3.0.4-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/3_0_4/xmlsec-3.0.4-source-release.zip.sha512">SHA-512</a>)</li><li>The current stable Java release is Apache XML Security for Java 2.3.
4: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/2_3_4/xmlsec-2.3.4-source-release.zip">xmlsec-2.3.4-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_3_4/xmlsec-2.3.4-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_3_4/xmlsec-2.3.4-source-release.zip.sha512">SHA-512</a>)</li><li>The older stable Java release is Apache XML Security for Java 2.2.6: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/2_2_6/xmlsec-2.2.6-source-release.zip">xmlsec-2.2.6-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_2_6/xmlsec-2.2.6-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_2_6/xmlsec-2.2.6-source-releas
e.zip.sha512">SHA-512</a>)</li><li>The current C++ release is Apache XML Security for C++ 2.0.4:<br clear="none"><ul><li><a shape="rect" class="external-link" href="https://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-2.0.4.tar.gz">xml-security-c-2.0.4.tar.gz</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-2.0.4.tar.bz2">xml-security-c-2.0.4.tar.bz2</a></li><li><a shape="rect" class="external-link" href="https://www.apache.org/dyn/closer.lua/santuario/c-library/xml-security-c-2.0.4.zip">xml-security-c-2.0.4.zip</a></li><li>For signatures and checksums for these artifacts, please refer to <a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/c-library/">https://downloads.apache.org/santuario/c-library/</a></li></ul></li></ul><h3 id="download-Archiveofoldreleases">Archive of old releases</h3><p>Older releases are available in the <a shape="rect" class="exte
rnal-link" href="http://archive.apache.org/dist/santuario/">archive</a>.</p><h3 id="download-Verifyreleases">Verify releases</h3><p>It is essential that you verify the integrity of the downloaded files using the PGP signatures. Digest verification ensures the file was not corrupted or tampered with but provides no real verification of authenticity. PGP verification ensures that the file is authentic. In practice, PGP verification is <strong>much</strong> more important and makes checksum verification redundant.</p><h3 id="download-PGPSignature">PGP Signature</h3><p>The PGP signatures can be verified using <a shape="rect" class="external-link" href="http://www.pgpi.org/" rel="nofollow">PGP</a> or <a shape="rect" class="external-link" href="http://www.gnupg.org/" rel="nofollow">GPG</a>. First download the Apache Santuario <a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/KEYS">KEYS</a> as well as the *.asc signature file for the particular distribution
. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div id="ConfluenceContent"><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you're looking for the C++ library, it has been officially retired due to lack of committers. See this <a shape="rect" class="external-link" href="https://shibboleth.atlassian.net/wiki/spaces/DEV/pages/3726671873/Santuario" rel="nofollow">external link</a> for details.</p></div></div><h1 id="download-ObtaintheApacheSantuario™distribution">Obtain the Apache Santuario™ distribution</h1><p>The <strong>Apache Santuario™</strong> project is aimed at providing implementation of the primary security standards for XML.</p><p>Apache XML Security for Java - This library includes a mature Digital Signature and Encryption implementation. It also includes the standard JSR 105 (Java XML Digital Signature) API. Applications ca
n use the standard JSR 105 API or the Apache Santuario API to create and validate XML Signatures.</p><h3 id="download-todownload">to download</h3><p>Use the links below to download a distribution of Apache Santuario from one of our mirrors. It is good practice to verify the integrity of the distribution files. Apache Santuario releases are available under the <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> - see the LICENSE.txt and NOTICE.txt files contained in each release artifact.</p><h3 id="download-Currentofficialrelease(closestmirrorsiteselectedautomatically)">Current official release (closest mirror site selected automatically)</h3><ul><li>The current stable Java release is Apache XML Security for Java 4.0.2: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/4_0_2/xmlsec-4.0.2-source-release.zip">xmlsec-4.0.2-source-release.zip</a> (<a shape="rect" class="external
-link" href="https://downloads.apache.org/santuario/java-library/4_0_2/xmlsec-4.0.2-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/4_0_2/xmlsec-4.0.2-source-release.zip.sha512">SHA-512</a>)</li><li>The current stable Java release is Apache XML Security for Java 3.0.4: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/3_0_4/xmlsec-3.0.4-source-release.zip">xmlsec-3.0.4-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/3_0_4/xmlsec-3.0.4-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/3_0_4/xmlsec-3.0.4-source-release.zip.sha512">SHA-512</a>)</li><li>The current stable Java release is Apache XML Security for Java 2.3.4: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/2_
3_4/xmlsec-2.3.4-source-release.zip">xmlsec-2.3.4-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_3_4/xmlsec-2.3.4-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_3_4/xmlsec-2.3.4-source-release.zip.sha512">SHA-512</a>)</li><li>The older stable Java release is Apache XML Security for Java 2.2.6: <a shape="rect" class="external-link" href="https://dlcdn.apache.org/santuario/java-library/2_2_6/xmlsec-2.2.6-source-release.zip">xmlsec-2.2.6-source-release.zip</a> (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_2_6/xmlsec-2.2.6-source-release.zip.asc">PGP</a>) (<a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/java-library/2_2_6/xmlsec-2.2.6-source-release.zip.sha512">SHA-512</a>)</li></ul><h3 id="download-Archiveofoldreleases">Archive of old release
s</h3><p>Older releases are available in the <a shape="rect" class="external-link" href="http://archive.apache.org/dist/santuario/">archive</a>.</p><h3 id="download-Verifyreleases">Verify releases</h3><p>It is essential that you verify the integrity of the downloaded files using the PGP signatures. Digest verification ensures the file was not corrupted or tampered with but provides no real verification of authenticity. PGP verification ensures that the file is authentic. In practice, PGP verification is <strong>much</strong> more important and makes checksum verification redundant.</p><h3 id="download-PGPSignature">PGP Signature</h3><p>The PGP signatures can be verified using <a shape="rect" class="external-link" href="http://www.pgpi.org/" rel="nofollow">PGP</a> or <a shape="rect" class="external-link" href="http://www.gnupg.org/" rel="nofollow">GPG</a>. First download the Apache Santuario <a shape="rect" class="external-link" href="https://downloads.apache.org/santuario/KEYS">KEYS
</a> as well as the *.asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default">% pgpk -a KEYS
% pgpv xml-security-bin-1_4_4.zip.asc
or