Red Hat Bugzilla – Bug 1010681
[RFE] Ad Hoc Domains - localization is set according to enum translator view and not via session context
Last modified: 2016-02-10 15:13:09 EST
Description of problem:
Localization is set according to enum translator view and not via session context.
This should be changed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. login using non english locale
2. create ad hoc report
All enum values are in english
Should be localized as well according to session
Moving to 3.5.0 due to capacity issues.
Waiting for a respond from Jasper.
Due to limitations in using session parameter in domain query,
we can't localize the Ad hoc reports results.
Tried to use the Jar and process provided by Jasper but result is still insufficient.
Open Case Number 00037486
(In reply to Shirly Radco from comment #2)
> Waiting for a respond from Jasper.
> Due to limitations in using session parameter in domain query,
> we can't localize the Ad hoc reports results.
> Tried to use the Jar and process provided by Jasper but result is still
We may still be able to do this using calculated columns. The column will display the localized string from filtered query, if it exists, and english from another query otherwise. Shirly, will that work?
"The way to fail over would be to change the expression for the current locale calculated field to the following:
groovy('requestAttributes.request.locale.toString() == null ? "en_US" : requestAttributes.request.locale.toString()')
If you're trying to use this in a derived table, it won't work because derived tables don't yet support dynamic parameter values.
I sent the implementation instructions in an email last time. I'm attaching them to the case as a PDF document for easier reference.
Created attachment 913464 [details]
Tried workaround from by Jasper.
Workaround is insufficient.
We will wait until Jasper adds this.
Moving to JRS component since there is no working workaround and this is dependent on their fix.