[SLING-4083] Sling Models: Enable SlingObject injector to inject all context objects when a request is attached to the current thread

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: Sling Models Implementation 1.1.0
• Component/s: Extensions
• Labels: models
• Assignee: Unassigned
• Reporter: Stefan Seifert
• Created: 21/Oct/14 16:10
• Updated: 21/May/15 13:19
• Resolved: 09/Dec/14 12:56

Description

The SlingObjectInjector should support injecting all context objects (Resource, ResourceResolver, Request, Response, SlingScriptHelper) always, and not only when derivable from the current adaptable.

in sling models 1.1.0 the injection of most of those objects fails e.g. when adapting from a resource resolver because the request object is not available. thus if a developer uses a @SlingObject annotation he has to be aware of those implementation details when the context objects are available and when not. if used from a scripting language light Sightly which first tries to adapt a model from the current resource, and after that from the current request things get worse.

if a model is adapted in a thread initiated from a request all injections should be always supported.

Issue Links

• is related to: SLING-4734 Sightly should try to instantiate Sling Models first via SlingHttpServletRequest then via Resource and not the other way around