Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of rstoyanchev@gopivotal.com
 designates 209.85.219.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <39154AAD-FCB0-48C4-B93D-15A8C1493165@nicholaswilliams.net>
References: 
 <CANiB1ks9-RzAm1HwL44U0t8YuMD7ckLEamxDXMbq6MTacwf1aA@mail.gmail.com>
	<520D016F.4000203@apache.org>
	<39154AAD-FCB0-48C4-B93D-15A8C1493165@nicholaswilliams.net>
Date: Thu, 15 Aug 2013 13:04:32 -0400
Message-ID: 
 <CAOYD2cbKHYLykUbUgcPGFqAgVP4szQyj9fveRNqRt8swqZScSg@mail.gmail.com>
Subject: Re: Exception by upgrading to WebSocket connection in 8.0.0-RC1
From: Rossen Stoyanchev <rstoyanchev@gopivotal.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Aug 15, 2013 at 12:39 PM, Nick Williams
<nicholas@nicholaswilliams.net> wrote:

>> I suspect that as both Spring 4 and Tomcat 8 are both in RC / milestone
>> stage that Tomcat changed in a way Spring wasn't expecting.

Right. This is already fixed actually. Just use Spring Framework
4.0.0.BUILD-SNAPSHOT.

Once the ticket below is completed, the underlying cause for this
issue should go away by the way:
https://issues.apache.org/bugzilla/show_bug.cgi?id=55314

Rossen

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org