openArchitectureWare moved to Eclipse Modeling as part of Galileo release. This blog series reports my experiences to migrate a huge oaw4 project. This is part 8 - you’ll find an overview of this blog series here.
oaw4 means openArchitectureWare 4.3.1, oaw5 means MWE (EMFT) + Xpand (M2T) + Xtext (TMF) - more infos at oaw WorkingGroup.
In the last blog I explained HowTo migrate your oaw4 workflow files – this entry will tell you what must be changed in your Xpand (.xpt) and Xtend (.ext) templates to make them run under oaw5.
oaw4:
In your oaw4 Xpand templates you’ll probably find:
![]()
…and in your Xtend templates maybe it looks like this:

oaw5:
Unser oaw5 the namespace changed and it should look this way:
![]()

So this was an easy part, I only had to do two Search / Replace for my Xpand (*.xpt) and Xtend (*.ext) - Templates.
- org::openarchitectureware::util::stdlib with org::eclipse::xtend::util::stdlib
- org::openarchitectureware::uml2 with org::eclipse::xtend::typesystem::uml2
I have logged my Search / Replace values – for your convienence you can download this file from here.
As always control your work if there’s an org::openarchitectureware:: left.
Now we’re hopefully done with the work and it’s time to run a MWE workflow ! (hopefully successfull) My next blog entry describes what perhaps can happen…

lentas (crete)
loutro (crete)
I
J Amsterdam 2013
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
friend of eclipse