clientBehaviours and providerBehaviours in FAMIXBehaviouralEntity

Hello,

There are some new methods introduced in FAMIXBehaviouralEntity: clientBehaviours and providerBehaviours.

clientBehaviours

<MSEProperty: #clientBehaviours type: #FAMIXBehaviouralEntity> <multivalued> <derived>

<MSEComment: 'All behaviours that depend on the receiver'>

^ self invokingMethods

InvokingMethods is defined in one of the subclasses of FAMIXBehaviouralEntity: FAMIXMethod and not the other subclass, FAMIXFunction. I have my code that subclasses FAMIXFunction and when I try to export the object to an MSE, there is an error: MyFunction(Object)>>doesNotUnderstand: #invokingMethods.

So, IMO, clientBehaviours and providerBehaviours methods need to point to a method at the same level instead of sending message to a subclass method.

regards,

Usman

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

Oops. My bad. It should be fixed now. Can you try?

On Mon, Aug 5, 2013 at 4:31 PM, Usman Bhatti <[hidden email]> wrote:

Hello,

There are some new methods introduced in FAMIXBehaviouralEntity: clientBehaviours and providerBehaviours.

clientBehaviours

<MSEProperty: #clientBehaviours type: #FAMIXBehaviouralEntity> <multivalued> <derived>

<MSEComment: 'All behaviours that depend on the receiver'>

^ self invokingMethods

InvokingMethods is defined in one of the subclasses of FAMIXBehaviouralEntity: FAMIXMethod and not the other subclass, FAMIXFunction. I have my code that subclasses FAMIXFunction and when I try to export the object to an MSE, there is an error: MyFunction(Object)>>doesNotUnderstand: #invokingMethods.

So, IMO, clientBehaviours and providerBehaviours methods need to point to a method at the same level instead of sending message to a subclass method.

regards,

Usman

_______________________________________________
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

The fix corrected the bug in MSE export. Tx.

The moose job is unstable and that's because of unimplemented-feature-test I guess?

On Tue, Aug 6, 2013 at 7:03 AM, Tudor Girba <[hidden email]> wrote:

Oops. My bad. It should be fixed now. Can you try?

On Mon, Aug 5, 2013 at 4:31 PM, Usman Bhatti <[hidden email]> wrote:

Hello,

There are some new methods introduced in FAMIXBehaviouralEntity: clientBehaviours and providerBehaviours.

clientBehaviours

<MSEProperty: #clientBehaviours type: #FAMIXBehaviouralEntity> <multivalued> <derived>

<MSEComment: 'All behaviours that depend on the receiver'>

^ self invokingMethods

InvokingMethods is defined in one of the subclasses of FAMIXBehaviouralEntity: FAMIXMethod and not the other subclass, FAMIXFunction. I have my code that subclasses FAMIXFunction and when I try to export the object to an MSE, there is an error: MyFunction(Object)>>doesNotUnderstand: #invokingMethods.

So, IMO, clientBehaviours and providerBehaviours methods need to point to a method at the same level instead of sending message to a subclass method.

regards,

Usman

_______________________________________________
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