I don't think integrating BlazeDS will be too difficult. You'll definitely get better performance out of it than if you went with REST or even SOAP. REST would definitely give you the reusability for other front ends, but like was stated before you lose out on the ability to use a full fledged domain model on the client side then and are stuck using the object proxies that Flex creates to wrap the responses from the web services.
My $0.02, Jeremy On Fri, Mar 13, 2009 at 4:04 PM, Rafael Nami <rafan...@gmail.com> wrote: > I'm using BlazeDS and AMF for quite a year now, and for me is much more > attractive, because your flex side is completely OO, instead of xml/JSON/WS > parsing related with E4X. Performance is a good argument too, but I believe > for Appfuse, everything must be kept flexible. Not that would be so > difficult to implement both as options as well, because the AMF + BlazeDS > would use just the Service layer. The bottom part - are you thinking on > doing something like "scaffolding" in Flex Client as well? > Cheers > > Rafael Nami > > > 2009/3/13 Matt Raible <m...@raibledesigns.com> > >> I believe REST is a better option as it can be used by multiple >> front-ends and can also be used as an API. However, if you can >> convince me that BlazeDS or AMF is a better choice, I'm open to that >> as well. >> >> Matt >> >> On Fri, Mar 13, 2009 at 1:35 PM, Rafael Nami <rafan...@gmail.com> wrote: >> > Hi Matt, how are you? >> > What about the Flex integration - are you thinking on use REST/WS to >> > communicate with it, or are you thinking on doing that with BlazeDS and >> AMF? >> > Best Regards >> > Rafael Nami >> > >> > 2009/3/13 Matt Raible <m...@raibledesigns.com> >> >> >> >> All, >> >> >> >> I've created a wiki page with ideas I have for improving AppFuse as >> >> part of Google's Summer of Code. If you have additional ideas, please >> >> add them to this page. >> >> >> >> http://appfuse.org/display/APF/Google+Summer+of+Code >> >> >> >> For your convenience, I've copied the list below. >> >> >> >> * Create a new archetype (appfuse-ws) that allows just deploying >> >> a backend (with SOAP/REST/GWT/Flex support). >> >> http://issues.appfuse.org/browse/APF-897 >> >> * Add ICEfaces to JSF module. This work has already been started. >> >> * Add REST support via existing XFire/CXF. >> >> * Add Flex support (light and/or basic). >> >> * Add GWT support (light and/or basic). >> >> * Add Compass support (patch exists for backend). >> >> * Upgrade to Spring 3.0 and convert Spring MVC to REST that can >> >> serve up HTML and JSON. >> >> * Upgrade to Struts 2.1, add REST plugin and allow serving up both >> >> HTML and JSON. >> >> >> >> Thanks, >> >> >> >> Matt >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net >> >> For additional commands, e-mail: users-h...@appfuse.dev.java.net >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net >> For additional commands, e-mail: users-h...@appfuse.dev.java.net >> >> >
