I finally figured out what the problem was: the exception vanished the moment I
removed the ${basedir} variables from my model and mergemappings URIs.
All went fine, except for some obscure complaints about not being able to
locate my merge mappings when I wrote:
<?xml version = '1.0' encoding = 'UTF-8' ?>
<andromda>
(...)
<mappingsSearchLocations>
<location>file:src/mappings</location>
</mappingsSearchLocations>
<namespaces>
<namespace name="default">
<properties>
(...)
<property
name="mergeMappingsUri">Merge</property>
</properties>
(...)
I always thought that I could write the mappings URIs in short form... As a
workaround, I use the long notation (file:src/mappings/MergeMappings.xml).
Peter
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1586#1586
Posting to http://forum.andromda.org/ is preferred over posting to the mailing
list!
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Andromda-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user
