| Summary: | Dedicated or RESt service invocation does not use the aliased names | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Joseph Vincens <jvincens> |
| Component: | EDT | Assignee: | Joseph Vincens <jvincens> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jspadea, mheitz |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Joseph Vincens
Whatever we decide for a deployment solution, the test server will need to do the same thing in its mapping of uri to generated name.
Also, what about the case:
svc iService1{@DedicatedService{classname = "pkg.class"}};
Will the generator know to generate "pkg.eze_class"? Any places in the code where it can come from a variable?
I'll move JavaAliaser from the generator to package org.eclipse.edt.javart.util in the runtime. I'll update this bug to let you know when I've done it. My changes are done. fixed runtime does an alias before getting the service class verified |