WCMUsePojo can be used in AEMasCS based project

[george6]

Hi Team,

One of the project in AEMasCS is still on WCMUsePojo . Is it recommended to move to SlingModel. How long WCMUsePojo will be supported by Adobe?
(The project development started only 2023 but the Vendor using WCMUsePojo, instead of SlingModel )

Thanks,
Geo

[arunpatidar · Accepted solution]

Hi @george6 
The WCMUsePojo is not deprecated yes, you can check the sdk api.

https://javadoc.io/doc/com.adobe.aem/aem-sdk-api/latest/com/adobe/cq/sightly/package-summary.html

However, Adobe Cloud Manager Pipeline may raise an quality issue 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi... 

[george6]

Thanks @arunpatidar 

[HrishikeshKa]

Hi @george6 ,

Yes, WCMUsePojo can be used in an AEM as a Cloud Service (AEMasCS) based project. However, it is recommended to use Sling Models instead of WCMUsePojo for several reasons:

1. Sling Models are more efficient than WCMUsePojo as they use fewer resources and provide better performance.
2. Sling Models are easier to test as they follow the standard Java POJO (Plain Old Java Object) pattern.
3. Sling Models provide better support for dependency injection, making it easier to manage dependencies between components.

Adobe has not announced any plans to deprecate or remove WCMUsePojo from AEM. However, Adobe recommends using Sling Models for new development and migrating existing code to Sling Models whenever possible.

If the project development started in 2023 and the vendor is still using WCMUsePojo instead of Sling Models, it is recommended to migrate to Sling Models as soon as possible to take advantage of their benefits.

[george6]

Thanks,@HrishikeshKa