|
|
| Re: StackOverflowError in WindowBuilder [message #787618 is a reply to message #787615] |
Tue, 31 January 2012 19:49   |
 Markus Schlegel
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
Can't provide one which compiles, since the code is not open source.
But from the Stacktrace, the problem seems to be obvious...
I mean
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo0(JavaInfoResolver.java:222)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:131)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
...
Markus
[Updated on: Tue, 31 January 2012 19:49] Report message to a moderator |
|
|
| Re: StackOverflowError in WindowBuilder [message #787653 is a reply to message #787618] |
Tue, 31 January 2012 20:58 |
Eric Clayberg
Messages: 979
Registered: July 2009
Location: Boston, MA |
Senior Member |
|
|
OK, if you think the problem is obvious, feel free to submit a patch. WB is open source after all. 
BTW, I would expect a patch to also include a test case that proves that the patch actually solves the problem.
It doesn't matter whether your specific code is open source or not. That is imaterial to providing a test case. If your current code triggers the problem, then it should be quite easy to construct a simple, standalone, dummy example that illustrates the exact same problem. Unless we have a way to actually reproduce the problem, there is really no point in spending time looking into it.
We are quite willing to look into this (and fix it), but only if we have the bare minimum of info needed to get started on it. That is what we need from you.
|
|
|
|
| Re: StackOverflowError in WindowBuilder [message #788199 is a reply to message #787975] |
Wed, 01 February 2012 13:30 |
Eric Clayberg
Messages: 979
Registered: July 2009
Location: Boston, MA |
Senior Member |
|
|
In that case, why send in a partial bug report and exclude the test case?
If you have a class that exhibits this problem, creating a test case that will reproduce that same problem should not take more than a few minutes.
I'm not sure why you would be disappointed with the level of support, since we are offerring to do just that. In fact, the very same team that worked on and supported WB before it was open sourced still works on and supports it now. I believe that our track record for responding to user questions and fixing bugs has been exceptional. We respond to almost every forum message, and we have closed 94% of bug reports in Bugzilla.
As I said earlier, we are more than willing to look into this, but you have to give us something to work with. Please read Reproducible Test Cases in the WB docs, if you need a further explanation of why this is important.
|
|
|
Powered by
FUDForum. Page generated in 0.03212 seconds
] 
Search
Help
Register
Login
Home
