Hi,
I use flex 4.5, BlazeDS 4 and Spring-flex 1.5.
When I try to return objects annotated with javax.persistence.*, Spring converts the object values:
11:33:00:819 - DEBUG - ? - Actual type of...
Type: Posts; User: 2rr; Keyword(s):
Hi,
I use flex 4.5, BlazeDS 4 and Spring-flex 1.5.
When I try to return objects annotated with javax.persistence.*, Spring converts the object values:
11:33:00:819 - DEBUG - ? - Actual type of...
It seems like I have to override the class org.springframework.flex.core.DefaultExceptionLogg er, and make sure that this will not log warnings. But how should I do this?
First I create a custom...
I had another go at fixing this exception message problem...
Hi,
The problem with 1.5.0 is that every time a java exception is thrown back to the flex client, the log is polluted by a long stacktrace. With 1.0.3 this did not happen.
Example 1.0.5:
...
Thank you for your answer. Unfortunatly I still have the same problem. I changed the project layout as you suggested. In addition I changed to:
<mvc:resources mapping="/css/**"...
Hi,
Hope someone can help me with this problem. The problem is that the resources is not found after I add a path variable. It works fine without.
Structure:
WEB-INF
css
images
First of all, I really appreciate your answer. Thank you!
The use of an Adapter confused me to. The reason I used it was because I followed an example found on the web. But in that example they...
Seriously, there must be someone with a qualified answer in here! I would appricate some help.
Hi,
In my application I use Flex, BlazeDS, Spring, Spring Security and Spring BlazeDS integration.
My problem is that I am not sure how to handle timeouts correctly. I was hoping that I could...
I have tested this new version briefly and it seems like the behavior now equals the M2 release. Thanks for fixing this very quickly.
Done. http://jira.springframework.org/browse/FLEX-69
I got the same problem when I upgraded from M2 to the current release. Before I could throw an exception from Java and then get its variables easily through FaultEvent.fault.rootCause, but now I have...