Re: Issue 416 in moose-technology: method invocation in Java don't fit metamodel

Updates:
        Cc: [hidden email]

Comment #4 on issue 416 by [hidden email]: method invocation in Java  
don't fit metamodel
http://code.google.com/p/moose-technology/issues/detail?id=416

Should we build AttributeInitializer as a subclass of BehavioralEntity?

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

Updates:
        Status: Accepted

Comment #5 on issue 416 by [hidden email]: method invocation in Java  
don't fit metamodel
http://code.google.com/p/moose-technology/issues/detail?id=416

Yes we can (create an AttributeInitializer entity)

currently verveineJ creates a method named "<Initializer>"
So this is just the same idea.

And what about the instance initializer?
currently, it goes in the same method "<Initializer>", do we want to  
separate the two cases?

I am not sure it is necessary, but if not, we should change the name to  
reflect this:
- Initializer?
- InstanceInitializer? (which is the official Java name for the  
initialization block

nicolas

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

Updates:
        Status: Fixed
        Labels: Milestone-4.6

Comment #6 on issue 416 by [hidden email]: method invocation in Java  
don't fit metamodel
http://code.google.com/p/moose-technology/issues/detail?id=416

I think the current solution is good enough.

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