Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357988 - syslib.getProperties is not supported in javascript
Summary: syslib.getProperties is not supported in javascript
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Yun Feng Ma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-16 16:01 EDT by Jing Qian CLA
Modified: 2017-02-23 14:16 EST (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jing Qian CLA 2011-09-16 16:01:47 EDT 
I have rununit.properties file, only has one line
key1=JingValue

in javascript library or RUIhandler, I have the following line

		etrRoot String = SysLib.getProperty("key1");	

This does not work today in EDT. 

Serveral things needs to be designed and implemented.

1. Where should user put the rununit.properties file for development and deployment mode?

2. VE server and deployment needs to do something so the javascript runtime can read the information from this file. 

You can reference RBD as how this should be designed.
Comment 1 Lisa Lasher CLA 2011-09-26 14:08:44 EDT 
I've set the target to I-15.  If this work item is deferred to 1.0, then change the target to Future.
Comment 2 Jing Qian CLA 2011-09-26 23:38:25 EDT 
Brian, I opened this enhancement meant for EDT 1.0
because right now EUnit is the only one uses syslib.getProperties() in javascript.  I have made enough change to use the workaround.  So for EUnit this can be deferred to 1.0 if no one else need it.
Comment 3 Will Smythe CLA 2011-12-16 12:03:08 EST 
What if we allowed developers to store properties in the DD (so, they could have different sets of properties defined in different DD files) and then deploy these properties (maybe directly into the deployed HTML) for use at runtime.
Comment 4 Justin Spadea CLA 2011-12-23 11:45:46 EST 
I like Will's idea - would eliminate the need to manually edit rununit.properties. Debug / VE could read these properties directly from the DD like is already done with resource bindings.