Bugzilla – Full Text Bug Listing
| Summary: | Support expressions and template parameter substitution in the same constructs | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Roded Bahat <rodedb> |
| Component: | Sapphire | Assignee: | Project Inbox <sapphire.ui-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | konstantin, rodedb |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
It turns out that accessing template params from EL is already supported. Not sure why I thought this didn't work yet. The available params are exposed via "Params" property, which is a map. You can access individual params using Params.FooBar syntax or Params[ "FooBar" ]. The second form is useful if your param name doesn't conform to property name requirements. |
Build Identifier: Build id: 20110916-0149 Devise a way to allow usage of Sapphire expressions ${...} in conjunction with template parameter substitution @{...}. See the following post for a usage example: http://www.eclipse.org/forums/index.php/t/271089/ Reproducible: Always Steps to Reproduce: N/A