Issue 747 in moose-technology: We should have set methods for all properties

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 747 in moose-technology: We should have set methods for all properties

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.6

New issue 747 by [hidden email]: We should have set methods for all  
properties
http://code.google.com/p/moose-technology/issues/detail?id=747

All methods annotated with <MSEProperty:type:> must have a set methods.

Now, when we export a model to MSE we cannot load them because some  
properties don't have set methods.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 747 in moose-technology: We should have set methods for all properties

moose-technology

Comment #1 on issue 747 by [hidden email]: We should have set methods  
for all properties
http://code.google.com/p/moose-technology/issues/detail?id=747

Fixed for properties in FAMIXNamedEntity, FAMIXNamespace and FAMIXType.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 747 in moose-technology: We should have set methods for all properties

moose-technology

Comment #2 on issue 747 by [hidden email]: We should have set  
methods for all properties
http://code.google.com/p/moose-technology/issues/detail?id=747

This is incorrect!

Only those that are not derived must have a setter. The derived ones will  
not be saved.

There is supposed to be a test for this case. If you find a property that  
causes problems, please add that to the tests.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 747 in moose-technology: We should have set methods for all properties

moose-technology

Comment #3 on issue 747 by [hidden email]: We should have set methods  
for all properties
http://code.google.com/p/moose-technology/issues/detail?id=747

Doru, think in this case:
You export a filtered model with Classes and Namespaces. Then you lose  
information about other entities what is OK (but you don't want to lose  
information about Classes and Namespaces, at least primitives properties).  
As consequence, it will not be possible to recompute derived properties..


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 747 in moose-technology: We should have set methods for all properties

moose-technology

Comment #4 on issue 747 by [hidden email]: We should have set  
methods for all properties
http://code.google.com/p/moose-technology/issues/detail?id=747

Sure. But, the derived properties cannot be saved anyway (unless you  
changed that).

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 747 in moose-technology: We should have set methods for all properties

moose-technology
Updates:
        Status: WontFix

Comment #5 on issue 747 by [hidden email]: We should have set methods  
for all properties
http://code.google.com/p/moose-technology/issues/detail?id=747

Yes, indeed.
ps: I was working in a modified image where it was possible to save all  
derived properties, and then I needed setter methods.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev