From Java to Flex

Discussions

Blogs: From Java to Flex

  1. From Java to Flex (7 messages)

    Is Flex the right choice for enhancing your Java EE application interface's ? How steep is Flex's learning curve if you have a Java background ? This blog entry tries to answer these and other questions.
    Flex builds on the advances made in the Java/J2EE community over the last decade. New Java converts to the Flex programming model will find the framework, language, and tools easy to learn, as there is a familiarity in the Flex IDE and the language structures, like the Flex Collections API. The Flex development tools offer the clearest link for current Java developers. The Flex IDE is built on Eclipse, which can be used as the stand-alone Flex Builder product or as an Eclipse plug-in. Virtually all Java developers have had some exposure to the Eclipse development environment. This is a huge benefit that speeds and enhances the learning process. But, at this point in the discussion, many ask, "Why not stick with just Java?" There are many compelling reasons for the Java community to look outside of Java for better technologies for building user interfaces, besides the strong value proposition offered by Flex. Bruce Eckel has dubbed this idea, "Hybridizing Java," where we keep the good parts of Java and replace the weaker ones with non-Java technologies
    Read the complete entry on Java to Flex: http://flexexamples.blogspot.com/2007/12/from-java-to-flex.html

    Threaded Messages (7)

  2. From Java to Flex[ Go to top ]

    I read this in Jon's full post "Flex also provides API's for multiple methods of integrating with backend services, including LiveCycle Data Services ES (Data Services), Web Services, and HTTP" and wanted to add WebORB for Java to this list. The following describes some of the features provided by this latest release of WebORB for Java: 1. Flex and Flash remoting support. Flex clients can use the RemoteObject API/MXML to connect to the deployed Java applications. Flash clients can use Flash Remoting components or the NetConnection API. 2. Product supports POJOs, Spring Beans, EJBs, Groovy objects, XML web services and custom object types. You can easily target any of the listed types from Flex or Flash clients. 3. The product can be deployed into any Java EE server or servlet container. 4. No additional configuration required to publish Java classes as remoting services. Classes can be deployed into WebORB just by copying them into WEB-INF\classes or WEB-INF\lib folders (packaged in JARs). 5. Management console. WebORB for Java features a Flex-based management console which includes everything to get started with the product. There are plenty of examples, service browser, invocation test drive and service-level security. The other thing developers will appreciate is that WebORB for Java is FREE. To download, simply go to: http://www.themidnightcoders.com/weborb/java/
  3. Re: From Java to Flex[ Go to top ]

    Flex is a good idea, but closed proprietary code and absence of automated testing puts it on a sideline.
  4. Original Article[ Go to top ]

    No idea why this content is on flexexamples.blogspot.com. You can find the original at: http://www.adobe.com/devnet/flex/articles/java_flex.html
  5. Re: From Java to Flex[ Go to top ]

    Check out the following for discussion on the proprietary nature of Flash: http://www.infoq.com/news/2007/12/top-10-flex-misconceptions.
  6. Re: From Java to Flex[ Go to top ]

    Not quite. There is a BSD-licenced unit testing framework for Flex called FlexUnit, which is quite similar to JUnit. Naturally, the number of testing tools at the moment is quite limited, but the commercial Flex Builder will offer profilers etc. in Flex 3. When you combine the Flex Builder and FlexUnit, you are atleast part of the way there and hopefully we'll see more automated testing solutions in the future. On the closed source issue, Flex 3 SDK is going to be open source under the MPL. This includes the Flex framework and the compilers and debuggers. For more information, visit the Flex open source FAQ
  7. Flex testing[ Go to top ]

    Investigating automated testing for flex, we found an open source Ruby solution called FunFX (http://funfx.rubyforge.org/). My initial impression is extremely favorable. It has a simple, powerful interface, and seems ideal for functional testing. It integrates easily with RSpec and Test::Unit, and the author is very active on his blog.
  8. Re: From Java to Flex[ Go to top ]

    all links given above are very informative, here i have tried to provide more information. http://en.wikipedia.org/wiki/Adobe_Flex kindly go through this link, you can get more information for the same. http://www.viteb.com