I normally do like this.
No abstract method in the generated abstract base class.
Generated method stub in the generated-once implementation subclass.
// TODO Auto-generated method stub
throw new UnsupportedOperationException("«name» not implemented");
Since the implementation class is only generated once, when adding more
operations it will be compilation errors.
These types of compilation errors can easily be fixed with Eclipse ctrl+1
Add unimplemented methods.
Regarding customization, the AOP features of oAW is great for this.
--
View this message in context:
http://www.nabble.com/-Cartridges%3A-JavaBasic--Should-methods-definded-in-an-Interface-be-abstract-in-the-AbstractClass--tf3768454s17564.html#a10689228
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
