I would avoid Java FX on the client side like the plague. It's a repackaging of the 15-year-old Java Applet technology which has a lot of problems. Java Swing is a nice API for building GUIs, but Java Applets and especially the Java Plug-in in browsers have a lot of problems that I would not want to experience again. (I developed Applets for years before switching to Flex.)
I would recommend Flex on the client side, Java on the server side, and either BlazeDS or LCDS for communicating between client and server. BlazeDS is free and simple, LCDS is elaborate and expensive. --- In [email protected], "TCash21" <tanya_cashor...@...> wrote: > > Hi all, > I'm currently trying to push Adobe Flex at my company for complex > network visualizations. The application will also need to run > computationally intensive simulations (accessing backend java code) as > well as some other distributed tasks. I know Java can store > everything in memory and access it but is Flex just as able? Would it > require Flex Data Services and what are the advantages? I'm easily > sold on the UI-experience and aesthetic appeal of the front-end, I'm > just unsure how it would handle massive computational efforts on the > backend and display it all to the client quickly. > > We're trying to figure out the best way to go, will it be JavaFX? Flex > Data Services? Flex and Java integrated? Elixir? > > Thank you all for any input, > -Tanya >
