Bug 1010681

Summary: [RFE] Ad Hoc Domains - localization is set according to enum translator view and not via session context
Product: Red Hat Enterprise Virtualization Manager Reporter: Yaniv Lavi <ylavi>
Component: jasperreports-server-proAssignee: Shirly Radco <sradco>
Status: CLOSED WONTFIX QA Contact: movciari
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: bazulay, ecohen, gklein, iheim, pstehlik, rbalakri, Rhev-m-bugs, sradco, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: reports
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-12 10:29:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Reports RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Case_37486_Workaround_Implementation_Instructions.pdf none

Description Yaniv Lavi 2013-09-22 14:01:00 UTC 
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):
3.3.0

How reproducible:
Always

Steps to Reproduce:
1. login using non english locale
2. create ad hoc report

Actual results:
All enum values are in english

Expected results:
Should be localized as well according to session

Additional info:
Comment 1 Yaniv Lavi 2014-03-19 19:36:08 UTC 
Moving to 3.5.0 due to capacity issues.



Yaniv
Comment 2 Shirly Radco 2014-06-02 12:17:08 UTC 
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.
Comment 3 Shirly Radco 2014-06-08 06:54:18 UTC 
Open Case Number 00037486

Shirly
Comment 4 Yaniv Lavi 2014-06-22 12:17:19 UTC 
(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
> insufficient.

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?



Yaniv
Comment 5 Shirly Radco 2014-06-30 15:30:06 UTC 
Jasper replied:

"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.

Steve"
Comment 6 Shirly Radco 2014-06-30 15:31:43 UTC 
Created attachment 913464 [details]
Case_37486_Workaround_Implementation_Instructions.pdf
Comment 9 Shirly Radco 2014-08-18 14:34:37 UTC 
Tried workaround from by Jasper.
Workaround is insufficient.

We will wait until Jasper adds this.

Shirly
Comment 11 Yaniv Lavi 2014-09-08 14:52:34 UTC 
Moving to JRS component since there is no working workaround and this is dependent on their fix.



Yaniv