coldbox-proxy

What problem does it solve?

Expose ColdBox application event handlers to remote, non-HTTP callers so external protocols like SOAP, Flex/AIR, event gateways, or direct CFC remoting can invoke application logic without relying on the HTTP request cycle.

Core Features & Use Cases

• Proxy pattern: create domain-focused proxy CFCs that extend coldbox.system.remote.ColdboxProxy to mediate remote calls into ColdBox events.
• Request bridging: use process() to merge incoming arguments into the request collection and return handler results directly to remote callers.
• App mapping and interception: configure COLDBOX_APP_MAPPING when the app is not at webroot and use the preProxyResults interception point for logging, transformation, or auditing.
• Use case: publish a SOAP or Flex endpoint that calls existing ColdBox handlers for CRUD operations while keeping business logic inside handlers.

Quick Start

Create a remote proxy CFC that extends coldbox.system.remote.ColdboxProxy, set arguments.event to the target handler, and return super.process with the argument collection to expose the handler to non-HTTP callers.