WebORB 3.6 for .NET is available
If you're working with the .NET version of our product, we have some news for you. There is a new release with some important features as well as bug fixes. See below for details:
- Support for Silverlight client - Includes client-side component with remoting APIs, code generator integrated into the management console as well as a command line code generation utility. Silverlight integration makes it super simple to invoke methods on remote objects as well as SOAP/REST web services. Btw, Silverlight integration works across all WebORB implementations thus you can connect Silverlight with .NET, Java, PHP and soon ColdFusion components.
- Support for server-to-server AMF invocations - Previous release made it possible to do server-to-server (or process-to-process if you will) invocations via RTMP. With 3.6 you can accomplish the same using AMF over HTTP. This should allow cross-platform integration where .NET can invoke Java or native .NET apps can call each other using simple and intuitive API without all the complexities associated with cross process integration.
- WebORB Visual Studio templates - Many of you asked for it and we listened. The product installer registers Visual Studio templates with your installation of VisualStudio 2005 and 2008 (whichever you have installed). The templates are available for C# and Visual Basic. There are two types of templates: one to create WebORB-enabled website projects and the other is for WebORB-enables class libraries. We put together a few screencasts demonstrating the templates in action:
Using WebORB Visual Studio templates - Part 1
Using WebORB Visual Studio templates - Part 2 - Custom MSMQ queue factories support - When using Producer/Consumer APIs with the messaging destinations connected with MSMQ, you may have a scenario when you need to construct instances of the queue in your own code. WebORB now supports custom queue factories to support this use-case. See the comments in WEB-INF/flex/messaging-config.xml (the <queuefactory> element)
- Class mappings between abstract generic collections and concrete implementations - Suppose you have a remoting method that declares an abstract generic argument:
public void processOrders( IList<Order> orders )
{
}
Since the argument is an abstract type, WebORB would need to know what concrete generic implementation should be used for that IList. The new release provides a way to establish mappings between abstract generic types and a concrete implementation. See <abstractclassmappings> section in weborb.config for more details. - Bug fixes:
- Fixed a bug with reference serialization. The error was resulted in a message "Error #2006: The supplied index is out of bounds"
- Fixed a bug with AJAX remoting and Firefox 3
- Fixed a bug with serialization of very large data sets
- Fixed a bug with passing credentials in AJAX invocations












