Hello,
CRISP API documentation states that it’s possible to configure CISP’s Spring Application Context XML definition as an XML file within the Site tier (e.g, site/components/src/main/resources/META-INF/hst-assembly/addon/crisp/overrides/custom-resource-resolvers.xml).
Is it possible to place such definition as an XML file within CMS tier? If so, where it should go?
Regards,
Rafał
13.4.2
, @woonsanko. Soon to be upgraded to 14.
Could you try to add the bean configuration in cms-dependencies/src/main/resources/META-INF/hst-assembly/addon/crisp/overrides/custom-resource-resolvers.xml
?
Woonsan
1 Like
I’m assuming that cms-dependencies
is another Maven module, adjacent to cms’, 'site`, etc.?
I’m asking, because my project doesn’t have one.
If so, I can presumably find an example of such module if I create vanilla project from Maven artefact of some recent version?
We started with version 12.0.1
couple years back which could probably explain why there is no cms-dependencies
module.
You can try to add cms/src/main/resources/META-INF/hst-assembly/addon/crisp/overrides/custom-resource-resolvers.xml
instead. cms-dependencies
was added in the later versions and the cms
sibling module includes that as a dependency.
I’m happy to report that I did just that and that it works!
Thanks a lot, @woonsanko, you were most helpful and your responses were blazing fast!
Kudos to @Shane_Ahern, as well who suggested the same thing as well, in the meantime.
Thank you both
Cheers! (holding my crisp-tasting hard apple cider)
1 Like