Comments on: Using Spring BlazeDS Integration 1.0

By: Manish

Manish — Thu, 04 Mar 2010 13:21:53 +0000

Can this be integrated with Spring.net?

By: flex 使用Spring BlazeDS Integration | wsflex

flex 使用Spring BlazeDS Integration | wsflex — Wed, 06 Jan 2010 08:29:36 +0000

[...] http://blog.springsource.com/2009/06/10/using-spring-blazeds-integration-10/ [...]

By: Thanuj Kumar

Thanuj Kumar — Mon, 23 Nov 2009 17:28:12 +0000

Already there is an application built using Spring technology and uses JSF as view technology. This is a client-server model, i am looking at solution where JSF is replaced with Adobe Flex and using Adobe Flex on desktop version of the application using Adobe AIR. At this point there isn't possibility to use existing code from Spring to move on to desktop application. I would like to know how much of the Spring code can be used for desktop application from client-server model. Is it possible to retain Business and Persistent layer of spring for desktop application using Adobe Flex and AIR instead of Java Swings?

Please let me know is this possible?

By: Curso de Spring Framework. - VPSA Blog

Curso de Spring Framework. - VPSA Blog — Fri, 30 Oct 2009 13:43:29 +0000

[...] Site do Spring: http://www.springsource.org/download Spring Integration BlazeDS: http://blog.springsource.com/2009/06/10/using-spring-blazeds-integration-10/ [...]

By: Oltar

Oltar — Mon, 28 Sep 2009 14:42:13 +0000

Solution – after adding some semicolons…

1. Open testdrive's main pom.xml : [Examples dir]\spring-flex-samples\spring-flex-testdrive\pom.xml

2. Add the following property:

testdrive

3. Open [Examples dir]\spring-flex-samples\spring-flex-testdrive\testdrive\pom.xml

4. Set final war-file name according to the previously defined property:
${app.context.root}

5. In all [Examples dir]\spring-flex-samples\spring-flex-testdrive\[Project dir]\pom.xml build files, set the context root used by Flex client to:
/${app.context.root}

6. Rebuild and redeploy testdrive.war to Tomcat's webapps directory.

Sorry for the mess – some preview feature would be useful…

By: Oltar

Oltar — Mon, 28 Sep 2009 14:36:39 +0000

The solution once again – thought the message box was somewhat more sophisticated…

Solution

1. Open testdrive's main pom.xml : [Examples dir]\spring-flex-samples\spring-flex-testdrive\pom.xml

2. Add the following property:

</properties>

3. Open [Examples dir]\spring-flex-samples\spring-flex-testdrive\testdrive\pom.xml

4. Set final war-file name according to the previously defined property:
${app.context.root}

5. In all [Examples dir]\spring-flex-samples\spring-flex-testdrive\[Project dir]\pom.xml build files, set the context root used by Flex client to:
/${app.context.root}

6. Rebuild and redeploy testdrive.war to Tomcat's webapps directory.

By: Oltar

Oltar — Mon, 28 Sep 2009 14:29:24 +0000

Hello.

I think I solved the context problem encountered by 3fr41n and other developers. My solution doesn't require deployment to the Tomcat's ROOT, or any changes in servlet mappings.

Cause of the problem

The {context.root} token in services-config.xml is substituted at compile time by a parameter passed to the mxmlc. The value of this parameter is defined separately in each project's pom.xml, by the element of flexmojos' plugin configuration. By default, it is set to "/". That's why Flex clients try to access Tomcat's ROOT context in search of the AMF channel, instead of [application name] context created by Tomcat.

Solution

1. Open testdrive's main pom.xml : [Examples dir]\spring-flex-samples\spring-flex-testdrive\pom.xml

2. Add the following property:

testdrive

3. Open [Examples dir]\spring-flex-samples\spring-flex-testdrive\testdrive\pom.xml

4. Set final war-file name according to the previously defined property:
${app.context.root}

5. In all [Examples dir]\spring-flex-samples\spring-flex-testdrive\[Project dir]\pom.xml build files, set the context root used by Flex client to:
/${app.context.root}

6. Rebuild and redeploy testdrive.war to Tomcat's webapps directory.

Now the app.context.root keeps everything in sync and Flex clients use valid url's when sending RPC requests. It is probably not the most elegant solution, but it works

Hope this helps and inspires somebody to invent something better.

Regards,
Oltar

By: kudos ltda.

kudos ltda. — Wed, 16 Sep 2009 21:39:54 +0000

That issue is open in Jira: Ensure compatability with Spring Security 3.0 http://jira.springframework.org/browse/FLEX-65

By: German

German — Wed, 16 Sep 2009 20:57:49 +0000

to kudos ltda.: I had the same problem. I had to fall back to spring security 2.0.5. If you check distribution 3.x and 2.0.x the class org.springframework.security.Authentication is in different folders.

By: kudos ltda.

kudos ltda. — Wed, 16 Sep 2009 20:48:36 +0000

I'm trying to use spring blazeds integration 1.0 with spring-framework-3.0.0.M4 , spring-security-3.0.0.M2 and Hibernate 3.3.0 but It seems that there is an incompatibility between blazeds integration 1.0 and spring-security-3.0.0.M2:

Error creating bean with name '_messageBrokerLoginCommand': Resolution of declared constructors on bean Class [org.springframework.flex.security.SpringSecurityLoginCommand] from ClassLoader [WebappClassLoader]

Caused by: java.lang.ClassNotFoundException: org.springframework.security.Authentication

any idea?
thanks for your help