boxlang-application-descriptor

Explain Application.bx configuration for multi-app BoxLang runtimes.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-application-descriptor-ortus-boxlang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boxlang-application-descriptor
Source: https://github.com/ortus-boxlang/skills/tree/main/boxlang-developer/application-descriptor
Command: npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-application-descriptor-ortus-boxlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and debug Application.bx behavior for multi-app environments, including app discovery, nesting, and per-app isolation, with lifecycle events and per-app settings.

Core Features & Use Cases

  • App discovery & nesting: locate the nearest Application.bx and isolate app memory, sessions, and settings per app.
  • Lifecycle management: define onApplicationStart, onRequestStart, onError, and other callbacks to control app lifecycle.
  • Pseudo-constructor settings: configure per-app identity, timeouts, and environment via this.* fields.
  • App-scoped schedulers and watchers: wire per-app schedulers and file watchers using this.schedulers and this.watchers.
  • Mappings and javaSettings resolution: manage mappings and Java configuration resolution per application context.

Quick Start

Create an Application.bx example that defines per-app settings and lifecycle hooks to demonstrate multi-app isolation and app-scoped wiring.

Frequently Asked Questions about boxlang-application-descriptor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure multi-app isolation in BoxLang using Application.bx?

Multi-app isolation in BoxLang is configured using Application.bx by locating the nearest descriptor file and isolating app memory, sessions, and settings per app context.

How do I define lifecycle callbacks like onApplicationStart in a BoxLang application?

BoxLang lifecycle callbacks like onApplicationStart, onRequestStart, and onError are defined directly within Application.bx to control multi-app lifecycle events and request processing.

Can I set up app-scoped schedulers and file watchers in BoxLang?

App-scoped schedulers and file watchers in BoxLang are wired directly through the this.schedulers and this.watchers fields inside the Application.bx descriptor.

How do I manage per-app mappings and javaSettings resolution in BoxLang?

Per-app mappings and javaSettings in BoxLang are managed through the Application.bx descriptor to resolve Java configuration and path mappings within each isolated application context.

What are the frontmatter requirements for a BoxLang Application.bx descriptor?

The BoxLang Application.bx descriptor enforces specific frontmatter requirements and pseudo-constructor settings to configure per-app identity, timeouts, and environment via this.* fields.