Hot Off The Press!  We're hiring talented Flex coders.  If you are looking for a job, please Visit our Blog to find out how to apply.  


WebORB for .NET (Beta 2) Is Here!

Last month we introduced WebORB for .NET (Beta 1) and since then have been hard at work refining the product for certified production release.  For those who have worked with this new version and provided feedback, we are very grateful.  Your feedback has helped us identify and fix the bugs reported to us in our Bug Tracking System.  We not only have fixed those bugs, but we have also added a few improvements and some more new features.  This is what you can expect in this new Beta version (references are to notes in Bug Tracking System):


  • Added code generator for Java clients. Generated code allows invocation of .NET services from Java (WONET-106)
  • Added support for Spring.NET objects. The support includes service browser which visualized all deployed Spring.NET beans, code generators, invocation test drive and a special invocation handler of Spring.NET objects. (WONET-108)
  • Support for constants in the generated code. All code generators will now create client-side code for the constants declared in the .NET services. Currently constant support is available only for the value object classes. (WONET-102)
  • Graphical destination management. There is a new configuration panel in the management console available under the Server Configuration tab. The panel enables full management of the remoting destinations (the ones declared in remoting-config.xml). Using the console you can add new destinations, delete and edit existing ones. (WONET-105)
  • Support for dynamic destinations for the Flash Builder plugin. WebORB can now create dynamic destinations for all deployed classes. The destinations will immediately show up in the Flash Builder plugin for WebORB. (WONET-88)

Bug Fixes

  • Fixed problems with logging configuration and display of the log file in the management console. (WONET-114)
  • WebORB now recognizes the code deployed through the special App_Code directory (WONET-33)
  • Flash Builder plugin has been updated to handle edge-case scenarios. The installer and the plugin are significantly more stable.
  • Fixed problem with stored procedure argument validation in WDMF (WebORB Data Management for Flex) to avoid collisions with the reserved words.


Eventric Wins with Top Name Entertainers Using WebORB for PHP

EVENTRIC provides desktop and mobile applications that are used by some of the biggest entertainment acts in the world, such as the Dave Matthews Band, Bon Jovi, The Eagles and now Lady Gaga.  These applications are used to manage tour logistics in real-time.  This includes everything from travel and hotel to detailed technical production information and financial settlement.

According to Jason Hinkle, VP of Development, "The benefits we enjoyed from using WebORB for PHP include reduced development time, easier debugging, better performance, scalability and peace of mind knowing there was a commercial company we could turn to if needed.  Best of all, we don't really need to think about WebORB much, it just works!"




Dakota Software Helps EHS Managers Succeed in Ever-Changing Regulatory Environment Using WebORB for .NET

DAKOTA SOFTWARE created the ProActivity software suite of tools (Profiler, Tracer, Auditor and Scout) that help corporate Environmental, Health and Safety (EHS) managers to proactively align the sustainability interests of corporate management, site personnel and other stakeholders giving companies an opportunity to quickly understand applicable requirements and compliance issues and adjust accordingly. 

According to Brooks Pollock, Director of Software Development, "While we looked at many solutions, WebORB for .NET was the only one that met our requirements for speed, functionality and ease of installation.  In fact, WDMF really did provide us with massive savings in time.





Data push is a mechanism of data delivery from server to the connected client applications. Data push between Java and Flex can be accomplished via HTTP polling or using a dedicated connection from the client program to the server-side process. The dedicated connection can use the RTMP protocol supported by Flash and Flex and also implemented by WebORB for Java. The example we're providing uses the latter approach. This example establishes a connection from a Flex client to the WebORB for Java server process. The server-side code schedules a timer task to push a Java object to all connected clients. When the client program receives the object sent by the server it updates the user interface with the received information.

This example’s server-side code runs inside of the WebORB server. For RTMP applications, WebORB requires a Java class which is the main handler of all events and actions for the given messaging application.  VIEW THIS EXAMPLE and source code on our Blog.