Jul 22
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!













July 22nd, 2008 at 11:34 am
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
July 22nd, 2008 at 11:35 am
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
July 22nd, 2008 at 11:36 am
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
July 22nd, 2008 at 11:38 am
[...] The Flex, Spring and BlazeDS full stack on Adobe Developer Connection [...]
July 22nd, 2008 at 12:56 pm
What did you do for spring security? There is still no good article out their about integrating flex + spring + blazeds + spring security
July 22nd, 2008 at 1:10 pm
[...] Source [...]
July 22nd, 2008 at 1:33 pm
that’s a very good question indeed. I haven’t tried yet.
July 29th, 2008 at 6:55 pm
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?
August 7th, 2008 at 5:20 pm
[...] 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 [...]
August 11th, 2008 at 9:58 pm
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
August 11th, 2008 at 9:59 pm
Sorry, i meaned Sebastien, :S lazy fingers…
August 11th, 2008 at 10:00 pm
Oh, and the missing file is
Missing:
———-
1) org.epseelon.samples:todolist-common:jar:1.0-SNAPSHOT
August 12th, 2008 at 9:21 am
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.
August 12th, 2008 at 4:40 pm
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!
August 13th, 2008 at 5:34 pm
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.
August 22nd, 2008 at 10:20 am
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.
August 26th, 2008 at 5:30 pm
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
August 26th, 2008 at 8:43 pm
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