• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 201
  • Last Modified:

add(Component) method question


In the init() method, I use add(myLabel). If myLabel is null, we get a nullPointer exception. Where is the method that throws that exception? I could not find it in the Component class where the add methods are written.
0
HanRui
Asked:
HanRui
  • 6
  • 3
1 Solution
 
objectsCommented:
It's in the Applet class or one of it descendants, probably Container.
Why do you need to know?

What you are doing is invalid and that is why you are getting an exception.
0
 
HanRuiAuthor Commented:
I looked in the classes all the way up the hierarchy, and there is no add method that is defined with "throws exception." I want to understand this so that I can communicate it to students. If an exception is reported, there must be a method somewhere that throws it.
0
 
objectsCommented:
Hang on I'll find it for you.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
objectsCommented:
Sorry, it's too early in the morning.
The exception won't be throw explicitly, it'll be thrown when you try and do something like this:

Object a = null;
String s = a.toString()  // This will cause a NPE to be thrown

I'll find the spot in the code where its occurring for you.
0
 
objectsCommented:
From the NPE javadoc:

Thrown when an application attempts to use null in a case where an object is required. These include:

- Calling the instance method of a null object.
- Accessing or modifying the field of a null object.
- Taking the length of null as if it were an array.
- Accessing or modifying the slots of null as if it were an array.
- Throwing null as if it were a Throwable value.
0
 
objectsCommented:
It's thrown from the addImpl method in the Container class.

Another easy way to find where an exception originated is to use the printStackTrace() method of the Exception class.

eg.

tr
{
   ....
}
catch (Exception e)
{
   e.printStackTrace();
}
0
 
HanRuiAuthor Commented:
Ok. I still want to see a method somewhere with throws exception in it. The priniciples that you listed make sense, but the more general principle is that for an exception to be thrown at all, there must be some method somewhere with "throws exception" as part of its definition.

java.lang.NullPointerException
  at java.awt.Container.addImpl(Compiled Code)
  at java.awt.Container.add(Compiled Code)
  at Test1.init(Compiled Code)
* at netscape.applet.DerivedAppletFrame$InitAppletEvent.dispatch(Compiled Code)
  at java.awt.EventDispatchThread$EventPump.dispatchEvents(Compiled Code)
  at java.awt.EventDispatchThread.run(Compiled Code)
  at netscape.applet.DerivedAppletFrame$AppletEventDispatchThread.run(Compiled Code)

The above is the message output in the Java console. The addImpl method does not throw an exception. I did see an IllegalArgumentException in the Container class, but no method with throws exception.
0
 
Igor BazarnyCommented:
Hi,

There is no need to declare 'throws Exception' to throw NulPointerException. Exception derived from RuntimeException end Error can be thrown from anywhere, no matter what throws clause says.
add() is method family of Container (not Component) and real implementation is in addImpl(). It's no wonder that it throws NullPointerException when you add null component. In fact, it prevents you from more serious problems--ability to add null component would possibly cause NullPointerException far from call to add().

You would better find a Label to add. And watch out, from my experience, NullPointerException is most often exception, and most helpful--you can tell from stacktrace where you try to use uninitialized reference. Much better than simply fall with 'General Protection Fault' message.

Regards,
Igor Bazarny
Brainbench MVP for Java 1
www.brainbench.com
0
 
HanRuiAuthor Commented:
Thank you. I already closed the question, but I appreciate your feedback.
0
 
objectsCommented:
The exception is thrown by the JVM as a result of calling a method on a null object reference.

Thanks for the points :)
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now