By newton_dave
via joshuajava.wordpress.com
Published: Nov 24 2008 / 19:38
A guy offers some reasons people might not want to use Flex and compares it with some functionality from Tapestry. I am not associated with Flex or Tapestry.
Tweet
SaveShareSend
Tags: flash-flex, frameworks, java, ria



Comments
Ola Bildtsen replied ago:
thejavafreak replied ago:
How could Flex be an application framework? It doesn't have what an application frameworks should have.
codecraig replied ago:
@thejavafreak: such as....??
thejavafreak replied ago:
* Email sending
* Report
* DB Connection. Including transactional support
* Security. Authorization and authentication
It all relies on what's on the server. Flex only send data to the server (or the backend) to process it. How could you say it's an application framework. Clearly it's a view presentation only. Look at Seam or Spring and you'll get what I mean.
Miloskov replied ago:
It means it is not mature enough yet. Thats why I would like people to appreciate Swing because is already very mature and it could work for RIA with JRE6_10.
Amr Ellafy replied ago:
Flex is not an application Framework and it should be wired to the Framework of your choice (asp.net, java or php). I think Flex is doing very well for client UI
Voters For This Link (15)
Voters Against This Link (14)