I'm seeing a localization error when testing a new website functionality in Web 8.5 and DXA 2.0.3 (Java).

We configured for serve this kind of url: http://localhost:8080/front-web/en/discovery/index.html

  • ContextUrl -> /front-web from front-web.war in Boss
  • RelativeUrl -> /en for English

Topology Config

PS C:\Users\MTSUser> Get-TtmMapping

CmEnvironmentId     : TridioncmDEV
PublicationId       : tcm:0-41-1
EnvironmentPurpose  : Live
WebApplicationId    : TestLive_RootWebApp
RelativeUrl         : /en
PrimaryMappedUrl    : http://localhost:8080/front-web/en
IsOffline           : False
CdEnvironment       :
Id                  : Mapping1
ExtensionProperties : {}

PS C:\Users\MTSUser> Get-TtmWebsite

BaseUrls             : {http://localhost:8080, http://frontdev-ecp.frontweb.com}
CdEnvironmentId      : Live
EnvironmentPurpose   : Live
CdEnvironment        :
ScopedRepositoryKeys : {}
Id                   : TestLive
ExtensionProperties  : {}

PS C:\Users\MTSUser> Get-TtmWebApplication

ContextUrl           : /front-web
WebsiteId            : TestLive
EnvironmentPurpose   : Live
CdEnvironment        :
ScopedRepositoryKeys : {}
Id                   : TestLive_RootWebApp
ExtensionProperties  : {}

When is trying to get settings.json and _all.json the RelativeUrl is not included to get the file and it's trying to get: /front-web/system/blabla.json

Debugging the code I see:


<?xml version="1.0" encoding="UTF-8"?>
<entry xmlns:metadata="http://docs.oasis-open.org/odata/ns/metadata" xmlns:data="http://docs.oasis-open.org/odata/ns/data" xmlns="http://www.w3.org/2005/Atom" metadata:context="http://frontdev-cis.frontweb.com:8083/client/v4/content.svc/$metadata#PublicationMappings/$entity" xml:base="http://frontdev-cis.frontweb:8083/client/v4/content.svc">
        <name>SDL OData v4 framework</name>
    <link rel="edit" title="PublicationMapping" href="PublicationMappings(NamespaceId=0,PublicationId=41)"></link>
    <category scheme="http://docs.oasis-open.org/odata/ns/scheme" term="#Tridion.ContentDelivery.PublicationMapping"></category>
    <content type="application/xml">
            <data:NamespaceId metadata:type="Int32">0</data:NamespaceId>
            <data:PublicationId metadata:type="Int32">41</data:PublicationId>
            <data:PathScanDepth metadata:type="Int32">100</data:PathScanDepth>

I expected that:


has to be:


Is my assumption correct?

With this response the url for _all.json will be correct.


1 Answer 1


I found the problem and the solution :)

just to refresh CIS configuration executing:

java -jar discovery-registration.jar forceSync


java -jar discovery-registration.jar update
  • Glad you were able to resolve the issue :)
    – Shiva
    Jul 3, 2019 at 21:19
  • Remarkable that fixed the issue! With these commands you synchronize the so-called Capabilities in Discovery Service with what’s in your configuration files. This should not affect the Publication mappings (which are automatically synchronized with Topology Manager). Jul 4, 2019 at 6:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.