You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2011/06/30 23:27:28 UTC
[jira] [Created] (GERONIMODEVTOOLS-763) "Source not found" message
when debugging a project
"Source not found" message when debugging a project
---------------------------------------------------
Key: GERONIMODEVTOOLS-763
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Under certain circumstances one can see "Source not found" message while debugging a project that exists in the workspace and is deployed to the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-763) "Source not found"
message when debugging a project
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058089#comment-13058089 ]
Jarek Gawor commented on GERONIMODEVTOOLS-763:
----------------------------------------------
There are really 2 problems here.
1) The Eclipse can sometimes compute the source paths too early - before the projects are deployed to the server. Here's the call trace Eclipse requests to compute the source paths too early:
at rg.apache.geronimo.st.v30.core.GeronimoSourcePathComputerDelegate.computeSourceContainers(GeronimoSourcePathComputerDelegate.java:63)
at org.eclipse.debug.internal.core.sourcelookup.SourcePathComputer.computeSourceContainers(SourcePathComputer.java:69)
at org.eclipse.debug.core.sourcelookup.containers.DefaultSourceContainer.createSourceContainers(DefaultSourceContainer.java:112)
at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.getSourceContainers(CompositeSourceContainer.java:129)
at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.findSourceElements(CompositeSourceContainer.java:46)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupParticipant.findSourceElements(AbstractSourceLookupParticipant.java:67)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector$SourceLookupQuery.run(AbstractSourceLookupDirector.java:141)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.doSourceLookup(AbstractSourceLookupDirector.java:490)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.getSourceElement(AbstractSourceLookupDirector.java:758)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.lookup(SourceLookupFacility.java:148)
at org.eclipse.debug.ui.DebugUITools.lookupSource(DebugUITools.java:777)
at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.getProblem(JavaDebugOptionsManager.java:577)
at org.eclipse.jdt.internal.debug.ui.breakpoints.SuspendOnCompilationErrorListener.breakpointHit(SuspendOnCompilationErrorListener.java:67)
at org.eclipse.jdt.internal.debug.core.breakpoints.BreakpointListenerManager$JavaBreakpointListenerProxy.breakpointHit(BreakpointListenerManager.java:135)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$HitNotifier.run(JDIDebugPlugin.java:644)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$AbstractNotifier.notifyListeners(JDIDebugPlugin.java:466)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$HitNotifier.notifyHit(JDIDebugPlugin.java:658)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.fireBreakpointHit(JDIDebugPlugin.java:407)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.handleSuspendForBreakpoint(JDIThread.java:1131)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.suspend(JavaBreakpoint.java:363)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint.handleBreakpointEvent(JavaExceptionBreakpoint.java:348)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleEvent(JavaBreakpoint.java:288)
at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:155)
at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:104)
at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:250)
2) Once Eclipse computes the source paths, it doesn't seems to re-compute them anymore. That causes a problem when deploying & debugging another project in the same session.
> "Source not found" message when debugging a project
> ---------------------------------------------------
>
> Key: GERONIMODEVTOOLS-763
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> Under certain circumstances one can see "Source not found" message while debugging a project that exists in the workspace and is deployed to the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-763) "Source not found"
message when debugging a project
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058207#comment-13058207 ]
Jarek Gawor commented on GERONIMODEVTOOLS-763:
----------------------------------------------
About 1). No idea why & how that happens but the early source path computation was triggered by the following code:
URL.setURLStreamHandlerFactory(streamHandlerFactory);
In OSGi this will always throw an Error on this call since the framework itself sets a default factory (and only one can be set). The call to this function was in a proper try {} catch block but somehow it still caused Eclipse to fire the breakpoint hit event.
> "Source not found" message when debugging a project
> ---------------------------------------------------
>
> Key: GERONIMODEVTOOLS-763
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> Under certain circumstances one can see "Source not found" message while debugging a project that exists in the workspace and is deployed to the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-763) "Source not found"
message when debugging a project
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058211#comment-13058211 ]
Jarek Gawor commented on GERONIMODEVTOOLS-763:
----------------------------------------------
In revision 1141790 I committed some changes that reset the source project lookup list when needed. The way the reset is done is not too great but I couldn't find a better / easier way to do it.
> "Source not found" message when debugging a project
> ---------------------------------------------------
>
> Key: GERONIMODEVTOOLS-763
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> Under certain circumstances one can see "Source not found" message while debugging a project that exists in the workspace and is deployed to the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-763) "Source not found" message
when debugging a project
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved GERONIMODEVTOOLS-763.
------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0
> "Source not found" message when debugging a project
> ---------------------------------------------------
>
> Key: GERONIMODEVTOOLS-763
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> Under certain circumstances one can see "Source not found" message while debugging a project that exists in the workspace and is deployed to the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira