Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 491 by andrehoraa: VerveineJ: MSE is not exporting implemented interfaces http://code.google.com/p/moose-technology/issues/detail?id=491
In VerveineJ the .mse file is not exporting the implemented interface(s) of a class. For example in LAN model the class XPrinter implements the interface that is not exported.
Please fill in the labels with the following information: * Type-Defect * Component-Verveine
Comment #1 on issue 491 by andrehoraa: VerveineJ: MSE is not exporting implemented interfaces http://code.google.com/p/moose-technology/issues/detail?id=491
For example in LAN model the class XPrinter implements the interface *IPrinter* that is not exported.
Updates: Status: Fixed Owner: anquetil.nicolas Labels: Component-Verveine
Comment #2 on issue 491 by anquetil.nicolas: VerveineJ: MSE is not exporting implemented interfaces http://code.google.com/p/moose-technology/issues/detail?id=491
(No comment was entered for this change.)
Updates: Labels: Milestone-4.3
Comment #3 on issue 491 by tudor.girba: VerveineJ: MSE is not exporting implemented interfaces http://code.google.com/p/moose-technology/issues/detail?id=491
What was the problem? Was it simply a matter of visiting the implemented interfaces?
Comment #4 on issue 491 by andrehoraa: VerveineJ: MSE is not exporting implemented interfaces http://code.google.com/p/moose-technology/issues/detail?id=491
The problem was that if a class implemented interfaces, VerveiveJ was not exporting this information. Now it is exporting and, as consequence, now it is possible to use next/previous for Inheritance (like a "multiple inheritance", similar what InFusion do).
-
moose-technology＠googlecode.com