Bugzilla – Full Text Bug Listing
| Summary: | syslib.getProperties is not supported in javascript | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Jing Qian <jqian> |
| Component: | EDT | Assignee: | Yun Feng Ma <mayunf> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | chenzhh, greer, hjiyong, jspadea, smythew, svihovec |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
I've set the target to I-15. If this work item is deferred to 1.0, then change the target to Future. 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. 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. 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. |
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.