Show all / Hide all

Is WebORB for Java an alternative to LiveCycle Data Services?

WebORB for Java offers many of the same features available in LCDS plus a lot more. The product provides remoting support and integration between Flex, Flash, Silverlight and AJAX clients and Java objects, EJBs, Spring beans, Groovy objects and XML Web Services. WebORB includes an implementation of Data Management functionality, significantly simplifying the process of creating data-driven Flex applications with Java backends. Additionally, WebORB includes unique features like comprehensive Flex-based management console, code generation tools, invocation test drive and ActiveRecord-based data management framework.

How compatible is WebORB with LiveCycle Data Services?

WebORB for Java is similar to FDS and supports three major subsystems: Remoting, Data Management and Messaging. WebORB for Java uses the same configuration files as FDS, implements the same binary protocols (AMF0 and AMF3) and exposes similar architectural concepts as destinations, channels and service adapters. From the Flex developer perspective, working with WebORB for Java is a process very similar to working with LCDS with an additional benefit of having a more streamlined development process. For example, deploying and exposing a Java class or a Spring Bean as a remoting service, would only require copying the class or JAR files into WEB-INF\classes or WEB-INF\lib directories.

Can I use Flex Builder or Flex SDK to develop Flex apps with WebORB?

Yes, WebORB integrates very well with both Flex Builder (both versions 2 and 3) as well as the Flex SDK. Flex developers can use the standard ActionScript API to communicate with server objects. This includes Flex remoting (RemoteObject), Flex data management (WDMF) and Flex messaging (Producer/Consumer or WeborbProducer/WeborbConsumer) MXML and API classes.

What is the cost of a WebORB license?

WebORB is available in both Community and Enterprise Editions.  The Community Edition is free and the Enterprise Edition can be purchased on a subscription or perpetual basis.  Please see Subscriptions or Production Support for pricing information.  

How do I get started with WebORB?

Download either the Community Edition or Enterprise Edition product and then familiarize yourself with the Getting Started Guide and Examples contained within your WebORB console.  If you'd like to shorten your learning curve, consider augmenting your download with some training classes.  Enterprise Edition customers have access to commercial support when they purchase a subscription license or buy production support.

Show all / Hide all

Do I need anything special on the client side to integrate with Java?

No, since WebORB handles all the client/server integration, your Flex application does not require anything special. In fact, you can use the same Flex client code to communicate with  .NET, Java, PHP, CF or Ruby (assuming your server application supports the same functionality).

Do my Java classes need to use any special APIs or dependencies on WebORB?

No, your server-side code can be 100% WebORB-free. Unless you require some advanced features, you do not need to use any special classes, interfaces or attributes. Your method arguments and return types can be standard Java classes, collections and interfaces or types from your application domain. WebORB will automatically handle all the translation between client objects and their server-side counterparts. You do not need to use any special base classes or attributes to expose your classes for remote access.

How does WebORB map client-side objects to the corresponding Java types?

The WebORB client/server type mapping system is one of the most powerful features of our product. WebORB intelligently adapts client-side objects to any corresponding server type. For example, if a Flex or Flash client sends a linear array, the server side type can be any linear Java collection or a custom array of application objects. Additionally, the developer can override default type mapping mechanism and map specific Java types to their corresponding ActionScript classes.

How can my Java application deliver errors and exceptions to the client side?

Delivering exceptions to the client application does not require any special programming techniques. Your Java application code can simply throw an exception and WebORB takes care of serializing it as a Flex/Flash fault event. Your client application also receives all the information the server code passed with the exception (error message, error code, stack trace).

Where can I find coding examples?

Your WebORB console contains many helpful examples.  You can also go to our Developer Zone for access to other helpful information.  Support Plan subscribers and Enterprise Edition subscribers have access to a rich online KnowledgeBase and support technicians as well.

Show me a basic example of Flex to Java connectivity.

The following example demonstrates basic invocation of a method in a Java class. Consider the following very basic Java class:

namespace com.acme.example;

class BasicService

{

  public String SayHello()

  {

    return "hello world";

  }

}

The following code can be used to invoke the SayHello() method shown above from a Flex client:

 

var ro:RemoteObject = new RemoteObject( "GenericDestination" );

ro.source = "com.acme.example.BasicService";

ro.SayHello.addEventListener( ResultEvent.RESULT, gotHelloResult );

ro.SayHello();

public function gotHelloResult( result:ResultEvent ):void

{

  Alert.show( “Server responded – “ + result.result );

}

Show all / Hide all

How can I deploy my Java application so Flex clients can consume its objects and services?

Deployment of a Java application is as simple as copying the class files into a WebORB-enabled Java web application (running in any Java EE server or servlet container). WebORB does not require any additional configuration changes and once copied over, you can start accessing your Java classes from a Flex client.

How can deploy WebORB into my existing Java application?

Deployment involves copying the WebORB jar  and configuration files as well as making a simple configuration change in web.xml to register the WebORB servlet. There are detailed instructions on deploying WebORB into an existing Java application.

I'm ready to deploy into production, what are my options?

You may deploy into production with either the Community Edition or the Enterprise Edition.  To ensure you are deploying with the most reliable, scalable and secure edition, we recommend you deploy with the Enterprise Edition.  There are several options available to fit any budget.  Please contact sales at 888-MYWEBORB, option 1 or sales@themidnightcoders.com if you would like to discuss your options.  (Note:  Distribution is not allowed under either the Community Edition or Enterprise Edition.  You must purchase an OEM license in that case.)

