Midnight Coders Extends WebORB for Java to Flex Clients

Discussions

News: Midnight Coders Extends WebORB for Java to Flex Clients

  1. Midnight Coders has announced immediate availability of a new version of WebORB for Java. This edition is ideal for Rich Internet Application (RIA) developers who need to rapidly connect Flex, Flash and AJAX clients to Java backend server environments and require more than the standard features and functionality found in competing solutions. WebORB for Java reduces the barrier to access for any sized organization and provides a complete set of tools enabling transparent connectivity between Flex, Flash and AJAX client applications and Java-powered backend systems. The product is a full-featured alternative to Adobe’s Life Cycle Data Services and includes remoting, data management and bi-directional messaging support for Flex clients. Additional features not available in any of the competing solutions include: powerful management console, service browser, and code generation tools. Midnight Coders is rolling out a suite of support plans for all product editions. WebORB for Java can be downloaded for free with registration at www.themidnightcoders.com.

    Threaded Messages (9)

  2. BlazeDS[ Go to top ]

    As of Tuesday Adobe now has their own open source alternative to LiveCycleDS, BladeDS. http://www.adobe.com/aboutadobe/pressroom/pressreleases/200712/121307BlazeDS.html How does WebORB compare with BladeDS?
  3. Open Source[ Go to top ]

    http://hessian.caucho.com/#Flash Single Jar needed, cross platform and also Comet. .V
  4. Integration with Seam[ Go to top ]

    Looks very cool. But while the Spring integration seems straightforward, does anyone have insight on how this product would interact with Seam-managed components on the server-side or Seam Remoting on the client-side? Thanks.
  5. Re: Open Source[ Go to top ]

    Have you used both of them ? WebOrb is 10 times easier to use than Hessian and 1000 times more powerful. You simply can't compare them. And WebOrb is a single jar. Plus it works exactly like advertised. (Made my first app in 10 minutes). It is probably more significant to compare WebOrb with BlazeDS. BlazeDS does not exist at this time in the form of a single jar to include into an existing app. You have to use the BlazeDS server, or include your app in the BlazeDS war. None of these solutions is acceptable for serious development. BlazeDS seems to have two qualities : it is open source, and much litterature will probably appear on the subject. However, this is not for tomorrow. WebOrb is working right now. What we would need to make it perfect is support for WebOrb in Spring.
  6. Flash Remoting and AMF[ Go to top ]

    @see http://wiki.java.net/bin/view/Javapedia/FlashRemoting @see http://en.wikipedia.org/wiki/Action_Message_Format @see http://www.graniteds.org/ @see http://labs.adobe.com/technologies/blazeds/ @see http://www.openamf.com
  7. GraniteDS[ Go to top ]

    I have been using GraniteDS for 6 months now and have been very happy with it. I have also used Adobe’s Life Cycle Data Services. Adobe’s Life Cycle Data Services are more feature rich, but if all you need is a solid AMF solution to connection Flex 2 to Java then GraniteDS does a great job. I have also worked with OpenAMF and find it to be behind the times, and lacking support for AMF3. I am interested to look at Adobe's new DS product.
  8. GraniteDS & Guice[ Go to top ]

    Also it was very easy to extend GraniteDS and create a factory to support Guice. Something that was not as straight forward in Red5 or OpenAMF.
  9. Same here... I've been very happy with GraniteDS. Nice integration between Flex and EJB3 (amongst others such as Spring and POJO's), including support for Hibernate's lazy instantiation.
  10. Here Franck Wolff comments about GraniteDS http://www.infoq.com/news/2007/12/more-on-rpc-in-flex-with-amf