WCEM Language Switch

[Former Member]

Hi,

I noticed a peculiar behavior in WCEM 2.0.  If I launch WCEM with the parameter: wec-locale=en_US everything shows up in English correctly (all text and catalog information).  However, if I change the URL to wec-locale=fr_CA, all the TEXT changes to French EXCEPT the Catalog information.  This stays in English.  Is there a way to switch the language in the catalog as well?

[adam_ebert · Accepted solution]

Hi,

because of used backend infrastructure, a language switch within one session via wec-locale request parameter won't work in most of the cases.

Additionally please check the OSS note 1807623.

Best regards,

Adam

[daniel_ruiz2 · Accepted solution]

hi Adam,

wouldn't it be better you to tell Jolly this is an issue with the WCEM? - do you find 'reasonable' not being able to switch languages between requests?

@Jolly: keep "com.sap.wec.localeDeterminationMode" as request, dispatch an event when the user "switch" the language (fixing SAP source) and intercept this event on your Module(s) Event Handler (in whatever module you need to re-create the Business Objects) and start re-building the objects with a proper locale.

Hope it helps,

D.

[adam_ebert · Accepted solution]

Hi Daniel,

for sure this behavior is not optimal and of course I would like to offer unlimited language switch at every place in WCEM. Unfortunately this is not always possible because of several technical facts. The most important one is the behavior of stateful connections which cannot switch language after they have been once created.

All solutions which exist for this area are either not able to provide switch in each situation or they lead to loosing of some session data.

I'm not 100% sure whether I got your proposal correctly, but I would assume that your proposal would loose the already existing BO data within a session during the rebuilding process (as long as you don't care to copy the BO data especially), isn't it?

Best regards,

Adam

[daniel_ruiz2 · Accepted solution]

Hi Adam,

Well, in fact yes, it's not 'straight forward' to keep session because of the reason you just mentioned.. but nevertheless, it's not impossible and the main issue in this thread would be just one BusinessObject that would need to keep getting re-created. Also, case CRM is being used, it's mainly the MDM Connection we would be talking about.

I'm in the opinion of such simple use-cases should be supported no matter what - it's not rocket science anyways.

Cheers,
D.

[Former Member · Accepted solution]

I just find it surprising that switching languages is such a technical challenge.  This should be a standard feature and I have a tough time convincing my client that this is not feasible without making significant modifications to the Business Object.

[WolfgangSattler]

Hi Jolly,

I investigate a lit bit in this area the last days and actually I agree with Adam that exchanging the complete session will be the best appraoch.

For sure this can't be done in every situation (e.g. if the user has already logged in) but in the standard case this should work.

This can be archive also with a customer enhancement

For this I would recommend to enhance the SessionInitialisationFilter and overwrite the protected method calculateAndSetLocale.

Regards Wolfgang

[Former Member]

HI Jolly,

Since the catalog is data driven from MDM, you need to have data for specific locale in MDM for it to show on webshop, Properties will show up from resource bundle in corresponding language but not catalog data.

thanks,

-tarun

[Former Member]

All catalog data and text are maintained in different languages.  My question is why only the text language changes when you modify the URL and not the catalog.  The catalog language stays the same.  However, if I opened up a new browser the language in the catalog changes as well.  This leads me to believe that it might be MDM catalog might be session-based.  Can someone verify?