Enable developers to click on UI to find the addComponent call/line in source code

[vaadin-bot]

Originally by @samie

---

To debug applications that have complex UI it is currently hard to find the Java source code that constructs it.

To help developers find the relevant source code line a generic debug feature into addComponent is suggested:

• Application debug mode
• Find out the code calling the addComponent function in a ComponentContainer
• Add a button (or similar) to component/windget UI that developer can select it
• When selected, output the formatted src line into stdout, so that Eclipse creates an active link out of it
• Developers can then click the button and and the line in console output to find the code that added the component

---

Imported from https://dev.vaadin.com/ issue #1243

[vaadin-bot]

Originally by @emarc

---

I recall having a working prototype of this at some point... Some thoughts:

• stack trace needed
• both component instantiation and addComponent() stack traces would be nice

[vaadin-bot]

Originally by Jani Laakso

---

This is quite straightforward to implement, code like below could be called for each instantiation code for every component:

StackTraceElement[] st = new Throwable().fillInStackTrace()
                .getStackTrace();
        try {
            String key = "";
            // Class fromCallerClass = Class.forName(st[4].getClassName());
            // String fromMethodName = st[4].getMethodName();
            // Class callerClass = Class.forName(st[3].getClassName());
            String methodName = st[3].getMethodName();
            int line = st[3].getLineNumber();

            String clazz = st[3].getClassName() + ".java";
            // String clazz = st[3].getClassName().substring(
            // st[3].getClassName().lastIndexOf('.') + 1)
            // + ".java";
            key = "(" + clazz + ":" + line + ")" + " " + methodName;
            Integer value = (Integer) classMethodCallCounter.get(key);
            if (value == null)
                value = new Integer(1);
            else
                value = new Integer(value.intValue() + 1);
            classMethodCallCounter.put(key, value);
            return value.intValue() + ": " + key;
        } catch (Exception e) {
            return "unknown class.method";
        }

[vaadin-bot]

Originally by Jani Laakso

---

Eclipse automatically creates links to source code when using specific format to standard streams (err/out);

[vaadin-bot]

Originally by @Artur-

---

There is actually support for this kind of functionality in the current trunk even though it is not enabled. The idea was not track addComponent() calls but to use this to help debugging layout related problems. What is tracked is actually the position where:

• a component is created
• the width of the component is set
• the height of the component is set

Is there really need for finding the position of the addComponent() call or would the creation point be sufficient? The constructor call would in my opinion be just as good for locating the component.

[vaadin-bot]

Originally by @Artur-

---

Related to #2393

[stale]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[stale]

The issue was automatically closed due to inactivity. If you found some new details to it or started working on it, comment on the issue so that maintainers can re-open it.