1) Open Tools|Options, UML, Templates: add a new domain template (Element Type:Class Stereotype:foo use any template file)
2) Create a class element with foo as stereotype.
3) Generate Code - in dialog, enable the new template, click OK
Result: no template found for the new element with the foo stereotype.
After the new domain template is added, click the option OK button. Open options again and click OK. This second OK
seems to persist the change properly.
Upon further investigation, it is the Stereotype and Output Parameter properties that are not being persisted properly.
The problem was with Stereotype and Output Parameters fields. The changes were not being pushed into the DOM like the
Element Type field was.
The issues have been corrected and checkin of fix awaits approval for release 60 fix candidate.
Problem also with the Description field as well.
fix checked in to trunk and unstable_uml_visualcomponent branch
The bug wasn't verified before cut-off date for 6.0.1patch1 and will be included in 6.0.1patch2.
verified in NB 6.1 build 200802191203.
Also verified in latest Meteora build (unstable_uml_visualcomponent branch).
The fix has been ported into the release601_fixes branch
Checking in DomainTemplatesManagerPanel.form;
new revision: 184.108.40.206; previous revision: 1.13
Checking in DomainTemplatesManagerPanel.java;
new revision: 220.127.116.11; previous revision: 1.27
Checking in DomainTemplatesRetriever.java;
new revision: 18.104.22.168; previous revision: 1.7