StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18963854
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-23T16:03:59.740
FavoriteCount
0
LastActivityDate
2013-09-23T16:03:59.740
LastEditDate
LastEditorUserId
0
OwnerUserId
1733377
ParentId
11938449
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I agree - I feel that this is a limitation of Java. Sure, they have made their case about the advantages of not allowing inherited static methods, so I get it, but the fact is I have run into cases where this would be useful. Consider this case: I have a parent <code>Condition</code> class, and for each of its sub-classes, I want a <code>getName()</code> method that states the class' name. The name of the sub-class will not be the Java's class name, but will be some lower-case text string used for JSON purposes on a web front end. The <code>getName()</code> method will not change per instance, so it is safe to make it static. However, some of the sub-classes of the <code>Condition</code> class will not be allowed to have no-argument constructors - some of them I will need to require that some parameters are defined at instantiation. I use the <code>Reflections</code> library to get all classes in a package at runtime. Now, I want a list of all the names of each <code>Condition</code> class that is in this package, so I can return it to a web front end for JavaScript parsing. I would go through the effort of just instantiating each class, but as I said, they do not all have no-argument constructors. I have designed the constructors of the sub-classes to throw an <code>IllegalArgumentException</code> if some of the parameters are not correctly defined, so I cannot merely pass in null arguments. This is why I want the <code>getName()</code> method to be static, but required for all sub-classes. My current workaround is to do the following: In the <code>Condition</code> class (which is abstract), I have defined a method: <pre><code>public String getName () { throw new IllegalArugmentException ("Child class did not declare an overridden getName() method using a static getConditionName() method. This must be done in order for the class to be registerred with Condition.getAllConditions()"); } </code></pre> So in each sub-class, I simply define: <pre><code>@Override public String getName () { return getConditionName (); } </code></pre> And then I define a static <code>getConditionName()</code> method for each. This is not quite "forcing" each sub-class to do so, but I do it in a way where if getName() is ever inadvertently called, the programmer is instructed how to fix the problem.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJava - Alternatives to forcing subclass to have a static method
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMichael Plautz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.