Unexpected behavior in Moose/VerveineJ superclass

Hi guys!

We've been looking with Alex today at a model built with VerveineJ and imported in Moose. 

In the following example: 

public class OrderedKAryTree<V, E> extends AbstractTypedGraph<V, E> implements Tree<V, E> 

If I obtain the object referring to the OrderedKAryTree and I call superclass I get Tree instead of AbstractTypedGraph. 

However, if I call directSuperclasses I get both Tree and AbstractTypedGraph. 

Is this normal behavior?

Thanks,

M.

* Code available at: 

http://grepcode.com/file/repo1.maven.org/maven2/net.sf.jung/jung-graph-impl/2.0.1/edu/uci/ics/jung/graph/OrderedKAryTree.java

--

Mircea Lungu, PhD.

Researcher
Software Composition Group
University of Bern

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

Hi,

superclass simply takes one of the super FAMIXClass objects. It would indeed be better if we would take the first FAMIXClass that is not interface.

I am offline until next week. Can someone else look into this?

Doru

On Tue, May 6, 2014 at 2:05 AM, Mircea Filip Lungu <[hidden email]> wrote:

Hi guys!

We've been looking with Alex today at a model built with VerveineJ and imported in Moose. 

In the following example: 

public class OrderedKAryTree<V, E> extends AbstractTypedGraph<V, E> implements Tree<V, E> 

If I obtain the object referring to the OrderedKAryTree and I call superclass I get Tree instead of AbstractTypedGraph. 

However, if I call directSuperclasses I get both Tree and AbstractTypedGraph. 

Is this normal behavior?

Thanks,

M.

* Code available at: 

http://grepcode.com/file/repo1.maven.org/maven2/net.sf.jung/jung-graph-impl/2.0.1/edu/uci/ics/jung/graph/OrderedKAryTree.java

--

Mircea Lungu, PhD.

Researcher
Software Composition Group
University of Bern

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

--

www.tudorgirba.com

"Every thing has its own flow"

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

Hi Doru,

So it's FAMIX!

I can take care of fixing that.

Cheers,

M.

2014-05-09 21:03 GMT+02:00 Tudor Girba <[hidden email]>:

Hi,

superclass simply takes one of the super FAMIXClass objects. It would indeed be better if we would take the first FAMIXClass that is not interface.

I am offline until next week. Can someone else look into this?

Doru

On Tue, May 6, 2014 at 2:05 AM, Mircea Filip Lungu <[hidden email]> wrote:

Hi guys!

We've been looking with Alex today at a model built with VerveineJ and imported in Moose. 

In the following example: 

public class OrderedKAryTree<V, E> extends AbstractTypedGraph<V, E> implements Tree<V, E> 

If I obtain the object referring to the OrderedKAryTree and I call superclass I get Tree instead of AbstractTypedGraph. 

However, if I call directSuperclasses I get both Tree and AbstractTypedGraph. 

Is this normal behavior?

Thanks,

M.

* Code available at: 

http://grepcode.com/file/repo1.maven.org/maven2/net.sf.jung/jung-graph-impl/2.0.1/edu/uci/ics/jung/graph/OrderedKAryTree.java

--

Mircea Lungu, PhD.

Researcher
Software Composition Group
University of Bern

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

--

www.tudorgirba.com

"Every thing has its own flow"

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

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