Blog

Luis Majano

March 11, 2016

Spread the word


Share your thoughts

In this entry I will go over how to leverage ColdBox's Modular architecture to RESTFul routing. In ColdBox, every module's ModuleConfig.cfc you create has two important facets for building RESTFul services: 1) The this.entryPoint and the 2) routes structure in the configure() method.

If you are creating ColdBox applications using modules, then you will benefit with the capability to nest entry points so they can match to nested sub-modules. Let's say you have the following module structure:

+modules
  + api
    + security
    + data

Then we can create a URL hierarchy to match any sub-module of the api module by leveraging the EntryPoint and the routes configuration.

Parent EntryPoint

The entry point in any module you create will become the pattern argument to a addModuleRoutes() call in the ColdBox routing services. This is important as any rules that apply to URL patterns applies to the entry point, e.g. you can use expressions, nesting, etc.

addModuleRoutes( string pattern, string module, [boolean append='true'] ) 

In the api module our entry point will simple become:

this.entryPoint = "/api";

This means that any incoming URL that has the /api prefix will be routed to the API module.

Parent Routes

The routes structure in the configure() method will be used to declare routes for the module you are building. You can declare all routing inline in this structure or actually declare an array of locations of routing CFM templates to load. By default, every module comes with a single route declared:

routes = [
    { pattern="/:handler/:action?" }
];

In the parent api module you can now register the sub-module entry points so if the parent receives a URL request, the module will then re-direct it to the sub-module:

routes = [
    { pattern="/security", moduleRouting="security" },
    { pattern="/data", moduleRouting="data" }
];

That's it. We have now created sub-module routing by leveraging a URL pattern argument and the moduleRouting argument which dictates to what module to re-direct the routing discovery. This will empower you to create very expressive URL entry points in a modular fashion.

Recent Entries

Introducing numeric placeholders in BoxLang source!

Introducing numeric placeholders in BoxLang source!

Introducing Numeric Placeholders in BoxLang

We're excited to announce a new addition to our BoxLang parser—a feature that draws inspiration from several other languages but fits naturally within BoxLang. The conversation around which features from other languages m...

Maria Jose Herrera
Maria Jose Herrera
September 18, 2024
BoxLang 1.0.0 Beta 14 Launched

BoxLang 1.0.0 Beta 14 Launched

In this release, we are excited to introduce several new features and enhancements aimed at improving functionality and user experience. These updates include the creation of immutable query types, new server keys to aid on CLI tooling, and methods to identify runtime initiation modes.

Additionally, we've added an event announcement for dump rendering to enable better integration with external listeners. Read on to learn more about these features and how they can benefit your workflow.

Code Strong!

Luis Majano
Luis Majano
September 13, 2024
Are you attending Adobe CFSummit 2024?

Are you attending Adobe CFSummit 2024?

If you are attending the Adobe ColdFusion Summit 2024, this is what you need to know: As always, Ortus Solutions will be sponsoring this years event as Silver Sponsors, we are excited to meet all the new attendees and old friends of the community of Coldfusion developers

Maria Jose Herrera
Maria Jose Herrera
September 10, 2024