greenhouse broken?

[svago]

running the android client yields the following error after username/password credentials are entered. It looks like the MembersController.profile method expects an Account parameter but a UsernamePasswordAuthenticationToken (in which an Account is buried inside a Principal) is being passed by the interceptor stack. Any help on this is appreciated! BTW i also see this with the EventsController as well...

SEVERE: Servlet.service() for servlet [appServlet] in context with path [/greenhouse] threw exception [Request processing failed; nested exception is java.lang.IllegalArgumentException: argument type mismatch
HandlerMethod details:
Controller [com.springsource.greenhouse.members.MembersControl ler]
Method [public com.springsource.greenhouse.members.Profile com.springsource.greenhouse.members.MembersControl ler.profile(com.springsource.greenhouse.account.Ac count)]
Resolved arguments:
[0] [type=org.springframework.security.authentication.U sernamePasswordAuthenticationToken] [value=org.springframework.security.authentication. UsernamePasswordAuthenticationToken@fe9203ec: Principal: com.springsource.greenhouse.account.Account@16d695 6; Credentials: [PROTECTED]; Authenticated: true; Details: org.springframework.security.oauth.provider.OAuthA uthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities]
] with root cause
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.web.method.support.InvocableHa ndlerMethod.invoke(InvocableHandlerMethod.java:212 )
at org.springframework.web.method.support.InvocableHa ndlerMethod.invokeForRequest(InvocableHandlerMetho d.java:126)
at org.springframework.web.servlet.mvc.method.annotat ion.ServletInvocableHandlerMethod.invokeAndHandle( ServletInvocableHandlerMethod.java:96)
at org.springframework.web.servlet.mvc.method.annotat ion.RequestMappingHandlerAdapter.invokeHandlerMeth od(RequestMappingHandlerAdapter.java:629)
at org.springframework.web.servlet.mvc.method.annotat ion.RequestMappingHandlerAdapter.handleInternal(Re questMappingHandlerAdapter.java:590)
at org.springframework.web.servlet.mvc.method.Abstrac tHandlerMethodAdapter.handle(AbstractHandlerMethod Adapter.java:80)
at org.springframework.web.servlet.DispatcherServlet. doDispatch(DispatcherServlet.java:900)
at org.springframework.web.servlet.DispatcherServlet. doService(DispatcherServlet.java:827)
at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:874)
at org.springframework.web.servlet.FrameworkServlet.d oGet(FrameworkServlet.java:779)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:621)

[Keith Donald]

Yes, this popped due to a bug that was recently introduced in Spring Framework. I've worked around the problem as part of the upgrade to Spring Framework 3.1 RC1. The bug that caused this is minor and should be fixed in RC2.

Keith

[svago]

thanks for the attention to this, Keith. One thing i did notice was that the Account parameter in GroupsController.eventView is never referenced/used. Is this intentional. My quick workaround was to just remove it.