import { ServiceBusClient } from '@azure/service-bus';
import { SbServerOptions, SbSubscriberRoutingContext } from '../interfaces';
import { SbSubscriberMetadata } from '../metadata-framework';
import { SbSubscriberRouter } from '../routing';
import { SbConfigurator } from '../management';
import { SbChannelManager } from '../resource-manager';
import { SbLogger } from '../utils';
import { SbErrorHandler } from '../error-handling';
export declare class SbServer {
    private readonly options;
    private readonly channelManager;
    readonly client: ServiceBusClient;
    readonly errorHandler: SbErrorHandler;
    readonly configurator?: SbConfigurator;
    readonly id?: string;
    sbLogger: SbLogger;
    protected router: SbSubscriberRouter;
    private routeContext;
    private routesToCommit;
    constructor(options: SbServerOptions, channelManager: SbChannelManager, client: ServiceBusClient, errorHandler: SbErrorHandler, configurator?: SbConfigurator);
    createRouteContext(): SbSubscriberRoutingContext;
    registerRoute(key: string | symbol, subscriber: SbSubscriberMetadata, instance: any): void;
    commitRoutes(): Promise<void>;
    destroy(): Promise<void>;
    /**
     * Store routing instruction for commit in a later phase of the initialization of the server.
     * Some logic is applied on the order that the server will commit all routes, the order of appending routes is
     * not guaranteed to be the order they register.
     *
     * For example, a subscription with a topic provision of `verifyCreate` will be bumped to the top of the list so it
     * can run before all other subscriptions which might depend on that topic but do not provision it's creation.
     */
    private appendRoute;
    private logRoute;
}
//# sourceMappingURL=service-bus-server.d.ts.map