Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


A presentation was made by Mike on February 16th 2010 about ERREST. The presentation was recorded and made available here :

It's also listed on the Screencasts page on and in the podcasts RSS feed.

Mike also did a session about it at WOWODC West 2009, you can buy this session in the Community Store.

Class names vs entity names

A question was asked about situations where your EO class name is different from your entity name. Mike's answer was :

Everything internally is based on entity names. Your class name has very little to do with things other than your own source code. So for example:

routeRequestHandler.addDefaultRoutes("SamsSchool"); // School.ENTITY_NAME

Regardless, you will always have:
public class SamsSchoolController extends ERXDefaultRouteController {
School school = (School) routeObjectForKey("samsSchool");

When those slides say "EntityName", they mean it (smile)

If you want to call it "School" to the outside, add this before you register the default routes for "SamsSchool":

ERXRestNameRegistry.registry().setExternalNameForInternalName("School", "SamsSchool"); // "School", School.ENTITY_NAME

After adding this, no other code changes. All you're saying is that the routes and type names that send over the wire should all say "School".

  • No labels