cn.vertxup.rbac.service.view

Interface VisitStub

All Known Implementing Classes:

VisitService

public interface VisitStub

Author:

lang

The Gold Rule for visitant

1. viewId + type + identifier + ( configKey = DEFAULT ) must return only one visitant ( Unique )
2. viewId + type + configKey ( User Input and UUID format ) must return only one visitant ( Unique )

The situation is as following:

1. view is abstract ( Bind to abstract identifier ), and the instance visitant could be divide into different by configKey here.
2. view is instance ( Bind to fixed identifier ), and the instance visitant could be divide into singleton one by configKey refer ( configKey = DEFAULT ) and identifier could distinguish between.

The tree for visitant searching processing:

Level1: type = XXX Level2: viewId = XXX ( contains role/user, resource ( uri + method ) ) Level3: 1. viewId = abstract, identifier = null 2. viewId = instance, identifier = fixed, configKey = DEFAULT Level4: configKey 1. configKey = DEFAULT ( Master visitant for identifier ) 2. configKey = UUID ( Master visitant for different identifiers ) 3. configKey = CODE ( This situation must be used with identifier at the same time )

Method Summary

Modifier and Type	Method and Description
io.vertx.core.Future<io.vertx.core.json.JsonObject>	fetchVisitant(String ownerType, String ownerId, io.vertx.core.json.JsonObject request)
io.vertx.core.Future<io.vertx.core.json.JsonObject>	saveAsync(io.vertx.core.json.JsonObject request, io.vertx.core.json.JsonObject view)

Method Detail

fetchVisitant

io.vertx.core.Future<io.vertx.core.json.JsonObject> fetchVisitant(String ownerType,
                                                                  String ownerId,
                                                                  io.vertx.core.json.JsonObject request)

saveAsync

io.vertx.core.Future<io.vertx.core.json.JsonObject> saveAsync(io.vertx.core.json.JsonObject request,
                                                              io.vertx.core.json.JsonObject view)