This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Although I put breakspoints in a Page BackBean the IDE doesnt stop when I debug the project. I tested, with Tomcat 6.0 and glassfish 2.
Works for me in trunk (6.1) code base.
I tested with gf v2 ur1 in 6.1 (build 02251204), it stops at breakpoint but I don't see the watch/breakpoint/callstack windows appear. I am seeing this red highlighted error in debugger console on the "non-existing paths" : connect-debugger: Non-existing path "C:\Documents and Settings\Krystyna Polomski\My Documents\NetBeansProjects\feb25notshared\${ws.debug.classpaths}" provided. Non-existing path "C:\Documents and Settings\Krystyna Polomski\My Documents\NetBeansProjects\feb25notshared\${ws.web.docbase.dirs}" provided. Attached JPDA debugger to localhost:9009 debug-display-browser: Browsing: http://localhost:8080/feb25notshared/ BUILD SUCCESSFUL (total time: 7 seconds) I tested in 6.0 with gf v2 ur1 and it works. Also see the same non-existent path error there. I'm reassigning to project (?)
Cannot reproduce. Reporter - can you please give more information? I retested with a clean userdir in trunk/6.1/0225 build and in fact the watches/breakpoint windows come up setting a breakpoint in Page Bean (Page1.java) of a VW project. Was this in fact a VW project? http://wiki.netbeans.org/FaqAlternateUserdir on how to execute with alternate userdir.
Its works for a new projects like you said but for my project doesnt work, I want to attach the project so you can see, where can I attach it? I also try with 6.1 200802191203 but I had a lot of problems with my libs, because the IDE doesnt work if I use in a different computer from the created when I try in the creation computer running on tomcat get 25/02/2008 09:46:55 PM com.sun.faces.lifecycle.LifecycleFactoryImpl getLifecycle ADVERTENCIA: LifecycleId com.sun.faces.lifecycle.PARTIAL does not exist and Tomcat doesnt show anything.
Please see your issue #128321 where I have added information regarding creating and attaching projects. Please use glassfish to create and run your VW project in order to rule out deployment related issue. Test with a clean userdir as well. Thanks.
Also remember that if you have closed the debugger windows, closed state is persisted (even for new projects). You can reset your windows via Tools > Reset Windows.
project isn't attached yet, also it may be some specific to project configuration or some config in the project is corrupted, so may be not a P1 issue. but anyway still incomplete.