This was a known bug in DXA1.2 but was stated on that ticket to have been fixed in 1.4.
However, there's a report regards the .Net implementation that this would be fixed in 1.5. The discussion by JordanRobinson is very interesting and may help you towards a workaround but fundamentally you'd be best advised to update the filenames.
The issue turned out to be in the Controller code (@RequestMapping).
I had the following:
@RequestMapping(ControllerUtils.INCLUDE_PATH_PREFIX + "Training/CampaignController")
public class CampaignController extends EntityController
It needed to be the following, without the Controller at the end of the Controller name:
Admittedly, the documentation of the DXA prerequisites is a bit unclear/confusing.
DXA is a Web Application Framework which builds upon the Content Delivery Architecture. For SDL web 8, it builds on the CD microservices architecture. In particular, it uses the following microservices:
Discovery Service -- For authentication and lookup of the other ...
It is recommended to delegate rendering of a Region to a Region View.
If, for whatever reason, you want to render all Entities in a Region without using a Region View, you can use a foreach loop to iterate over all Entities and then use the dxa:entity tag to delegate rendering of the Entity to the appropriate Entity View.
DXA has built-in server-side responsive image resizing (to not send unnecessarily large images to mobile devices) based on device parameters and width and aspect ratio parameters specified in the View code.
Not sure what you mean exactly with "...
The Query sent to the Broker to get the image will not return anything to your Model as the url sent for the request is wrong, hence you will not have it stored in your BinaryData/en/media/ as well, which leads to stop you not to use correct src url as well because there is no such image exists, moreover if any time there is no media returned from Broker, ...
Yes! It is possible but need some customization on the DD4T template. DD4T template does not add the schema information (for folder and structure group metadata) in the presentation and because of that you are unable to map it properly with the DXA model. So to resolve that you have to add the schema information along with the metadata component by updating ...
I see this as expected behavior because how should getEntityClassByFullyQualifiedName know when to load Seo and when it should load Link?
The thing that makes entities unique is the entityName which is derived from RootElement names for all Schemas.
The solution is to use unique RootElement names for all Schemas.
Best option to override model binding methods is:
Implement a separate model builder class and register it along with default model builder. Write your own functions to override the default behavior in your custom model builder.
In this way model builder will be executed 2 times for every model.
Implement a custom model builder and override functions to ...
The problem may be that you did not register your CeairLink Entity Model. See: https://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v5/GUID-FEDC295C-1D87-485E-B904-AE5596A4A802
As mentioned in that doc topic, DXA 1.5 Java provides an easy way to register such "embedded" Entity Models. On earlier DXA version, you can't register a View Model without an ...
Since DXA 1.3, loading of config files is done "on-demand" (i.e. when config values are needed) instead of upfront (at "bootstrap" time). This improves startup performance.
So, indeed, the LocalizationData.ConfigStaticContentUrls property is not used anymore; config files are loaded when needed in Localization.LoadConfigSection.
AFAIK, config files named ...
Try adding this in your pom.xml (for version 1.4)
Wow! That is confusing!
From the Stack Trace you can see that the error occurs when trying to save a Business Process Type in COntent Manager (DXA 1.3+ indeed comes with predefined BPTs).
This triggers validation against Topology Manager (to check that the associated Topology Type exists) as can be seen in the (HTML) error: http://localhost:82/ttm201501
You have to ensure that the "inherited" metadata fields are defined in the Schema.
In case of inherited metadata on Pages, you will also have to ensure that the Page has an associated metadata Schema (even if the Page itself doesn't have any metadata), because otherwise you end up with a Page with (inherited) metadata, but no metadata Schema (as Sayantan ...
at first glance it looks like SmartTarget is working fine (content is being delivered from FH) but there is a failing in communication between SmartTarget and Google Analytics. My first thought is to check whether you have all the necessary jars in the correct places. Please check the jars in the Publication Target's CD Endpoint URL as follows:
Ensure you ...
Regarding question 1: this setting should not be needed; we have it set to false on our DXA Test Environments where XO works perfectly fine.
Regarding question 3: check the XO docs for how to setup XO Experiments. From a Web App perspective, Experiments are just Promotions which will randomly show different items. Furthermore, the DXA XO Module ...
That method is only called when an Entity Model is "inflated" from a Rich Text Field.
To clarify: DXA supports Media Items embedded in a Rich Text field (most obvious: embedded Images, but any kind of Media Item can be embedded). If a Rich Text field contains embedded Media Items, DXA creates Entity Models for those Media Items when processing the Rich Text ...
It is currently logged as a defect https://github.com/sdl/dxa-web-application-java/issues/41 (issue is available in both Java and .NET versions DXA), and we are looking at solving it in the upcoming 1.5 release (but no promises currently about that).
DXA has what we called automagic mapping of Schema fields to model properties, for this it uses the semantic mapping, which defaults to using the root element name of a Schema (see also http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v4/GUID-7EA7470E-1592-4734-B824-8F23FF3BD526).
Because of that, it is sort of required that you choose unique root ...
Include Pages are modeled as top-level Regions (named after the Include Page title).
The Component Presentations on the Include Page are also grouped in Regions (based on the CT metadata). These become nested Regions within the top-level Region representing the Include Page.
You can indeed use two levels of Region Views. If you don't need multiple Regions ...
The dxa:entities Tag is intended to be used in a Region View in order to render all Entities within that Region. You don't specify a Region Name in the tag, because it acts on the current Region.
In DXA 1.2+ the best way to deal with empty Regions is to predefine your (potentially) empty Regions in your Page Template metadata. This will ensure that empty ...
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-@RequestMapping.
For PageController mapping if / since no explicit mapping is provided. Thus the resulting mapping for handleJspIncludesErrors() is / + /...
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 project artifactory.
Example can be found
on https://github.com/sdl/dxa-web-application-java/blob/master/dxa-example-webapp/pom.xml in <repositories/> tag,...
The error suggests a connection issue, Can you access your Discovery Service from the machine you are debugging from?
Possible causes (and there could be a lot)
Incorrect value for discovery-service-uri in web.config, shown below
Discovery service incorrectly configured
Firewall blocking Discovery service, as it runs on "unusual" port number (8087?)
Looking at the PowerShell error message, the problem seems to be in the CdEnvironmentId parameter of the Add-TtmWebsite command. So, in the value of $cdEnvironment.Id.
Does your CD Environment ID contain a comma? PowerShell may then misinterpret it as an array of strings instead of a single string.
I did notice that your CD Environment has a quite ...