Professional Documents
Culture Documents
Data management code integrated into the Data Modeler and responsible
generator for creating client-side (ActionScript) and server-
X X side code to handle all database operations,
including data retrieval, creation of new records,
updating and deletion of existing records.
Runtime
Runtime server Runtime server provides support for RPC
infrastructure, marshalling and unmarshalling of
X X X X arguments/return values for remoting invocations,
messaging and streaming.
Custom Invocation pre- and Provides support for expanding the invocation
post- handling processing chain with custom code executed by
the container before and after specific method
invocation takes place. Pre/Post invocation handler
X can be plugged in using method attributes.
Enables developers to observe method
arguments, return value, and measure invocation
performance and control security.
Service life cycle management Controls how the remoting gateway manages
instances of the deployed services. Most common
schemes are “request”, “session” and
“application”, where instances are created once
for each request, session and application
X2 X2 X
respectively. Unlike other solutions, WebORB
allows to configure activation via class attributes,
Flex xml configuration files (channel configuration,
destination configuration) or by modifying
gateway URL on the client-side.
Custom service activation Provides a way to control service instance
management in a custom way. For instance
X creating pooled services can be accomplished with
this feature.
Pluggable service handler for The product supports the following service types
custom service types out of the box: POJOs, Spring beans, EJBs, Web
X services. WebORB provides an API to expand the
list of supported services using custom handlers.
Service aliasing Enables decoupling of server-side class names
X
from the client application.
Service factories Default mechanism for instantiation of remoting
services (POJOs for instance) is the default no-
argument constructor. For the scenarios when
X classes do not have such constructor, WebORB
supports the concept of service factories. A
factory is mapped to a class and is responsible for
creating instances of the class so invocations can
take place.
Argument factories Similar to Service Factories described above,
Argument factories are responsible for creating
X argument objects based on the data received from
client.
Abstract argument mappings When arguments of remoting service method
signature reference abstract types or interfaces,
X WebORB provides a way to establish mapping to a
concrete type to be used to represent the value.
For instance in the following method:
iExternalizable support X X X
Event logging Framework allows customizable logging categories
X X X
and supports multiple logging agents or loggers.
Data Management
Flex data management A framework for operating with data in a
framework distributed client/server environment. Must
X X support basic database operations (CRUD) and
client synchronization.
Integrated real-time data Delivers notification of data changes to the clients
(client) synchronization X X X that have (or would have) retrieved changed/new
data.
Conflict resolution X
Transaction (batch processing) X X
Data paging X X X
Lazy loading X X
SQL adapter/query execution X X X
Hybernate adapter X X X
Support for loading of related
X
entities
Supports multiple DBMS X X X
Offline application support Supports both data caching and local message
X X queuing.
1 - BlazeDS and LiveCycle DS support custom serialization only through the IExternalizable interface. Classes serialized in a custom way MUST provide a serialization
implementation both on the client and server sides.
2- The only way to control service life cycle with BlazeDS is by specifying scope in destination configuration.