| Summary: | Invocation API does not handle dynamic models | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] QVTo | Reporter: | Radomil Dvorak <dvorak.radek> | ||||
| Component: | Engine | Assignee: | Radomil Dvorak <dvorak.radek> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | serg.boyko2011 | ||||
| Version: | 2.0 | Keywords: | plan | ||||
| Target Milestone: | 3.0 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | Extensibility | ||||||
| Attachments: |
|
||||||
|
Description
Radomil Dvorak
Created attachment 142870 [details]
qvto.test.invoke.issue fix
Added a workaround solution to function against the QVTo 2.0 Galileo release. The users may add the provided TransformationExecutorExt class to their projects. Eventually, we can deliver it in an internal package in service releases.
The invocation API in Helios release will provide the same ability to pass a custom package registry in the current TransformationExecutor class.
Fixed. |