StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20177204
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-24T16:56:36.767
FavoriteCount
0
LastActivityDate
2014-11-19T00:14:33.540
LastEditDate
2014-11-19T00:14:33.540
LastEditorUserId
1329290
OwnerUserId
1329290
ParentId
20176558
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Object Oriented programming in Java states that your service is scope for invocation, nothing else (forget <code>static</code>). So there is no normal way to find who is calling instance's method other than passing <code>S</code> instance as argument. But that does not mean it is impossible. If you only need to know what is the type of caller, you can use <code>Thread.currentThread().getStackTrace()</code>: <pre><code>StackTraceElement[] elements = Thread.currentThread().getStackTrace() StackTraceElement caller = elements[elements.length - 2]; printLn(caller.getClassName()); </code></pre> As I said at the beginning it is totally counter objective Java code. If you need to refer exact instance, you probably should add caller as call parameter. I assume that if you want to refer to caller, callee's code is written by you, so you are able to do it. As for me it would be best choice, because if you need caller in scope of callee, you should pass it directly. Other option is to set caller on ThreadLocal in <code>U</code>, but you don't have confidence that developer will do it each time. If interface cannot be changed, and U is an interface, you could create <code>U</code> builder object: <pre><code>public class UBuilder { public U getS(final S caller) { Proxy.newProxyInstance(getClass().getClassLoader(), U.class, new InvocationHandler() { public Object invoke(Object proxy, Method method, Object[] args) throws Throwable { // store caller value on some ThreadLocal variable try { method.invoke(proxy, args); } finally { // remove caller from ThreadLocal variable } } } } } </code></pre> After that you have additional invocation context (<code>ThreadLocal</code>) referring <code>S</code> instance. If <code>U</code> is not interface, <code>Javassist</code>, <code>CgLib</code> or something similar would help, but only if invoked method is not static or final. If <code>F</code> is static or final I see only dramatically hackish answers. Maybe creating own interface imitating <code>U</code>, and forwarding method invocations in <code>InvocationHandler</code> could be some way. Of course S should refer to this interface, not <code>U</code> directly. Hope it helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODoes callee knows the caller?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStunguski
UserOwnerUserId
1. UStunguski
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.