OK, we're baffled. We somehow got this to build yesterday but when we tried
to run we got:
Invocation of init method failed; nested exception is
java.lang.NoSuchMethodError:
org.apache.mina.transport.socket.nio.NioSocketAcceptor.<init>(ILjava/util/concurrent/Executor;)V
Caused by: java.lang.NoSuchMethodError:
org.apache.mina.transport.socket.nio.NioSocketAcceptor.<init>(ILjava/util/concurrent/Executor;)V
at
org.safehaus.asyncweb.service.transport.mina.MinaTransport.start(MinaTransport.java:166)
at org.safehaus.asyncweb.service.BasicServiceContainer.startTransports
(BasicServiceContainer.java:298)
at
org.safehaus.asyncweb.service.BasicServiceContainer.start(BasicServiceContainer.java:227)
... which has me baffled as to how we got it to build. An now we can no
longer get even that going. It's back tol complaining about the CRLF -->
CrLf name change.
Any ideas on this? Should the current Asyncweb in the sandbox be buildable?
Thanks!
Ben
bmarklein wrote:
>
> OK, seems to be fixed now...
>
>
> bmarklein wrote:
>>
>> We're trying to get Asyncweb to build and it currently won't because
>> CRLFDecodingState was renamed. Looks like this was a change Trustin made
>> a couple of hours ago.
>>
>> Can someone either a) fix this or b) let us know how to force Maven to
>> grab an older jar? Thanks!
>>
>> Ben
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/CRLFDecodingState-name-change---Asyncweb-doesn%27t-build-tf4788938s16868.html#a13720824
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
