My colour is ${logic.colour ? logic.colour : 'not important'} and I'm from ${logic.year}
the object would be able to access the parameters like:
use(function() {
'use strict';
var colour = this.colour || '';
var year = this.year || new Date().getFullYear();
return {
colour: colour,
year: year
}
});
#### Caveats
Since these scripts are evaluated server-side, by compiling JavaScript to Java, you need to pay attention when comparing primitive objects using the strict equal operator (`===`) since comparisons between JavaScript and Java objects with the same apparent value will return `false` (this also applies to the strict not-equal operator - `!==`).
Assuming the following HTL script:
| Use Provider |
Advantages |
Disadvantages |
| Sling Models Use Provider |
- convenient injection annotations for data retrieval
- easy to extend from other Sling Models
- simple setup for unit testing
|
- lacks flexibility in terms of component overlaying, relying on
service.ranking configurations; this was solved for Sling Models 1.3.0 by SLING-5992
|
| Java Use Provider |
Use-objects provided through bundles:
- faster to initialise and execute than Sling Models for similar code
- easy to extend from other similar Use-objects
- simple setup for unit testing
Use-objects backed by Resources:
- faster to initialise and execute than Sling Models for similar code
- easy to override from inheriting components through search path overlay or by using the
sling:resourceSuperType property, allowing for greater flexibility
- business logic for components sits next to the HTL scripts where the objects are used
|
Use-objects provided through bundles:
- lacks flexibility in terms of component overlaying
Use-objects backed by Resources:
- cannot extend other Java objects
- the Java project might need a different setup to allow running unit tests, since the objects will be deployed like content
|
| JavaScript Use Provider |
- allows JavaScript developers to develop component logic
- can be reused through the dependency mechanism provided by the
use function
|
- harder to test and debug, relying mostly on end-to-end testing and console logging
- slower to execute than both Sling Models and Java Use-API objects
|
| Script Use Provider |
- allows the usage of Use objects evaluated by other Script Engines available in the platform
|
- like in the case of the JavaScript Use Provider, the performance is influenced by the Script Engine's implementation
|