Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336593

Summary:	Check for unresolved proxies
Product:	[Modeling] Acceleo	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	Project Inbox <acceleo-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	stephane.begaudeau
Version:	3.0.0
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Ed Willink

2011-02-08 03:44:54 EST

Forked off from Bug 335764.

> When accessing potential unresolved proxies, it is a good idea to check for a
> > proxy. The most evident unchecked place to me is at the root of AcceleoServ
> > ice.doGenerate where
> > 
> > final EClassifier argumentType = template.getParameter().get(0).getType();
> > 
> > is unchecked and the unresolved proxy results in a very quick execution and no
> > output for no matches.

We can't check for proxies everywhere ... but yes, this particular access
should be.

Everywhere is certainly impractical, but most proxies are actually to contained objects so they are very unlikely to fail.

The critical ones are type accesses that might resolve to a different module, these probably only occur in a couple of highly shared places.

Comment 1 Stephane Begaudeau

2011-03-30 05:24:42 EDT

Contributed on HEAD. It will be available in Acceleo 3.1 M7.