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 2013/12/17 21:23:34 UTC
svn commit: r890765 [2/7] - in /websites/production/santuario/content: ./
cache/ secadv.data/
Modified: websites/production/santuario/content/ccredits.html
==============================================================================
--- websites/production/santuario/content/ccredits.html (original)
+++ websites/production/santuario/content/ccredits.html Tue Dec 17 20:23:32 2013
@@ -52,7 +52,7 @@ Apache Santuario -- c_credits
</td><td align="right" colspan="1" nowrap>
<a shape="rect" href="http://www.apache.org/" title="The Apache Software Foundation"><img border="0" src="http://activemq.apache.org/images/asf-logo.png"></a>
</td></tr></table>
-</p></div>
+</p><p></p></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -89,21 +89,20 @@ Apache Santuario -- c_credits
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3><a shape="rect" name="Navigation-ApacheSantuario"></a>Apache Santuario</h3>
-<ul><li><a shape="rect" href="index.html" title="Index">Home</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="secadv.html" title="secadv">Security Advisories</a></li><li><a shape="rect" href="faq.html" title="faq">FAQ</a></li><li><a shape="rect" href="team.html" title="team">Team</a></li><li><a shape="rect" href="contributing.html" title="contributing">Contributing</a></li><li><a shape="rect" href="mailing.html" title="mailing">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html" title="history">History</a></li><li><a shape="rect" href="oldnews.html" title="old_news">Old News</a></li></ul>
+<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="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://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><a shape="rect" name="Navigation-Java"></a>Java</h3>
-<ul><li><a shape="rect" href="javaindex.html" title="java_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="javareleasenotes.html" title="java_release_notes">Release Notes</a></li><li><a shape="rect" href="javafaq.html" title="java_faq">FAQ</a></li><li><a shape="rect" href="javaapi.html" title="java_api">API</a></li><li><a shape="rect" href="javainterop.html" title="java_interop">Interoperability</a></li></ul>
+<h3 id="Navigation-Java">Java</h3>
+<ul><li><a shape="rect" href="javaindex.html">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="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul>
-<h3><a shape="rect" name="Navigation-C"></a>C++</h3>
-<ul><li><a shape="rect" href="cindex.html" title="c_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="creleasenotes.html" title="c_release_notes">Release Notes</a></li><li><a shape="rect" href="cinstallation.html" title="c_installation">Installation</a></li><li><a shape="rect" href="cfaq.html" title="c_faq">FAQ</a></li><li><a shape="rect" href="ctools.html" title="c_tools">Tools</a></li><li><a shape="rect" href="cprogramming.html" title="c_programming">Programming</a></li><li><a shape="rect" href="ccredits.html" title="c_credits">Credits</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="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">Programming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul>
-<h3><a shape="rect" name="Navigation-ASF"></a>ASF</h3>
-<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul>
-</div>
+<h3 id="Navigation-ASF">ASF</h3>
+<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></div>
<!-- NavigationBar -->
</div>
</div>
@@ -113,9 +112,9 @@ Apache Santuario -- c_credits
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1><a shape="rect" name="c_credits-Credits"></a>Credits</h1>
+<div id="ConfluenceContent"><h1 id="c_credits-Credits">Credits</h1>
-<h1><a shape="rect" name="c_credits-SoftwareUsed"></a>Software Used</h1>
+<h1 id="c_credits-SoftwareUsed">Software Used</h1>
<p>The Apache XML Security for C++ package makes heavy use of the <a shape="rect" class="external-link" href="http://xml.apache.org/xalan-c/">Xalan-C</a> and <a shape="rect" class="external-link" href="http://xerces.apache.org/xerces-c/">Xerces-C++</a> libraries from the Apache Software Foundation.</p>
Modified: websites/production/santuario/content/cfaq.html
==============================================================================
--- websites/production/santuario/content/cfaq.html (original)
+++ websites/production/santuario/content/cfaq.html Tue Dec 17 20:23:32 2013
@@ -52,7 +52,7 @@ Apache Santuario -- c_faq
</td><td align="right" colspan="1" nowrap>
<a shape="rect" href="http://www.apache.org/" title="The Apache Software Foundation"><img border="0" src="http://activemq.apache.org/images/asf-logo.png"></a>
</td></tr></table>
-</p></div>
+</p><p></p></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -89,21 +89,20 @@ Apache Santuario -- c_faq
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3><a shape="rect" name="Navigation-ApacheSantuario"></a>Apache Santuario</h3>
-<ul><li><a shape="rect" href="index.html" title="Index">Home</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="secadv.html" title="secadv">Security Advisories</a></li><li><a shape="rect" href="faq.html" title="faq">FAQ</a></li><li><a shape="rect" href="team.html" title="team">Team</a></li><li><a shape="rect" href="contributing.html" title="contributing">Contributing</a></li><li><a shape="rect" href="mailing.html" title="mailing">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html" title="history">History</a></li><li><a shape="rect" href="oldnews.html" title="old_news">Old News</a></li></ul>
+<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="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://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><a shape="rect" name="Navigation-Java"></a>Java</h3>
-<ul><li><a shape="rect" href="javaindex.html" title="java_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="javareleasenotes.html" title="java_release_notes">Release Notes</a></li><li><a shape="rect" href="javafaq.html" title="java_faq">FAQ</a></li><li><a shape="rect" href="javaapi.html" title="java_api">API</a></li><li><a shape="rect" href="javainterop.html" title="java_interop">Interoperability</a></li></ul>
+<h3 id="Navigation-Java">Java</h3>
+<ul><li><a shape="rect" href="javaindex.html">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="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul>
-<h3><a shape="rect" name="Navigation-C"></a>C++</h3>
-<ul><li><a shape="rect" href="cindex.html" title="c_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="creleasenotes.html" title="c_release_notes">Release Notes</a></li><li><a shape="rect" href="cinstallation.html" title="c_installation">Installation</a></li><li><a shape="rect" href="cfaq.html" title="c_faq">FAQ</a></li><li><a shape="rect" href="ctools.html" title="c_tools">Tools</a></li><li><a shape="rect" href="cprogramming.html" title="c_programming">Programming</a></li><li><a shape="rect" href="ccredits.html" title="c_credits">Credits</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="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">Programming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul>
-<h3><a shape="rect" name="Navigation-ASF"></a>ASF</h3>
-<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul>
-</div>
+<h3 id="Navigation-ASF">ASF</h3>
+<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></div>
<!-- NavigationBar -->
</div>
</div>
@@ -113,37 +112,37 @@ Apache Santuario -- c_faq
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1><a shape="rect" name="c_faq-FrequentlyAskedQuestionsApacheXMLSecurityforC"></a>Frequently Asked Questions - Apache XML Security for C++</h1>
+<div id="ConfluenceContent"><h1 id="c_faq-FrequentlyAskedQuestions-ApacheXMLSecurityforC++">Frequently Asked Questions - Apache XML Security for C++</h1>
-<h3><a shape="rect" name="c_faq-1.CompilingandUsingtheLibrary"></a>1. Compiling and Using the Library</h3>
+<h3 id="c_faq-1.CompilingandUsingtheLibrary">1. Compiling and Using the Library</h3>
-<h5><a shape="rect" name="c_faq-1.1.IsOpenSSLrequired%3F"></a>1.1. Is OpenSSL required?</h5>
+<h5 id="c_faq-1.1.IsOpenSSLrequired?">1.1. Is OpenSSL required?</h5>
<p>The main development work for the library is done using OpenSSL, so this is the recommended option. However, Windows Crypto API and NSS interfaces are also now provided.</p>
<p>It is also possible to implement interfaces for other cryptographic libraries and pass them into the xml-security-c library during initialisation (via the XSECPlatformUtils::Initialise() call).</p>
-<h5><a shape="rect" name="c_faq-1.2.DoesthelibraryprovideafullCwrapperforOpenSSL%3F"></a>1.2. Does the library provide a full C++ wrapper for OpenSSL?</h5>
+<h5 id="c_faq-1.2.DoesthelibraryprovideafullC++wrapperforOpenSSL?">1.2. Does the library provide a full C++ wrapper for OpenSSL?</h5>
<p>The C++ crypto interface layer provided for the library provides only the smallest subset of cryptographic functions necessary for the library to make calls to the provided library. Applications will need to work directly with OpenSSL (or other libraries) to read and manipulate encryption keys that should then be wrapped in XSECCrypto* objects and passed into the library.</p>
-<h5><a shape="rect" name="c_faq-1.3.WhatisWinCAPI%3F"></a>1.3. What is WinCAPI?</h5>
+<h5 id="c_faq-1.3.WhatisWinCAPI?">1.3. What is WinCAPI?</h5>
<p>WinCAPI is the developmental interface being built to give users of the library access to the Windows Cryptographic library.</p>
<p>It is not a C API wrapper for the overall library.</p>
-<h5><a shape="rect" name="c_faq-1.4.IsXalanrequired%3F"></a>1.4. Is Xalan required?</h5>
+<h5 id="c_faq-1.4.IsXalanrequired?">1.4. Is Xalan required?</h5>
<p>The library can be compiled without linking to Xalan-c. However doing so will disable support for XPath and XSLT transformations.</p>
<p>To disable Xalan-c support either use --without-xalan when running configure on UNIX, or use the VC++ "without Xalan" settings.</p>
-<h5><a shape="rect" name="c_faq-1.5.AreversionsofXalanpriorto1.6supported%3F"></a>1.5. Are versions of Xalan prior to 1.6 supported?</h5>
+<h5 id="c_faq-1.5.AreversionsofXalanpriorto1.6supported?">1.5. Are versions of Xalan prior to 1.6 supported?</h5>
<p>No. Whilst the functionality required is available in prior versions, the location of include files changed in 1.6. A decision was made in version 1.0.0 of Apache XML Security for C++ to update the source to support these new locations.</p>
-<h5><a shape="rect" name="c_faq-1.6.IsignadocumentandwhenItrytoverifyusingthesamekey%2Citfails"></a>1.6. I sign a document and when I try to verify using the same key, it fails</h5>
+<h5 id="c_faq-1.6.IsignadocumentandwhenItrytoverifyusingthesamekey,itfails">1.6. I sign a document and when I try to verify using the same key, it fails</h5>
<p>After you have created the XMLSignature object, before you sign the document, you must embed the signature element in the owning document (which is returned by the call to DSIGSignature::createBlankSignature(...)) before calling the DSIGSignature::sign() method,</p>
@@ -151,7 +150,7 @@ Apache Santuario -- c_faq
<p>If you have not embedded the signature node in the document, it will not have any parent or ancestor nodes, so it will not inherit their namespaces. If you then embed it in the document and call verify(), the namespaces will be found and the canonical form of SignedInfo will be different to that generated during sign().</p>
-<h5><a shape="rect" name="c_faq-1.7.HowdoesthelibraryidentifyIdattributes%3F"></a>1.7. How does the library identify Id attributes?</h5>
+<h5 id="c_faq-1.7.HowdoesthelibraryidentifyIdattributes?">1.7. How does the library identify Id attributes?</h5>
<p>During a signing operation, finding the correct Id attribute is vital. Should the wrong Id Attribute be used, the wrong part of the document will be identified, and what the user signs will not be what they expect to sign.</p>
@@ -161,13 +160,13 @@ Apache Santuario -- c_faq
<p>As this is a potential security exposure, this behaviour can be disabled using a call to DISGSignatures::setIdByAttributeName(false). There are also methods provided to modify the list of attributes that will be searched. However it is recommended that these methods not be used, and DOM attributes of Type=ID be used.</p>
-<p><b>Warning</b> In version 1.1 and above, the library defaults to searching for Id attributes by name if a search by Id fails. As this is a potential security risk, this behaviour may be changed in a future version of the library.</p>
+<p><strong>Warning</strong> In version 1.1 and above, the library defaults to searching for Id attributes by name if a search by Id fails. As this is a potential security risk, this behaviour may be changed in a future version of the library.</p>
-<h5><a shape="rect" name="c_faq-1.8.WhatpartsoftheXKMSspecificationdoesthelibrarysupport%3F"></a>1.8. What parts of the XKMS specification does the library support?</h5>
+<h5 id="c_faq-1.8.WhatpartsoftheXKMSspecificationdoesthelibrarysupport?">1.8. What parts of the XKMS specification does the library support?</h5>
<p>The library currently supports X-KISS (XML Key Information Service Specification) message generation and processing. Support for X-KRSS (XML Key Registration Service Specification) will be provided in version 1.3 of the library.</p>
-<h5><a shape="rect" name="c_faq-1.9.DoesthelibraryprovideaprogrammaticXKMSclient%3F"></a>1.9. Does the library provide a programmatic XKMS client?</h5>
+<h5 id="c_faq-1.9.DoesthelibraryprovideaprogrammaticXKMSclient?">1.9. Does the library provide a programmatic XKMS client?</h5>
<p>Not yet. A command line tool xklient is provided for generating and processing messages. This can be used as an example for processing XKMS messages.</p>
Modified: websites/production/santuario/content/cindex.html
==============================================================================
--- websites/production/santuario/content/cindex.html (original)
+++ websites/production/santuario/content/cindex.html Tue Dec 17 20:23:32 2013
@@ -52,7 +52,7 @@ Apache Santuario -- c_index
</td><td align="right" colspan="1" nowrap>
<a shape="rect" href="http://www.apache.org/" title="The Apache Software Foundation"><img border="0" src="http://activemq.apache.org/images/asf-logo.png"></a>
</td></tr></table>
-</p></div>
+</p><p></p></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -89,21 +89,20 @@ Apache Santuario -- c_index
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3><a shape="rect" name="Navigation-ApacheSantuario"></a>Apache Santuario</h3>
-<ul><li><a shape="rect" href="index.html" title="Index">Home</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="secadv.html" title="secadv">Security Advisories</a></li><li><a shape="rect" href="faq.html" title="faq">FAQ</a></li><li><a shape="rect" href="team.html" title="team">Team</a></li><li><a shape="rect" href="contributing.html" title="contributing">Contributing</a></li><li><a shape="rect" href="mailing.html" title="mailing">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html" title="history">History</a></li><li><a shape="rect" href="oldnews.html" title="old_news">Old News</a></li></ul>
+<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="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://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><a shape="rect" name="Navigation-Java"></a>Java</h3>
-<ul><li><a shape="rect" href="javaindex.html" title="java_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="javareleasenotes.html" title="java_release_notes">Release Notes</a></li><li><a shape="rect" href="javafaq.html" title="java_faq">FAQ</a></li><li><a shape="rect" href="javaapi.html" title="java_api">API</a></li><li><a shape="rect" href="javainterop.html" title="java_interop">Interoperability</a></li></ul>
+<h3 id="Navigation-Java">Java</h3>
+<ul><li><a shape="rect" href="javaindex.html">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="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul>
-<h3><a shape="rect" name="Navigation-C"></a>C++</h3>
-<ul><li><a shape="rect" href="cindex.html" title="c_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="creleasenotes.html" title="c_release_notes">Release Notes</a></li><li><a shape="rect" href="cinstallation.html" title="c_installation">Installation</a></li><li><a shape="rect" href="cfaq.html" title="c_faq">FAQ</a></li><li><a shape="rect" href="ctools.html" title="c_tools">Tools</a></li><li><a shape="rect" href="cprogramming.html" title="c_programming">Programming</a></li><li><a shape="rect" href="ccredits.html" title="c_credits">Credits</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="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">Programming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul>
-<h3><a shape="rect" name="Navigation-ASF"></a>ASF</h3>
-<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul>
-</div>
+<h3 id="Navigation-ASF">ASF</h3>
+<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></div>
<!-- NavigationBar -->
</div>
</div>
@@ -113,25 +112,31 @@ Apache Santuario -- c_index
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1><a shape="rect" name="c_index-ApacheXMLSecurityforC"></a>Apache XML Security for C++</h1>
+<div id="ConfluenceContent"><h1 id="c_index-ApacheXMLSecurityforC++">Apache XML Security for C++</h1>
-<h3><a shape="rect" name="c_index-Overview"></a>Overview</h3>
+<h3 id="c_index-Overview">Overview</h3>
<p>The Apache XML Security for C++ library is an implementation of the XML Digital Signature and Encryption specifications, along with some additional XKMS code. It is designed to be easily ported to new platforms, and is generally tested on Windows, Linux, OS X, and Solaris. Other platforms with autoconf support may also work.</p>
<p>The library makes use of the Apache Xerces-C XML Parser and Xalan-C XSLT processor. The latter is used for processing XPath and XSLT transforms. The use of Xalan-C is optional, but without it, XPath and XSLT transformations cannot be performed.</p>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">The state of the Xalan-C project is unclear at this time, and these features should be viewed with caution.</td></tr></table></div>
+ <div class="aui-message warning shadowed information-macro">
+ <span class="aui-icon icon-warning">Icon</span>
+ <div class="message-content">
+ <p>The state of the Xalan-C project is unclear at this time, and these features should be viewed with caution.</p>
+ </div>
+ </div>
+
<p>In addition, the library currently uses OpenSSL to provide cryptographic functionality. The cryptographic interface is implemented via a thin wrapper layer, and development versions of implementations for the Windows Cryptographic API and NSS have also been implemented.</p>
-<h3><a shape="rect" name="c_index-News"></a>News</h3>
+<h3 id="c_index-News">News</h3>
-<p>Version 1.7.2 of the Apache XML Security for C++ library has been released. This release addresses a number of <a shape="rect" href="secadv.html" title="secadv">security vulnerabilities</a> reported to the project. All library users should upgrade to this release as soon as practical.</p>
+<p>Version 1.7.2 of the Apache XML Security for C++ library has been released. This release addresses a number of <a shape="rect" href="secadv.html">security vulnerabilities</a> reported to the project. All library users should upgrade to this release as soon as practical.</p>
-<h3><a shape="rect" name="c_index-OldNews"></a>Old News</h3>
+<h3 id="c_index-OldNews">Old News</h3>
-<p>See <a shape="rect" href="oldnews.html" title="old_news">here</a> for old news.</p></div>
+<p>See <a shape="rect" href="oldnews.html">here</a> for old news.</p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/santuario/content/cinstallation.html
==============================================================================
--- websites/production/santuario/content/cinstallation.html (original)
+++ websites/production/santuario/content/cinstallation.html Tue Dec 17 20:23:32 2013
@@ -52,7 +52,7 @@ Apache Santuario -- c_installation
</td><td align="right" colspan="1" nowrap>
<a shape="rect" href="http://www.apache.org/" title="The Apache Software Foundation"><img border="0" src="http://activemq.apache.org/images/asf-logo.png"></a>
</td></tr></table>
-</p></div>
+</p><p></p></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -89,21 +89,20 @@ Apache Santuario -- c_installation
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3><a shape="rect" name="Navigation-ApacheSantuario"></a>Apache Santuario</h3>
-<ul><li><a shape="rect" href="index.html" title="Index">Home</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="secadv.html" title="secadv">Security Advisories</a></li><li><a shape="rect" href="faq.html" title="faq">FAQ</a></li><li><a shape="rect" href="team.html" title="team">Team</a></li><li><a shape="rect" href="contributing.html" title="contributing">Contributing</a></li><li><a shape="rect" href="mailing.html" title="mailing">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html" title="history">History</a></li><li><a shape="rect" href="oldnews.html" title="old_news">Old News</a></li></ul>
+<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="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://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><a shape="rect" name="Navigation-Java"></a>Java</h3>
-<ul><li><a shape="rect" href="javaindex.html" title="java_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="javareleasenotes.html" title="java_release_notes">Release Notes</a></li><li><a shape="rect" href="javafaq.html" title="java_faq">FAQ</a></li><li><a shape="rect" href="javaapi.html" title="java_api">API</a></li><li><a shape="rect" href="javainterop.html" title="java_interop">Interoperability</a></li></ul>
+<h3 id="Navigation-Java">Java</h3>
+<ul><li><a shape="rect" href="javaindex.html">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="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul>
-<h3><a shape="rect" name="Navigation-C"></a>C++</h3>
-<ul><li><a shape="rect" href="cindex.html" title="c_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="creleasenotes.html" title="c_release_notes">Release Notes</a></li><li><a shape="rect" href="cinstallation.html" title="c_installation">Installation</a></li><li><a shape="rect" href="cfaq.html" title="c_faq">FAQ</a></li><li><a shape="rect" href="ctools.html" title="c_tools">Tools</a></li><li><a shape="rect" href="cprogramming.html" title="c_programming">Programming</a></li><li><a shape="rect" href="ccredits.html" title="c_credits">Credits</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="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">Programming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul>
-<h3><a shape="rect" name="Navigation-ASF"></a>ASF</h3>
-<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul>
-</div>
+<h3 id="Navigation-ASF">ASF</h3>
+<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></div>
<!-- NavigationBar -->
</div>
</div>
@@ -113,15 +112,15 @@ Apache Santuario -- c_installation
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1><a shape="rect" name="c_installation-InstallingtheApacheXMLSecurityforCLibrary"></a>Installing the Apache XML Security for C++ Library</h1>
+<div id="ConfluenceContent"><h1 id="c_installation-InstallingtheApacheXMLSecurityforC++Library">Installing the Apache XML Security for C++ Library</h1>
-<h3><a shape="rect" name="c_installation-Prerequisites"></a>Prerequisites</h3>
+<h3 id="c_installation-Prerequisites">Prerequisites</h3>
<p>The library requires one of OpenSSL, NSS, or WinCAPI for cryptographic support, but only OpenSSL is well-tested. Xalan-C is also required if XPath and/or XSLT transformations are required.</p>
<p>Version 1.6.0 of the library has been tested with versions 3.x and 2.8.0 of Xerces-C, and Version 0.9.7 (and above) of OpenSSL. Xalan-C has no official releases that will build successfully with Xerces-C 3.x.</p>
-<h3><a shape="rect" name="c_installation-Gettingthesource"></a>Getting the source</h3>
+<h3 id="c_installation-Gettingthesource">Getting the source</h3>
<p>You can download the sources via WWW in the distribution directory from one of the Apache mirrors.</p>
@@ -129,17 +128,17 @@ Apache Santuario -- c_installation
<p>A HTTP interface to browse the sources online is available <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/santuario/xml-security-cpp/trunk/">here</a></p>
-<h3><a shape="rect" name="c_installation-BuildingforUNIX"></a>Building for UNIX</h3>
+<h3 id="c_installation-BuildingforUNIX">Building for UNIX</h3>
<p>XML Security C++ is currently fully supported on Red Hat and SUSE Linux, Solaris, and Mac OS X. It has been built and tested using GNU gcc 3.x/4.x and Sun Workshop (Solaris).</p>
-<h5><a shape="rect" name="c_installation-SetuptheEnvironment"></a>Set up the Environment</h5>
+<h5 id="c_installation-SetuptheEnvironment">Set up the Environment</h5>
<p>The build process has been corrected as much as possible to rely on standard configure and make commands and not environment variables.</p>
<p>If configure cannot find anything for Xalan, it will assume that you are not interested in XPath or XSLT support and will compile without linking to Xalan. Any attempt to use these features will raise an exception in the library.</p>
-<h5><a shape="rect" name="c_installation-Configure"></a>Configure</h5>
+<h5 id="c_installation-Configure">Configure</h5>
<p>Now go to the root directory and run the command ./configure. This will create the necessary makefiles and header files necessary to build the package.</p>
@@ -150,7 +149,7 @@ Apache Santuario -- c_installation
<p>Using the --without-xalan option will automatically mean that the library does not support XPath or XSLT transformations (although envelope transforms will work as the library can perform these without going through an XPath transform).</p>
-<h5><a shape="rect" name="c_installation-Compile"></a>Compile</h5>
+<h5 id="c_installation-Compile">Compile</h5>
<p>Assuming the output of the above command looks reasonable simply type make (or gmake) in the base directory. This will build the library. In addition, make tools will make the tools (or examples) in the src/tools directory.</p>
@@ -164,29 +163,29 @@ Apache Santuario -- c_installation
<p>Finally - you can use make clean and make distclean to remove all binaries and libraries (former) and build scripts (latter)</p>
-<h5><a shape="rect" name="c_installation-Install"></a>Install</h5>
+<h5 id="c_installation-Install">Install</h5>
<p>make install can be used to install the library and the include files into the relevant directories (which can be set via the configure script using the various --prefix= options.</p>
-<h3><a shape="rect" name="c_installation-BuildingforWindows"></a>Building for Windows</h3>
+<h3 id="c_installation-BuildingforWindows">Building for Windows</h3>
<p>Apache XML Security for C++ has been built and tested on Microsoft's Visual C++ 6.0 and 2005/2008/2010 compilers. The following subsections briefly describe how to rebuild the library, tools and samples using the supplied workspaces. The specific information is for VC6, but the process for later versions is similar.</p>
<p>The library can be built without OpenSSL on a Windows platform. (The WinCAPI provider will be used instead). See below for details on how to do this. This is experimental, but should work for some scenarios.</p>
-<h5><a shape="rect" name="c_installation-SetupDirectories"></a>Setup Directories</h5>
+<h5 id="c_installation-SetupDirectories">Setup Directories</h5>
<p>The workspace and project files provided do not make any assumptions about where Xerces, Xalan or OpenSSL might be on the system. The first step is therefore to configure VC directories under Tools->Options (Directories).</p>
<p>For the Include directories you will need something similar to my setup below (replacing D:\PROG\CLIB\.. with the appropriate path on your system).</p>
-<p><span class="image-wrap" style=""><img src="cinstallation.data/vc6a.gif" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image" src="https://cwiki.apache.org/confluence/download/attachments/25199053/vc6a.gif?version=1&modificationDate=1295355799000&api=v2" data-image-src="/confluence/download/attachments/25199053/vc6a.gif?version=1&modificationDate=1295355799000&api=v2"></p>
<p>Similarly the library directories will need to be added to. Note that in the example below, I use both Debug and Release libraries for Xalan and Xerces. As provided, the workspace projects link to the debug libraries for XSEC Debug and Release for XSEC Release.</p>
-<p><span class="image-wrap" style=""><img src="cinstallation.data/vc6b.gif" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image" src="https://cwiki.apache.org/confluence/download/attachments/25199053/vc6b.gif?version=1&modificationDate=1295355807000&api=v2" data-image-src="/confluence/download/attachments/25199053/vc6b.gif?version=1&modificationDate=1295355807000&api=v2"></p>
-<h5><a shape="rect" name="c_installation-Configure"></a>Configure</h5>
+<h5 id="c_installation-Configure.1">Configure</h5>
<p>If you are using Xalan and OpenSSL, no configuration is required when building from the Visual C++ v6.0 workspace.</p>
@@ -200,7 +199,7 @@ Apache Santuario -- c_installation
<p>When compiling, using the "...No Xalan configurations for each project. These are the same as the normal debug or release builds, but the Xalan library is not linked in.</p>
-<h1><a shape="rect" name="c_installation-BuildLibraryandTools"></a>Build Library and Tools</h1>
+<h1 id="c_installation-BuildLibraryandTools">Build Library and Tools</h1>
<p>The main workspace (for VC 6.0) is found in :</p>
Modified: websites/production/santuario/content/contributing.html
==============================================================================
--- websites/production/santuario/content/contributing.html (original)
+++ websites/production/santuario/content/contributing.html Tue Dec 17 20:23:32 2013
@@ -52,7 +52,7 @@ Apache Santuario -- contributing
</td><td align="right" colspan="1" nowrap>
<a shape="rect" href="http://www.apache.org/" title="The Apache Software Foundation"><img border="0" src="http://activemq.apache.org/images/asf-logo.png"></a>
</td></tr></table>
-</p></div>
+</p><p></p></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -89,21 +89,20 @@ Apache Santuario -- contributing
<div id="wrapper-menu-page-bottom">
<div id="menu-page">
<!-- NavigationBar -->
-<div id="navigation"><h3><a shape="rect" name="Navigation-ApacheSantuario"></a>Apache Santuario</h3>
-<ul><li><a shape="rect" href="index.html" title="Index">Home</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="secadv.html" title="secadv">Security Advisories</a></li><li><a shape="rect" href="faq.html" title="faq">FAQ</a></li><li><a shape="rect" href="team.html" title="team">Team</a></li><li><a shape="rect" href="contributing.html" title="contributing">Contributing</a></li><li><a shape="rect" href="mailing.html" title="mailing">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/licenses/">License</a></li><li><a shape="rect" href="history.html" title="history">History</a></li><li><a shape="rect" href="oldnews.html" title="old_news">Old News</a></li></ul>
+<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="http://svn.apache.org/viewvc/santuario/">SVN</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">Issue Tracking</a></li><li><a shape="rect" class="external-link" href="http://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><a shape="rect" name="Navigation-Java"></a>Java</h3>
-<ul><li><a shape="rect" href="javaindex.html" title="java_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="javareleasenotes.html" title="java_release_notes">Release Notes</a></li><li><a shape="rect" href="javafaq.html" title="java_faq">FAQ</a></li><li><a shape="rect" href="javaapi.html" title="java_api">API</a></li><li><a shape="rect" href="javainterop.html" title="java_interop">Interoperability</a></li></ul>
+<h3 id="Navigation-Java">Java</h3>
+<ul><li><a shape="rect" href="javaindex.html">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="javafaq.html">FAQ</a></li><li><a shape="rect" href="javaapi.html">API</a></li><li><a shape="rect" href="javainterop.html">Interoperability</a></li></ul>
-<h3><a shape="rect" name="Navigation-C"></a>C++</h3>
-<ul><li><a shape="rect" href="cindex.html" title="c_index">Index</a></li><li><a shape="rect" href="download.html" title="download">Download</a></li><li><a shape="rect" href="creleasenotes.html" title="c_release_notes">Release Notes</a></li><li><a shape="rect" href="cinstallation.html" title="c_installation">Installation</a></li><li><a shape="rect" href="cfaq.html" title="c_faq">FAQ</a></li><li><a shape="rect" href="ctools.html" title="c_tools">Tools</a></li><li><a shape="rect" href="cprogramming.html" title="c_programming">Programming</a></li><li><a shape="rect" href="ccredits.html" title="c_credits">Credits</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="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">Programming</a></li><li><a shape="rect" href="ccredits.html">Credits</a></li></ul>
-<h3><a shape="rect" name="Navigation-ASF"></a>ASF</h3>
-<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul>
-</div>
+<h3 id="Navigation-ASF">ASF</h3>
+<ul><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How Apache Works</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/">Foundation</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsor Apache</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></div>
<!-- NavigationBar -->
</div>
</div>
@@ -114,24 +113,24 @@ Apache Santuario -- contributing
<!-- Content -->
<div class="wiki-content">
<div id="ConfluenceContent">
-<h1><a shape="rect" name="contributing-ContributingtoApacheSantuario"></a>Contributing to Apache Santuario</h1>
+<h1 id="contributing-ContributingtoApacheSantuario">Contributing to Apache Santuario</h1>
-<h3><a shape="rect" name="contributing-Introduction"></a>Introduction</h3>
+<h3 id="contributing-Introduction">Introduction</h3>
<p>The Apache Santuario Project is an Open Source volunteer project released under a very open 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" title="mailing">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>
+<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>
<p>You can get your local working copy of the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/santuario/">latest and greatest code</a>. Review the todo list, choose a task (or perhaps you have noticed something that needs patching). Make the changes, do the testing, generate a patch, and post to the dev mailing list. (Do not worry - the process is easy and explained below.)</p>
-<h3><a shape="rect" name="contributing-HelpWantedHere"></a>Help Wanted Here</h3>
+<h3 id="contributing-HelpWantedHere">Help Wanted Here</h3>
<p>The rest of this document is mainly about contributing new or improved code and/or documentation, but 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 reproducable 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" title="mailing">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>
+<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 reproducable 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><a shape="rect" name="contributing-Subversion%28SVN%29UsageOverview"></a>Subversion (SVN) Usage Overview</h3>
+<h3 id="contributing-Subversion(SVN)UsageOverview">Subversion (SVN) Usage Overview</h3>
<p>An overview of how to use Subversion to participate in the Apache Santuario development. Do not be afraid - you cannot accidently destroy the actual code repository, because you are working with a local copy as an anonymous user. Therefore, you do not have the system permissions to change anything. You can only update your local repository and compare your revisions with the real repository.</p>
@@ -139,7 +138,7 @@ Apache Santuario -- contributing
<p>Have a look at the Java or C++ installation pages to see how to get a local copy of the source.</p>
-<h3><a shape="rect" name="contributing-SubversionCommitterwithHTTPSaccess"></a>Subversion Committer with HTTPS access</h3>
+<h3 id="contributing-SubversionCommitterwithHTTPSaccess">Subversion Committer with HTTPS access</h3>
<p>After a developer has consistently provided contributions (code, documentation and discussion), then the rest of the dev community may vote to grant this developer commit access to SVN.</p>
@@ -148,9 +147,9 @@ Apache Santuario -- contributing
<ul><li><a shape="rect" class="external-link" href="http://apache.org/dev/version-control.html#https-svn">Apache Committer Subversion Access</a></li><li><a shape="rect" class="external-link" href="http://svnbook.red-bean.com/" rel="nofollow">Subversion book</a></li></ul>
-<h3><a shape="rect" name="contributing-ProcedureforRaisingDevelopmentIssues"></a>Procedure for Raising Development Issues</h3>
+<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" title="mailing">mailing list</a> or the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/SANTUARIO">bug database</a>.</p>
+<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>
@@ -162,12 +161,11 @@ Apache Santuario -- contributing
<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><a shape="rect" name="contributing-ContributionNotesandTips"></a>Contribution Notes and Tips</h3>
+<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 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="createlink" href="https://cwiki.
apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=Patch&linkCreation=true&fromPageId=24193313">Patch</a>, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=Proposal&linkCreation=true&fromPageId=24193313">Proposal</a>, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=RT&linkCreation=true&fromPageId=24193313">RT</a> (Random Thought which quickly blossom into research topics <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif" height="20" width="20" alt="" border="0">, <a shape="rect" class="createlink" href="https://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=SANTUARIO&title=STATUS&linkCreation=true&fromPageId=24193313">STATUS</a> (development status of a certain facility).</li><li>When makin
g 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 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>You would usually do any development work against the HEAD branch of CVS.</li><li>When sending a patch, you usually do not need to worry about which CVS branch it should be applied to. The maintainers of the repository will decide.</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 t
hread.</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>
-
+<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 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 blossom into research topics <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png" 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 de
tect 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 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. Redu
ce clutter.</li><li>You would usually do any development work against the HEAD branch of CVS.</li><li>When sending a patch, you usually do not need to worry about which CVS branch it should be applied to. The maintainers of the repository will decide.</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>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>
<!-- Content -->