Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367775 - Support expressions and template parameter substitution in the same constructs
Summary: Support expressions and template parameter substitution in the same constructs
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-03 11:21 EST by Roded Bahat CLA
Modified: 2021-11-19 09:21 EST (History)
2 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 Roded Bahat CLA 2012-01-03 11:21:14 EST 
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
Comment 1 Konstantin Komissarchik CLA 2012-03-14 14:04:32 EDT 
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.