From a6f77271b899fecba13a728b142997a403650831 Mon Sep 17 00:00:00 2001
From: Keith Donald <kdonald@vmware.com>
Date: Tue, 1 May 2007 22:32:28 +0000
Subject: [PATCH] removed confusing logging statement that implies a lock was
 being acquired when it wasnt

---
 .../support/AbstractConversationFlowExecutionRepository.java  | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/spring-webflow/src/main/java/org/springframework/webflow/execution/repository/support/AbstractConversationFlowExecutionRepository.java b/spring-webflow/src/main/java/org/springframework/webflow/execution/repository/support/AbstractConversationFlowExecutionRepository.java
index c456be19..7a4dd6fa 100644
--- a/spring-webflow/src/main/java/org/springframework/webflow/execution/repository/support/AbstractConversationFlowExecutionRepository.java
+++ b/spring-webflow/src/main/java/org/springframework/webflow/execution/repository/support/AbstractConversationFlowExecutionRepository.java
@@ -118,10 +118,6 @@ public abstract class AbstractConversationFlowExecutionRepository extends Abstra
 	}
 
 	public FlowExecutionLock getLock(FlowExecutionKey key) throws FlowExecutionRepositoryException {
-		if (logger.isDebugEnabled()) {
-			logger.debug("Getting lock for flow execution with key '" + key + "'");
-		}
-		// lock the entire conversation
 		return new ConversationBackedFlowExecutionLock(getConversation(key));
 	}