Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » M2M (model-to-model transformation) » [QVTO] Bug 254417 fix broke black box import in org.eclipse.m2m.qvt.oml_1.0.1?
[QVTO] Bug 254417 fix broke black box import in org.eclipse.m2m.qvt.oml_1.0.1? [message #630095] Thu, 30 September 2010 15:06
Adrian Price is currently offline Adrian PriceFriend
Messages: 61
Registered: July 2009
Member
Good day,

I have been struggling, without success, to import a black box Java library
in m2m.qvt-1.0.1. It seems to me that this functionality may have been
broken by the fix for Bug 254417.

I can see the library extension being loaded successfully by
LibrariesRegistryImpl, but get the message "Cannot find imported compilation
unit xxx", regardless of whether the qvto file says 'import xxx;' or 'import
library xxx;'. I did a bit of archaeology and discovered that:

In QvtOperationalVisitorCS.visitMappingModule() line 1266:
for (ImportCS libImport : moduleCS.getImports()) {

if (false == libImport instanceof LibraryImportCS) {

continue; // <== always a ModuleImportCS, never a LibraryImportCS,
even for 'import library xxx;'

In QvtOpLPGParser.ruleAction() line 2587:

// Rule 277: importCS ::= import library qualifiedNameCS ;

case 277: {


CSTNode result = createLibraryImportCS( // <== never gets called, even for
'import library xxx;'

I'm guessing that when 'import library' was deprecated, this broke the
parser code that resolves blackbox library references.

Could anyone please confirm this and/or suggest a workaround?

Thanks,

Adrian Price

Senior Architect

TIBCO Software Inc.
Previous Topic:[ATL-EMF] Problem with references
Next Topic:[QVTO]when a type does not conform to itself?
Goto Forum:
  


Current Time: Tue Jun 25 01:19:39 GMT 2019

Powered by FUDForum. Page generated in 0.01675 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top