Search Results

In DXA all the dependency management was moved to dxa-bom and dxa-bom-2013sp1 artifacts, and now versions are managed for the whole framework in one place. That was needed to get rid of multiple versi …

Basically <dxa:richtext content="instance of RichText"> iterates over fragments of HtmlElement passed into as a parameter, and doesn't take care of wrapping anything. The tag calls richText.getFragme …

You don't need easylicense, that's right. There were some known (and fixed in some later versions) bugs in CIL when some artifacts were still dependent on CIS stuff. Simply exclude easylicense from t …

No matter which version of Tridion/SDL Web you are using, you can just exclude CWD dependencies if they're coming transitively. https://maven.apache.org/guides/introduction/introduction-to-dependency …

The solution is surprisingly simple. @Controller public class MyPageController { @Autowired private PageController pageController; @RequestMapping(value = "/articles") public String …

cd_broker:8.1.1 is a part of backend, and is not intended to be used inside your web application. SDL CIL 8.1.1 is to be used for this. content-compatible artifact is there for backward-compatibility …

Although there is no a normal way to override the view for 500 error, there is a possible workaround to solve the issue. Since view is resolved with a ViewResolver instance, you can specify your own …

It seems dd4t artifacts are not in DXA distribution. Since they're custom, they're not available on Maven Central. Thus you cannot resolve them. The correct command is mvn clean package -Pweb8 which …

It tries to get a dependency com.sdl.web:content-client-api:jar:8.2.0-1008 which doesn't exist in Maven Central. com.sdl.web:xo-client:jar:8.2.0 is dependent on it. The problem can be workarounded if …

As Bart Koopman said, artifacts for 7.1.0 are not in Maven Central. To be able to use them, you should either manually install them into your Maven repository or configure your project to use local pr …

Particularly this message: "The POM for com.sdl.web:content-client-api:jar:8.5.0-1012 is missing, no dependency information available." seems like an issue in libraries. Also it's interesting th …

By returning a view name you tell Spring MVC to find this view in web resources and then to invoke the code in that view. If your view contains jsp:useBean tag, it obviously look for a PageModel bean …

Make sure that your cache config has all the caches configured like in the following file https://github.com/sdl/dxa-web-application-java/blob/DXA_2.0_CTP_2_Release/dxa-webapp/src/main/resources/ehcac …

As @Quirijn has mentioned, BaseConroller is an abstract class that contains this mapping. When you extend it with an implementation, Spring maps base methods to concrete-class-@RequestMapping + method …

There is an inconsistency in how DXA resolves normal and contextual views. Short story Set dxa.web.views.folder=/ in dxa.properties. Add your views to <YOUR_WEBAPP>/src/main/resources/WEB-INF/Views …