WebORB for Java is now GA

I am happy to report that WebORB 2.0 for Java is now GA! The product is available for immediate download. Here's what you will find in 2.0:

• Major Message Server enhancements.
• Improved client side APIs
• Support for both AJAX and Flash clients
• Universal message delivery. Message Server can deliver any message type (primitives, strings, complex types, arrays) to the supported clients. Messages get automatically formatted to the client environment
• Full documentation (client API, server architecture)
• WebORB Standard Edition license generation is available to the public. Registered users can generate their own WebORB Standard license keys.
• Safari 2.0 support. The Rich Client System has been fixed to work on Safari. All AJAX examples now work on all major browsers.
• Date and array serialization for the AJAX clients has been fixed
• Serialization of circular object references in returned complex types has been fixed.
• Serialization of returned singleton objects has been fixed.
• Added QuickStart guide for ColdFusion Components (CFCs) to the user guide.
• Multi-protocol support. WebORB architecture allows pluggable protocol handlers. There are 2 built-in implementations: WOLF (Web Object Literal Format) - an XML-based protocol for handling AJAX requests and AMF (Action Message Format) - binary protocol developed by Macromedia for Flash-based clients.
• Rich Client System. WebORB includes a set of APIs to simplify object binding and invocation process. In the future the APIs will include support for dynamic widget generation.
• Integration with BlueDragon by New Atlanta and support for ColdFusion Components.
• Ability to map client classes to the server ones and vice versa.
• Type adaptation improvements. Added support for conversion of string-based arguments to the numeric types
• JDBC Integration improvements. Changed to use column labels instead of column names.
• WebORB for Java supports Development Mode. If license file cannot be found, WebORB for Java will respond to the requests only from 1 IP address. In addition to the IP limitation, the server will perform a shutdown after 3 hours of operation.
  

We would like to solicit your feedback on what you would want to see in the next release. We're looking into implementing the new AMF protocol and will simplify integration with Flex 2.0. If you have any suggestions please feel free to share them with us.