Found the problem, an extra UrlBasedViewResolver bean is in place with viewClass JstlView and order 5. Because of this new UrlBasedViewResolver the BeanNameViewResolver is never reached. This is why we get HTTP Status 404 – Not Found.
change the mapping of the jsp servlet to /WEB-INF/Views/* so that the JSP servlet is only used for views, and leaves all other requests for the dispatcher servlet.
update the web.xml on webapp level
Try enabling these following properties in dxa.properties file
#adf.context.provider - Activates ADF instead of Context Service for context claims.
ADF is needed for XPM Session Preview, Experience Optimization and Context Expressions. Values: [true, false]:
Q: Why do I need to declare my view inside getDefaultMvcData()?
A: This method is intended for so-called embedded Entity Models. That is, Entity Models which are used within Rich Text content. On the CM-side, these are just linked Components, so these Entity Models won't get MVC data (View name etc.) from CM. If the Entity Model implements this method, it ...
Yes you can. See the following blog (near the end), or the official documentation.
Sites 9.0 (or rather Content Delivery 11.0.0) is compatible with DXA 1.8, however you won't be able to use the new features introduced, for example content mashups.
The issue here was that the content was being cached at multiple locations and so the services and the webapp needed a proper restart and in the correct order. We are using JMS for the CD services so here is the order in which we restarted and it worked
JMS Caching services
DXA Model service
In my understanding, DXA caches the resources (jsons and other files) on the filesystem of the webserver. By doing an admin/refresh you instruct the application to reload those resources from the DB. But, this is not a global operation, it only applies to that specific server. Having that in mind, the most straight forward solution is to call the admin/...
I was getting issues because i was not using dynamic documentation module here,
And this is Tridion docs implementation so after addition ofdynamic documentation moduler and update of few references to dynamic documentation module classes now I am able to get the pagemodel object.
After investigating I found out udp-discovery-client-lightweight:11.1.0-1063 api is trying to find default ehcache file with name : ehcache-default.xml.
In order to fix exception on console, i have renamed dxa-ehcache.xml to ehcache-default.xml
and on dxa.properties also updated the reference for key dxa.caching.configuration
from dxa-ehcache.xml to ...
I was able to fix this problem by updating jackson apis to version 2.10.0, previously it was refering to version 2.8.10
jacksonversion = '2.10.0'
The DXA Resolver uses a non-standard logging mechanism which can be activated by setting an environment variable called DXA_LOGGING with the path of the log file.
You cannot prevent an exception or error being thrown by the application for pages or items that does not exist. However, you can customize the error message or throw errors differently to create a better user experience.
You can look through the example for DXA 1.4. It should be pretty similar to the DXA version that you are using, though.
The other way ...
DXA offers 2 OOTB ways of generating the sitemap, static and dynamic. You can read more here.
Now depending on which type you use, the default one is static, you will have to do different actions. Either adjust the numeric prefixes or adjust the taxonomy and keywords used by pages.
Yes, but you will have to custom code this yourself and since you want this ...