| Summary: | Content assist isn't giving any help on @Resource for interface declaration | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Jing Qian <jqian> | ||||
| Component: | EDT | Assignee: | Xiao Bin Chen <xiaobinc> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | chenzhh, jvincens, svihovec | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
The @Resource{} and @dedicateService{} annotation can't be used in interface type.
They are used in Service type.
@dedicateService{} can not be used on interface part,
but @Resource{} can be used on interface part.
Both @Resource{} and @dedicateService{} can be used on an interface or service. This is different than RBD.
For @dedicateService{} the user must specify @dedicateService{{serviceName = "<fully qualified service name>"}}
if I type {@ then ctrl space I see both dedicatedservice and resource as selections so both seem to be working this morning.
Since We have a new design in EDT for Service. ContentAssist will make some change for this part. Created attachment 204922 [details]
Add support for EDT interface service
fixed. verified on 2011/11/11/0901's build |
Define an interface myInterface. s myInterface?{@Re, then type content assit, no choices is given.