port name conflicts (and other bundle descriptor problems)

[ChrisVeigl]

when a bundle descriptor for a plugin contains input- and output ports of the same name, the "download component collection" in the ACS fails and the component collection cannot be used.

internally, prefixes for the portnames are used (e.g. ipMyPort and opMyPort) - so there should be no name conficts in such a case. nevertheless, the main problem is that the ARE does not thorw any log or error message - thus it becomes very difficult to find such problems when creating a new plugin.

errors when parsing the bundle descriptor should be reported (at least logged to the console window) to ease debugging.

(additionally the plugin creation wizard could prevent name conflicts of ports or events)