Cant we use ValueMapValue with @Model(adaptables=Resource.class) ? | Community

Level 6

Solved

Cant we use ValueMapValue with @Model(adaptables=Resource.class) ?

Forum|Forum|2 years ago
December 28, 2023
1 reply
1311 views

Hi Team

Cant we use ValueMapValue with @Model(adaptables = Resource.class) ?

Should it be with

@Model(adaptables = SlingHttpServletRequest.class

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by aanchal-sikka

Yes we can use ValueMapValue with both Resource and SlingHttpServletRequest. Infact, its the recommended way to access properties of a component

https://techrevel.blog/2017/03/18/sling-model-annotations/

Community Advisor

Accepted solution

Community Advisor

Yes we can use ValueMapValue with both Resource and SlingHttpServletRequest. Infact, its the recommended way to access properties of a component

https://techrevel.blog/2017/03/18/sling-model-annotations/

Aanchal Sikka

Level 6

Hi @aanchal-sikka I have doubt in below can u help to solve please ?

A custom component has one dialog field:

<Title

fieldLable=Title

name = ./title

sling:resourceType=granite/ui/components/coral/foundation/textfield

The developer needs to implement a Sling Model to perform a business logic on the authored value.
The developer writes the following HTL snippet.

<sly data-sly-use.display="com.adobe.aem.core.model.HelloWorldModelImpl">

<h1>${display.messageText}</h1>

</sly>

Do you observe any wrong in below code ?

@Model(Adaptable = Resource.class, defaultInjectionStrategy=DefaultInjectionStrategy.OPTIONAL))
public class HelloWorldModelImpl{
@ValueMapValue
@Named("title")
private String authoredVal;
private String messageText;

<relevant code>
}

Community Advisor

Community Advisor

Hello @jakecham

Thanks for sharing the relevant code snippets. Here are the improvements, please try once

@ValueMapValue needs to be added to each field in Sling Model. A model can have various types of fields, example OSGi Service and normal variables. Thus, every field which is a component property needs to be annotates individually

@ValueMapValue
@Named("title")
private String authoredVal;

@ValueMapValue
private String messageText;

Second, in the dialog you only have the "Title field". The messageText isn't part of it. Unless it is added to component in any other way (like manually), it would be null/empty.

Aanchal Sikka