The Flex, Spring and BlazeDS full stack on Adobe Developer Connection
The last part of the reedition of my article series about Flex and Spring has been published on the Adobe Developer Connection. This episode is the last one in this improved series so if you haven’t read it yet on my blog, I think the version I gave to ADC is better.
Enjoy!
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
What did you do for spring security? There is still no good article out their about integrating flex + spring + blazeds + spring security
[...] Source [...]
that’s a very good question indeed. I haven’t tried yet.
Having strange error when building client. I have been following your posts and mine is slightly different because I am using LCDS. Anyhow when I try to do a “mvn install” on the client (i.e. todo-ria in your example) I get an error:
“Could not resolve to a component implementation”
So I realize I need to add “fds.swc” as a dependency in my POM so i add:
com.adobe.flex.sdk
fds
3.0.0.3.0.0.477
swc
Now when I run “mvn install” I get:
Unable to resolve resource bundle “data” for locale “en_US”
Any ideas?
[...] proposed AMF support for the Zend framework and of course BlazeDS which fits wonderfull into a stack with Spring and Hibernate! – Posted in ActionScript, Cairngorm, Flex by Sönke [...]
Hello Seabstien, great tutorials!! I only have one question to do, when im on step 3, i download the sample file, and when i try the mvn install im getting this error:
1 required artifact is missing.
for artifact:
org.epseelon.samples:todolist-web:war:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
flex-mojos-repository (http://flex-mojos.googlecode.com/svn/trunk/repository/)
,
epseelon-repository (http://m2repo.epseelon.org/)
How can i (or you :] ) fix this?
Thanks, you finally disipated a big black cloud i had on my mind about how to use blazeDS
Sorry, i meaned Sebastien, :S lazy fingers…
Oh, and the missing file is
Missing:
———-
1) org.epseelon.samples:todolist-common:jar:1.0-SNAPSHOT
Are you sure you’re running mvn install from the root directory of the project? Because todolist-common is one of the three components of the project and the other two depend on this one. So if you run mvn install under todolist-ria for example, and you have never run it under todolist or todolist-common, then todolist common has never been deployed to your local repository, which yields the message you get.
Hi Sebastien, its me again, thanks for your help on this.
I did tried to run it in the main root folder of the project but i still get that dependency error, look here please, its my full mvn install log with -e parameter:
http://www.adrianlabastida.com/?page_id=30
Thanks again!
HI, me again… just to let you know, if i download the sample files from your site instead from the ones @ adobe’s version of the tutorial, the sample compiles successfully! (Specifically the sample file on part 3)
What may be different?
Thanks for all the info.
Thanks Sebastian, I actually followed your articles but customizing it to my own multi-module project and I can say it works like a charm.I used 1.0 version of flex-mojo though and one thing to note is flex-mojo SVN is under a new place: http://svn.sonatype.org/flexmojos. Thanks a lot.
Hi Sébastien,
I’ve downloaded the todolist3.zip from the 3 part (from adobe site) and it doesn’t build. Here is the stack trace:
[ERROR] BUILD ERROR
[INFO] ————————————————————————
[INFO] Failed to resolve artifact.
Missing:
———-
1) org.epseelon.samples:todolist-common:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.epseelon.samples -DartifactId=todolist-common -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.epseelon.samples -DartifactId=todolist-common -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.epseelon.samples:todolist-web:war:1.0-SNAPSHOT
2) org.epseelon.samples:todolist-common:jar:1.0-SNAPSHOT
———-
1 required artifact is missing.
Looks like the module todolist-common was missed and I can’t see it inside the archive.
Thanks
Kirill, hello.
I had the very same issue, and what i did was to download the sample files on the tutorials here on Sebastien’s website instead of the ones in adobe’s website.
Take a shot and see if that worked for you
Regards.
Adrian
Hi Sebastein,
Good work, all works like u said. We need the actionscript generator that creates action script classes from java pojos, can u help us out. Also any work done towards, creating tests.
–Irshad.
Hi Sebastien
Do you have a plan to add an episode 4 to the serie where you show how to use Streaming over BlazeDS ?
Or do you know where there is a good example for that ?
Thank you!
matt
Good work mate.
Well, I wanted to contact you but, the contact form didn’t appear to me.
Cheers!
Contact form is fixed…
OK, obviously there are 2 problems in my article on Adobe Developer Connection and I finally found the time to look into it:
First of all, there was a big error in one of the POMs in todolist3.zip. In todolist-web/pom.xml, if the first dependency looks like this:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>todolist-common</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
Then replace it with this:
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>todolist-config</artifactId>
<version>1.0-SNAPSHOT</version>
<classifier>resources</classifier>
<type>zip</type>
<scope>provided</scope>
</dependency>
And it should work fine.
The second error is in the article itself: of course, all of the namespace declarations should be xmlns:mx=”http://www.adobe.com/2006/mxml” instead of xmlns:mx=”/2006/mxml” .
I’ll try to reach ADC editor so that they can fix those mistakes. Thanks for the feedback.
[...] An overview of the Flex/BlazeDS Stack: http://sebastien-arbogast.com/2008/07/22/the-flepring-and-blazeds-full-stack-on-adobe-developer-conn… [...]
Hi,
Am facing the below exception while am building folder under todolist-ria.Please help me out
[INFO] Trace
java.lang.NullPointerException: id can not be null
at org.apache.maven.wagon.repository.Repository.(Repository.java:81)
at org.apache.maven.artifact.repository.DefaultArtifactRepository.(DefaultArtifactRepository.java:70)
at org.apache.maven.artifact.repository.DefaultArtifactRepositoryFactory.createDeploymentArtifactRepository(DefaultArtifactRepositoryFactory.java:44)
at org.apache.maven.project.ProjectUtils.buildDeploymentArtifactRepository(ProjectUtils.java:80)
at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1029)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:880)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255)
at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:277)
at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184)
at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1626)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHandlersInPlugins(DefaultLifecycleExecutor.java:1468)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:222)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:178)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] -
Description Resource Path Location Type
The project was not built due to “Resource already exists on disk: ‘/todolist-web/target/classes/org/epseelon/samples/todolist/domain/hibernate/hbm/TodoItem.hbm.xml’.”. Fix the problem, then try refreshing this project and building it since it may be inconsistent todolist-web Unknown Java Problem
Regards
Pawan
Hi Sebastien,
Please help me to solve this problem.
regards
Hi, very nice post.. I will add to greader
Regards,
Albulescu Cosmin