Steps to reproduce:
- Create Java class.
- Choose it in model tree ( or on diagram ).
- Apply to it some design pattern ( this class should be used as participant) .
As result - model element has right structure that was created in design pattern (
all methods and attributes declared in template ) , but source code was not changed.
Only hierarchy is propagated in source code ( implements , extends ).
--- 10/19/04 14:20 GMT
reproducible with coke060619
generate code do not correct source (may be a bug in generate code).
----: 2006-06-21 15:23:42
This is fixed in a mannor of speaking, since we no longer support live round trip. Now you will have to
use the code generation action when you are ready to generate source code.
It's still valid in 061010 because Apply Design Pattern process has its own code
Ok, we then need to dispable to autocode generation.
We have decided to disable this feature. When a Design Pattern is applied, there
will not be an option to Generate Code. So now just Generate Code for the newly
created elements from the applied DP.
The dialog to Generate Code after applying a design pattern is no longer displayed.
Now there is a Regression:
UML|Design Pattern|Design Pattern Catalog|Generate Code After Applying Pattern
option has no effect.
I think current fix is incomplete because generate code isn't removed from all
places but I can file separate issue on the option if it's more appropriate for you.
Are you saying that the remaining issue is that the global preference still
remains? If so, I can use this issue to track it.
yes, you got it.
I think global option(preference) should be removed at the same time as
we already have some obsolete preferences which wasn't removed at proper time
and seems will remains in options for a long time
Removed the preferences from the UML Options
verfied with 061018_27