coldbox-proxylisted

# ColdBox Proxy ## When to Use This Skill Use this skill when you need to expose your ColdBox application to non-HTTP callers: SOAP web services, Flex/AIR binary protocol, ColdFusion event gateways, or any remote CFC invocation that bypasses the normal HTTP request cycle. ## Core Concepts - **Proxy** — A CFC that extends `coldbox.system.remote.ColdboxProxy` and acts as an interface between external callers and the ColdBox event model - **`process()`** — Executes a ColdBox event from within the proxy; all extra arguments are merged into the request collection - **`loadColdBox()`** — For loading an external ColdBox app whose `Application.cfc` is not in the webroot - **`COLDBOX_APP_MAPPING`** — Required in `Application.cfc` when the ColdBox app lives in a sub-folder and uses non-HTTP protocols (Flex/AIR, gateways) - **`preProxyResults`** interception point — Fires right before proxy returns results; ideal for logging, transformation ## File Organization Create a `remote/` folder in your application root and place one or more proxy CFCs there, organized by domain: ``` /Application /remote UserProxy.cfc OrderProxy.cfc ``` ## Basic Proxy Structure ```javascript // remote/UserProxy.cfc component extends="coldbox.system.remote.ColdboxProxy" { /** * Get a list of users * @page Page number * @limit Records per page */ array function getUsers( numeric page = 1, numeric limit = 25 ) { arguments.event = "api.users.index"; va