This solution is really works. And old style binding (where FormAction is used) also works.
But the bug is really exists. At this time we can not use converters to bind values from MultipartFile...
Type: Posts; User: serg-b; Keyword(s):
This solution is really works. And old style binding (where FormAction is used) also works.
But the bug is really exists. At this time we can not use converters to bind values from MultipartFile...
Yes, and really I want to pass this imported beans as parameters to methods of beans from the global application context. In this example bean with id "bean" is some application scope object, e.g....
to Mister_Lie:
yes, your have understood the problem. But your method is not a solution. I need really dynamic invocation and I do not want to place into main application context some dependencies...
Can we pass beans from the application context as bean-action parameters?
For example, here is an application context fragment:
<bean id="alpha" class="..." />
<bean id="beta" class="..." />
...
I am thinking the following extensions will be usefull.
<transition on-exception="example.MyBusinessException" to="state3">
<errors>
<error formAction="exampleFormAction"...
There is a closed issue
http://opensource.atlassian.com/projects/spring/browse/SPR-2648. But
the problem still alive. The file contains a test case.
This bug appears only when I building with...
Yes, I do not understand this scope. Now I have changed formErrorsScope to REQUEST and my application now is working. Thanks.
I have been using webflow for a long time. Some my form objects are not serializable. I am placing such objects in request scope. So there were no problems. (I am using client continuation...
It looks like "forcePrincipalAsString"="true". In your configuration this property value is "false", but...
Try to debug. You need to trace 4 last lines of the method...
Problem arises in method "checkAuthenticationAllowed(Authentication)".
Really RememberMeAuthenticationToken is rejected by the method...
You class mixes two responsibilities. You can split it into a thread executor and a bean impelementing some bisness logic. The last will be intercepted. This schema do not need making the class aware...
So, you are using "internal" call. An interception works only for outside invocations. At this situation you can use "org.springframework.aop.framework.AopContext.currentProxy()" to make an...