EASC

EASC and enums

2009-01-28T03:03:01+01:00

Quite a while ago, we showed a workaround on how to work with enum types and the Remote API. A bit later, there was RFC #0132 which added real enum types to the XP Framework, but support for them in EASC was forgotten. This oversight has now been resolved.

RFC #0132: Enum support

2007-07-06T00:06:11+02:00

Scope of Change
There will be a defined way to write enums.

Rationale
Interaction with programming languages with enums, via EASC, for example.

Read the full RFC here

EASC and enum types

2007-07-05T23:31:09+02:00

While developing a client for a stateless session bean deployed on an enabled application server for a corporate project, I stumbled upon the need to pass a Java 5 enum. It was part of the signature of a remote method which was something along the lines of:
public CaseId createCase(FaxId faxId, Provider provider, String url);

The Provider is an enumeration type, declared as follows:
public enum Provider { FAXTOOL, ORDERING, TELECOM }

Because PHP does not support enums, we will have to find a workaround.

EASC.NET

2007-03-30T18:37:00+02:00

Following the Perl EASC implementation, I started developing a .NET implementation of the EASC protocol using the C# programming language. Its sourcecode is available at .

Update (2007-04-01): Fixed the last couple of outstanding issues and now have the first working implementation:

.NET EASC client in a Cygwin Shell, remotely invoking a unittest in Peking

Perl EASC implementation

2007-03-13T15:09:22+01:00

Besides XP4 and XP5, we're trying to get more languages to implement the EASC protocol. Yesterday, I committed a Perl implementation originally written by Marc to the XP SVN repository, testing and fixing bugs while doing so.

The experiment is available here:

RFC #0110: RemoteStackTraceElement

2007-02-28T14:42:51+01:00

Scope of Change
Stack trace elements representing stack frames on the remote side will be mapped to RemoteStackTraceElement objects instead of StackTraceElements.

Rationale

Ability to distinguish between local stack frames and remote stack frames.
Get rid of "php." prefix (e.g., in "php.java.lang.reflect.Method")

Read the full RFC here

RFC #0076: Transfer exception causes

2006-09-22T14:34:02+02:00

Scope of Change
An exception's cause will be transferred via EASC to the client.

Rationale
The remote.InvocationException's stacktrace is not really helpful in finding what may have caused a serverside exception.

Read the full RFC here

RFC #0062: HA-JNDI

2006-06-30T10:05:16+02:00

Scope of Change
The ability to pass a list of servers to the Remote API will be added.

Rationale
Load balancing and failover.

Read the full RFC here

Support for readResolve()

2006-05-03T11:37:00+02:00

The EASC's Java deserializer now supports correctly objects that have a readResolve() method. See Java Object Serialization Specification: 3.7 The readResolve Method for details.

EASC API moved

2006-02-14T14:37:51+01:00

The EASC API was moved in SVN from experiments/arena/easc to ext/java/easc. EASC has been in productive use for a couple of weeks here at Schlund+Partner and has proven to work.

RFC #0048: ESDL - Enterprise Service Description Language

2005-12-23T12:56:16+01:00

Scope of Change
A new API will be added to programmatically discover an Enterprise Bean's functionality.

Rationale
With this new API, Enterprise Bean client logic can be auto-generated.

Read the full RFC here.

EASC and transactions

2005-11-28T16:49:02+01:00

The EASC API now supports transactions. Apart from Java, where a remote transaction is begun by performing a lookup on UserTransaction as follows:

  UserTransaction tx= (UserTransaction)((new InitialContext()).lookup("UserTransaction"));
  tx.begin();
  // ...
  tx.commit(); // or tx.rollback();

..., the XP equivalent to this is more similar to the syntax used in the rdbms API:

  $remote= &Remote::forName('...');
  $tx= &$remote->begin(new UserTransaction());
  // ...
  $tx->commit(); // or $tx->rollback();