db4o

IConfiguration.AddAlias Method 

adds a new Alias for a class, namespace or package.

void AddAlias(
   IAlias alias
);

Remarks

adds a new Alias for a class, namespace or package.

Aliases can be used to persist classes in the running application to different persistent classes in a database file or on a db4o server.

Two simple Alias implementations are supplied along with db4o:
- Db4objects.Db4o.Config.TypeAlias provides an #equals() resolver to match names directly.
- Db4objects.Db4o.Config.WildcardAlias allows simple pattern matching with one single '*' wildcard character.

It is possible to create own complex Db4objects.Db4o.Config.IAlias constructs by creating own resolvers that implement the Db4objects.Db4o.Config.IAlias interface.

Four examples of concrete usecases:

// Creating an Alias for a single class
Db4o.configure().addAlias(
  new TypeAlias("com.f1.Pilot", "com.f1.Driver"));


// Accessing a .NET assembly from a Java package
Db4o.configure().addAlias(
  new WildcardAlias(
    "com.f1.*, F1RaceAssembly",
    "com.f1.*"));


// Using a different local .NET assembly
Db4o.configure().addAlias(
  new WildcardAlias(
    "com.f1.*, F1RaceAssembly",
    "com.f1.*, RaceClient"));


// Mapping a Java package onto another
Db4o.configure().addAlias(
  new WildcardAlias(
    "com.f1.*",
    "com.f1.client*"));


Aliases that translate the persistent name of a class to a name that already exists as a persistent name in the database (or on the server) are not permitted and will throw an exception when the database file is opened.

Aliases should be configured before opening a database file or connecting to a server.

See Also

IConfiguration Interface | Db4objects.Db4o.Config Namespace