Why is it better to deploy into production with Enterprise Edition?

Enterprise Edition is the most reliable, scalable and secure integration and runtime solution available.  We're so sure about this that we are willing to certify the product's performance, scalability and security features, because we know they matter the most to you.  The Enterprise Edition subscription is also backed by commercial support and that gives you the peace of mind that we are there to help when you most need it.  If your name and business success depends upon the reliability of the applications you build, an Enterprise Edition subscription or support plan is the smart choice.

Am I allowed to distribute WebORB with my application?

There are a four ways to look at distribution:  (1) You could be distributing access to your application through a SaaS model.  (2) You could be creating a custom application that would be distributed to one customer for their own use.  (3) You could be creating an application that would be distributed to multiple customers.  (4) You could be creating an application that would be distributed in non-standard computing products.  Scenarios (3) and (4) require you to license WebORB under an OEM/ISV licensing agreement.  Please contact us if you are unsure if your distribution would require an OEM/ISV license.

Show all / Hide all

Automated exposure of the deployed classes sounds dangerous. How can I restrict access to my application?

WebORB supports a very powerful security system, which can limit access to the executable code at any level, starting with package names right down to a particular method declaration.

How can I secure my application to prevent unauthorized use?

There are two ways to configure code-level security – using the WebORB Management Console or through the product configuration file. Security restrictions can be applied to package names, classes and methods. Access to any of these can be restricted to users with particular credentials, or users accessing the application from a defined IP address mask.

Can I add my own authentication or authorization mechanism?

Yes, in fact, WebORB provides a rich extensibility mechanism for custom authentication and authorization implementations. Applications can be secured to authenticate users against a database or custom security domains.

How can my Flex client know if authentication failed?

When WebORB security restricts access to a secured method (or class, or namespace), WebORB delivers an exception to the client as a FaultEvent. To indicate a security-related error, the extendedData field of the Fault object encapsulated within FaultEvent is set to 401. As a result, your Flex application code can do a simple check as shown below:

public function handleFault( event: FaultEvent ):void

{

  if( Number( event.fault.extendedData ) == 401 )

  {

     // authentication failure logic goes here

  }

}

Can I use JDBC to fetch data from a database and display it in Flex?

Yes, WebORB contains special serialization logic to serialize JDBC java.sql.ResultSet objects as an array of complex types. Each complex type in the array is an object with fields corresponding to the column names. As a result, when the server code returns ResultSet, the client side can assign the return value as a data provider for the databindable components (DataGrid, List, etc). Server-side code does not need to include any WebORB specific code.

Show all / Hide all

Does WebORB support Flex Data Management Services (FDMS)?

WebORB currently implements a subset of the FDMS functionality. Applications can perform all four basic database operations (CRUD) using the mx.data.DataService API. Data destination classes can be registered in data-management-config.xml. Client applications can use mx.data.DataService class to perform fill and sync operations. Client synchronization and conflict resolution are made available in the Flex ActiveRecord implementation.

What is Flex ActiveRecord for WebORB?

Flex ActiveRecord for WebORB is Midnight Coders enhanced implementation of Flex Data Management Services functionality. It borrows some of the best ideas from the frameworks like Ruby on Rails ActiveRecord and Hibernate. The system provides a rich interface for all data related operations (data retrieval, construction, update and deletion). It supports transactions and can be easily extended with custom operations. The framework includes a powerful code generator for both ActionScript and .NET (C#/VB.Net) classes. The client-side API is very similar to the Rails’ ActiveRecord with support for dynamic, patterned methods. For more info, see the WebORB Blog.

Can I use JDBC to fetch data from a database and display it in Flex?

Yes, WebORB contains special serialization logic to serialize JDBC java.sql.ResultSet objects as an array of complex types. Each complex type in the array is an object with fields corresponding to the column names. As a result, when the server code returns ResultSet, the client side can assign the return value as a data provider for the databindable components (DataGrid, List, etc). Server-side code does not need to include any WebORB specific code.

Show all / Hide all

Does WebORB support Flex Messaging?

Yes, WebORB supports both Flex Producer and Consumer MXML/API (as well as our own WeborbConsumer/WeborbProducer) and provides integration with JMS. WebORB delivers messages published by Flex producers to a messaging destination. A destination can be configured to route published messages to a JMS topic/queue or use a pluggable routing logic. Flex consumers subscribe to a destination and become destination listeners. WebORB facilitates the delivery of all messages from a destination to all consumers. Additionally, WebORB can deliver any messages published by non-Flex producers (JMS publishers) thus providing integration between Flex and Java applications.

Does WebORB support real-time messaging?

WebORB contains an implementation of the Real-Time Messaging Protocol (RTMP). As a result, the product supports all the functionality delivered on top of RTMP, including support for Remote SharedObjects, client stream recording, video streaming, server-to-client invocations.

Can Flex application use Remote SharedObjects in WebORB?

Yes, WebORB includes support for remote SharedObject API. 

Can I send a message from a client to all other connected clients?

Yes, you can use the SharedObject API to perform a client-side function invocation from a client on all other clients connected to the same SharedObject.

Can I stream Flash video to a Flex/Flash client through WebORB?

Yes, WebORB supports FLV video streaming.