Bug 284989 - Invocation API does not handle dynamic models
Summary: Invocation API does not handle dynamic models
Status: RESOLVED FIXED
Alias: None
Product: QVTo
Classification: Modeling
Component: Engine (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M2   Edit
Assignee: Radomil Dvorak CLA
QA Contact:
URL:
Whiteboard: Extensibility
Keywords: plan
Depends on:
Blocks:
 
Reported: 2009-07-29 06:28 EDT by Radomil Dvorak CLA
Modified: 2010-05-28 15:22 EDT (History)
1 user (show)

See Also:

Attachments
qvto.test.invoke.issue fix (24.51 KB, application/zip)
2009-07-29 06:38 EDT, Radomil Dvorak CLA 		no flags Details
View All 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 Radomil Dvorak CLA 2009-07-29 06:28:38 EDT 
The current invocation API only involves the global package registry.
The client should be able to provide a custom registry, possibly initialized with packages loaded from the workspace located ecore files.
Comment 1 Radomil Dvorak CLA 2009-07-29 06:38:23 EDT 
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.
Comment 2 Radomil Dvorak CLA 2009-08-27 17:53:55 EDT 
Fixed.