Hi marcelloh
I'd say, this is behaviour! Whether it is expected or not is another discussion
As you probably know, EA is based on a MS-Access DB.
Now, if you insert an image it is neatly stored in the DB as 'long binary data'.
I assume that you controll your packages and VC them with subversion.
So, if you check in your package that contains this diagram you certainly assume that everything is put away. As you even can not move element on a diagram of a checked in package!
The problem is: controlling packages is done via XML and in XML, you can not store binary data but only a link to it. What happens now is that an object of type 'boundary' is exported to XML and put into VC.
So if your colleague gets your changed package, he will only see an empty boundary for you are quite right: the image information is stored in the EAP-file only (which is an Access-DB).
At the moment I can not see a solution to this.
A possible approach could be that Sparx Sys. don't put the binaries into the DB but only store (relative) links to them. By then you cut put the binaries in subversion, too! But this still wouldn't be really satisfying, would it?
