Bugzilla – Full Text Bug Listing
| Summary: | Confusing error message when the method of an invoke can't be found | ||
|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Yvan Lussaud <yvan.lussaud> |
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | laurent.goubet |
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
When either the method or Class of a service call isn't found, the Error message now tells as such. Likewise, an exception occuring during a service call is now logged. |
When one enter some false information in the invoke: invoke('classname', 'methodname(args)', Sequence{str}) For instance classname or nemthodname or args are mistaken. There is no compilation error (may try to find a way to provide a warning at least) and the runtime error is complaining about a null value returned by the service and not about the fact the service was not found.