Description Philipp Zech 2010-12-02 06:40:20 EST

Build Identifier: M20100909-0800

during the evaluation of the following workflow component

<component id="StoryGenerator" class="org.eclipse.xpand2.Generator">
		<metaModel class="org.eclipse.xtend.typesystem.emf.EmfMetaModel">
			<metaModelPackage value="org.eclipse.emf.ecore.EcorePackage"/>	
		</metaModel>	
		<metaModel class="org.eclipse.xtend.typesystem.uml2.UML2MetaModel"/>
		<metaModel id="profile"
			class="org.eclipse.xtend.typesystem.uml2.profile.ProfileMetaModel">
			<profile value="src/info/teststories/generator/profile/TTSProfile1.profile.uml"/>
		</metaModel>
		<expand value="info::teststories::generator::xpand::Teststory::Teststory FOR model"/>
		<outlet path="${projectLocation}/src/info/teststories/sut/stories"/>
		<beautifier class="org.eclipse.xpand2.output.JavaBeautifier"/>
	</component>

during the search of the best matching type for the input model (residing in "slot"), also the ProfileMetaModel is searched for a fitting type and following the internalProfileMetaModel is accessed, also with getType(); however, at this point internalProfileMetaModel is null, which actually leads to the NPE and aborts execution of the workflow.
interestingly, the NPE is not thrown if running the workflow inside an eclipse instance, however as soon as a standalone (host) eclipse is used, where the generator resides inside an exported plugin and is not loaded from the workspace of the host plugin, the exception is thrown.
the bug did not show up in the former oaw releases (affected project is currently ported from oaw 4.3.1 to MWE)
during debugging I also realized that inside the ProfileMetaModel the init() method actually is called, however, it returns at line 165 without initializing the stereotypes, as the profiles ArrayList is empty.

Reproducible: Sometimes

Steps to Reproduce:
1. use above workflow excerpt (replace profile by own one)
2. try to run the generator...
3.