not detecting conflict among automatic generated set and get methods and user-written methods with the same ename

[GoogleCodeExporter]

when we have an attribute (e.g abc) which Umple will generate set and get 
methods (setAbc(),getAbc()) for it and on the other hand we have user-written 
methods with the same name, Umple just considers its own generated code and put 
to garbage user-written methods. Even Umple considers high priority for its own 
methods, it must arise a warning (or an error) and lets the developer know 
about this decision. This is really critical because the developer would think 
that its set and get methods will work in final system.
class A{
    abc;
    boolean setAbc(String data){
        //use-written special code.
    }  
}

In final generated code, we don't see user-written method.

Original issue reported on code.google.com by V.Abdel...@gmail.com on 27 May 2014 at 4:05

[GoogleCodeExporter]

Original comment by rof...@gmail.com on 29 May 2014 at 9:17

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 10 Jun 2014 at 2:57

• Added labels: Component-Metamodel

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 5 Aug 2014 at 6:35

• Changed state: Verified