Question: why do you implement the same interface that is already implemented by the abstract class in the concrete class?
15 views
Skip to first unread message
weizh...@gmail.com
unread,
Dec 6, 2012, 3:12:18 PM12/6/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to kaleid...@googlegroups.com
Hi there,
I'm just wondering why you are implementing the same interface that is already implemented by the abstract class in the concrete class, like in EhCacheImpl.class?
publicclassEhCacheImpl<K extendsSerializable, V extendsSerializable>extendsAbstractCache<K, V>implements org.kaleidofoundry.core.cache.Cache<K, V>{
Thanks,
David
jraduget
unread,
Dec 7, 2012, 4:12:12 AM12/7/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to kaleid...@googlegroups.com
Hi David,
You're right, it is not necessary, This is more a a personal habit, and not a best practice...