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.

Bug 59749

Summary: "Apply Code Changes" throws NullPointerException
Product: debugger Reporter: mariso <mariso>
Component: JavaAssignee: issues@debugger <issues>
Status: CLOSED DUPLICATE    
Severity: blocker    
Priority: P4    
Version: 4.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Attachments: messages.log

Description mariso 2005-06-08 16:39:37 UTC
"Apply Code Changes" doesn't work for me. I am using SUN AS 8.1.

When I press the button it always throws NPE:

Classes to be reloaded:
 lv.idega.txgateway.wstestclient.wsclient.WSClient
D:\Projects\IdegaTransactionGateway\TransactionGatewayWEBTestClient\nbproject\build-impl.xml:461:
The following error occurred while executing this line:
D:\Projects\IdegaTransactionGateway\TransactionGatewayWEBTestClient\nbproject\build-impl.xml:209:
java.lang.NullPointerException
BUILD FAILED (total time: 2 seconds)

It refers to "nbjpdareload" in those lines:

    <target name="-do-debug-fix" if="netbeans.home"
depends="init,-pre-debug-fix,compile-single">
        <webproject1:nbjpdareload/>
    </target>


        <macrodef name="nbjpdareload"
uri="http://www.netbeans.org/ns/web-project/1">
            <attribute name="dir" default="${build.classes.dir.real}"/>
            <sequential>
                <nbjpdareload>
                    <fileset dir="@{dir}" includes="${fix.includes}*.class"/>
                </nbjpdareload>
            </sequential>
        </macrodef>


Steps to reproduce: 
-run IDE 
-create a new WEB app with a WEB Service client
-start debug session with SUN AS 8.1 PE (sun-appserver-pe8.1_01)
-add some line of code (for example add "int t=0;").
-press "Apply code changes"
Comment 1 mariso 2005-06-08 16:40:29 UTC
Created attachment 22558 [details]
messages.log
Comment 2 Martin Entlicher 2005-06-08 20:30:51 UTC
This seems to be a duplicate of issue #58323 (see also issue #58396). It's
already fixed in 4.2 dev builds.

*** This issue has been marked as a duplicate of 58323 ***
Comment 3 Quality Engineering 2010-04-29 09:23:08 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.