My two cents. I don't think that it's a question of Flex vs. Java. Flex and Java work well together. I've built applications using the HTTP and Web Services request facilities of Flex with Java and Java Web Services and they work great.
More importantly, *why* are they considering changing from ColdFusion to Java/JSP? They have to weigh the costs of the conversion against the benefits of the switch. Good reasons for a switch might be that, for example, it is becoming difficult or expensive to find ColdFusion developers...? (I don't know if that is true or not. A better example would have been my tenure at a company where it was becoming harder and harder to find Tcl developers, hence the switch to Java. But that said, it was still a very expensive conversion.) pc On 9/27/07, Giles Roadnight <[EMAIL PROTECTED]> wrote: > > I am leaving my current job in about a month and a suggestion has been > made that as I am leaving it would be better to re-write our flex / > coldfusion sites in jsp and java as that is what the larger company as > a whole uses. > > I need some couter arguments but don't know enough about Java. > > Replacing coldfusion with jsp is less of an issue but I Think that > Flex is very well suited for the front end. > > The site I've worked with most is used for managing customer accounts > and viewing information about them. There are screen for ssearchign > for accounts, setting up accounts with e-mail lists and a lot of reports. > Basically most of the site loads data and displays it in datagrids. > > What arguments can we use to convince people that flex is the way to > go rather than jsp / java? > > Thanks > > Giles > > >
