Fixed a typo in the logging initializer that was causing the transaction log to fail.
authorwassa <wassa@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Tue, 17 May 2005 19:08:14 +0000 (19:08 +0000)
committerwassa <wassa@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Tue, 17 May 2005 19:08:14 +0000 (19:08 +0000)
git-svn-id: https://subversion.switch.ch/svn/shibboleth/java-idp/trunk@1497 ab3bd59b-922f-494d-bb5f-6f0a3c29deca

src/edu/internet2/middleware/shibboleth/log/LoggingInitializer.java

index 3b421c8..fea1126 100644 (file)
@@ -89,7 +89,7 @@ public class LoggingInitializer {
         */
        public static void initializeLogging(Element configuration) throws ShibbolethConfigurationException {
 
-               NodeList txLogElems = configuration.getElementsByTagNameNS(IdPConfig.configNameSpace, "TransactonLog");
+               NodeList txLogElems = configuration.getElementsByTagNameNS(IdPConfig.configNameSpace, "TransactionLog");
                if (txLogElems.getLength() > 0) {
                        if (txLogElems.getLength() > 1) {
                                System.err.println("WARNING: More than one TransactionLog element detected in IdP logging "