Thanks for your comment. I

rainwebs — Sat, 03 May 2008 22:12:23 -0400

Thanks for your comment. I agree with your stack. Our current architecture uses certain parts of it already, but still misses the "cool frontend" and OSGI. So, we're on the way into the exciting future ;-).

For Flex projects that I

rv49649 — Sat, 03 May 2008 14:19:53 -0400

For Flex projects that I oversee, and establish architectual direction for, my teams have devised this Spring-centric open source stack for the server-side (from bottom toward top):

Java 6 JRE
Tomcat 6 (supports HTTP listener using NIO and implements Comet Events protocol)
Spring 2.5.x
Spring Security (Acegi-based)
Spring JdbcTemplate and iBATIS (or could use Hiberanate or JPA)
BlazeDS 3.0
JDOM (for any server-side XML processing)
XStream (for any need of marshalling Java objects as XML format)
Spring OSGi (Equinox-based in our case)
ActiveMQ (for JMS messaging - messages published to a JMS topic are routed to Flex-based client subscribers via BlazeDS; Flex clients can in turn publish into JMS queues and topics)

With the way BlazeDS is wired in, we use Spring POJO beans to handle BlazeDS remoting, Spring Controllers enable using Spring POJOs to handle HTTP services such as GET/POST/PUT, and using Spring JMS template classes we also wire Spring POJOs to process ActiveMQ JMS messaging. Spring security is applied uniformly across all these context.

Certainly the big news is that SpringSource has debuted a Equinox-based OSGi framework directly themselves. Folks seem to be regarding this as a tipping point of SpringSource directly entering into the "application server" fray - as an alternative to JEE, of course.

I know it's possible to do all manner of other server-side "simple SOA" solutions for Flex/AIR clients, but I tend to view this Tomcat/Spring/OSGi/BlazeDS/ActiveMQ combo as the most potent thing going. The power of Spring on the middle-tier seems well matched to the competence and coolness of Flex on the client.

So the equation for the next generational phase of the web might be written as:

Web RIA + SOA

but I think more intuitively of this as really being:

Flex/AIR RIA + Spring/BlazeDS

Anything else would be just poor imitations or substitutes.

Meanwhile, there's an

rainwebs — Fri, 02 May 2008 15:51:19 -0400

Meanwhile, there's an alternative to Flexible written in AIR:

designview

As the link starts the designer immediately, you may use Adobe Exchange for download/installation.

Web Builder Zone - Comments for "AIRgonaut: The &quot;From Desktop to AIRtop&quot; Series"

Thanks for your comment. I

For Flex projects that I

Meanwhile, there's an

Web Builder Zone - Comments for "AIRgonaut: The "From Desktop to AIRtop" Series"