boxlang-application-descriptor

You can configure application lifecycle callbacks in BoxLang by defining start, end, session, and request handling events within the Application.bx file. This ensures correct startup and processing behavior across multi-application environments.

Scope isolation in BoxLang separates runtime environments by assigning distinct this.name values in Application.bx. This mechanism ensures isolated application, session, and request scopes for modular or multi-tenant architectures.

Debug application discovery and startup issues in BoxLang by verifying app discovery paths, checking session hooks, and validating async scheduler or watcher setup configurations within your Application.bx lifecycle settings.

Yes, you can run multiple isolated applications within a single BoxLang runtime by setting distinct this.name properties in each Application.bx file, which configures isolated environments for multi-tenant or modular setups.

Session hooks may not trigger during BoxLang application startup if app discovery fails or Application.bx lifecycle settings are misconfigured. Verify your application scope isolation settings and async watcher setup to resolve the issue.