Adding any of SAP datahub integration extension in localextensions.xml leads to build error with root cause Extension doesn't specify a path and no scanned extension was matching the name.
If someone uses custom tomcat for hybris, be aware that latest version of Tomcat 8.5.32 is not compatible with all versions of hybris and datahub due to implementation in Tomcat of Java EE v.8 specification(EE 5.3.3), which defines that deployment should fail if the lookup element of an annotation or the lookup-name element in a deployment descriptor entry does not specify a name with an explicit java: namespace. This breakable changes was added in apache tomcat commit.
Smartedit works perfectly on local environment, but after deploying on development environment (which is deployed with CI/CD pipeline) smartedit stops responding with endless loading.
OOTB hybris provides ant unittests command to run unit and integration tests, which are pretty low level and requires additional configuration to simplify run and result collection for DevOps. Below you can find configuration for buildcallbacks.xml, which you can just copy-paste into any hybris project (version 6.0+) and significantly simplify DevOps job required for setup of CI/CD pipeline.
As a Team Lead I want to see a clean git repository with branches, which are currently in development and not to see list of 3000+ branches, which was created from the first day of the project. Manual investigation and removing of obsolete branches will take ages, so I created few bash scripts, which will do the work automatically.
Starting catalog synchronization with CatalogVersionSyncJob in a bussiness process action leads to “Error in worker SyncWorker : Entity not found ( pk = 8794627343487 name = ‘de.hybris.platform.persistence.processing_CronJob’ type code = ‘501’ db table = ‘cronjobs’)”. I didn’t find a way to fix such behaviour of syncing inside business process action, but I resolved this issue by triggering event from process action and running SyncJob in event listener. For me sync performs well only via SetupSyncJobService, performing job via CatalogSynchronizationService causes exception in SyncWorker.
Sometimes simple tasks like “On base product price change also change price for all its sub products” can lead to long nights of debugging and seeking of workarounds. Sounds like this task should be easy for implementation. Create PrepareInterceptor, check if price was changed with InterceptorContext.isModified() method, iterate all sub products and put the new price.