UML attribute not created on attributes which call methods

[GoogleCodeExporter]

Steps to reproduce:
1. import the attached example into pynsource
2. look for the uml result of scanning self.datamodelProxy.setData(2)

Expected output:

class should have a uml attribute called "datamodelProxy"

Instead:

Nothing is created.

Original issue reported on code.google.com by [email protected] on 15 Jul 2012 at 12:26

Attachments:

• parsebug_example.py

[GoogleCodeExporter]

UML attribute not being created for DataSubmittedCommand.datamodelProxy, due to 
the fact that a call to setData() is made off that attribute.

Parser should be improved so that an attribute pointing to an object Z and 
calling methods on that object is recognised as an attribute pointing to class 
Z.

Original comment by [email protected] on 15 Jul 2012 at 12:29

[GoogleCodeExporter]

Original comment by [email protected] on 15 Jul 2012 at 2:16

• Removed labels: Milestone-Release1.7

[GoogleCodeExporter]

Original comment by [email protected] on 15 Jul 2012 at 2:19

• Added labels: Component-Parsing
• Removed labels: Component-Logic