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
