Bug 1087871 - kieResources.newFileSystemResource(File) should also support specifying the encoding for portability reasons
Summary: kieResources.newFileSystemResource(File) should also support specifying the e...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ER2
: 6.0.2
Assignee: Mario Fusco
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 13:38 UTC by Geoffrey De Smet
Modified: 2014-08-06 19:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:53:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Geoffrey De Smet 2014-04-15 13:38:48 UTC
All KieResources methods have an overloaded method with a String encoding parameter, for example:
  Resource newInputStreamResource(InputStream in);
  Resource newInputStreamResource(InputStreamin, String encoding);

Except for:
  Resource newFileSystemResource(File file);

Requirements: Add a method:
  Resource newFileSystemResource(File file, String encoding);


If no encoding is specified, the encoding defaults to the platform default (windows-1252 on windows, UTF-8 on linux). This causes portability issues: a DRL file that works perfectly on the developers machine might not work on the production machine - if they use different operation systems.

Comment 4 Marek Winkler 2014-05-06 10:29:30 UTC
Verified on BRMS 6.0.2 ER2.


Note You need to log in before you can comment on or make changes to this bug.