Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8274939
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T07:54:00+00:00 2026-06-08T07:54:00+00:00

From Effective Java DOCUMENT ALL EXCEPTIONS THROWN BY EACH METHOD It should be noted

  • 0

From Effective Java “DOCUMENT ALL EXCEPTIONS THROWN BY EACH METHOD“

It should be noted that documenting all of the unchecked exceptions that each
method can throw is an ideal, not always achievable in the real world. When a
class undergoes revision, it is not a violation of source or binary compatibility if
an exported method is modified to throw additional unchecked exceptions.
Suppose a class invokes a method from another, independently written class. The
authors of the former class may carefully document all of the unchecked
exceptions that each method throws, but if the latter class is revised to throw
additional unchecked exceptions, it is quite likely that the former class (which has
not undergone revision) will propagate the new unchecked exceptions even
though it does not declare them.

I fail to understand how can former class propagate the new unchecked excpetions ? The java language doesn’t mandate the caller to catch and propagate unchecked exceptions .

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T07:54:02+00:00Added an answer on June 8, 2026 at 7:54 am

    It will propagate it precisely because exceptions are either caught or propagated. If not caught, an exception propagates:

    public void caller() {
        callee();
    }
    
    public void callee() {
        throw new RuntimeException();
    }
    

    In the above example, the exception thrown from callee() will be propagated by the caller() method, since caller() doesn’t catch it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Possible Duplicate: Unchecked exceptions in Java: Inherit from Error or RuntimeException? Looking at how
A quote from Effective Java states that: A second legitimate use of finalizers concerns
I am reading about clone from Effective Java It says that in clone the
I read from Effective Java that In the absence of synchronization the following sequence
I am trying to fathom the following lines from Effective Java One thing that
From Effective Java Second Edition, Item 28 : Do not use wildcard types as
Hey, what's the most effective way to remove beginning and ending slashes from all
From Effective Java 2nd edition item 67 page 266-268: The background thread calls s.removeObserver
I read Effective Java by Joshua Bloch and removed the 'Constant Interface anti-pattern' from
I am reading about double check locking from Effective Java . The code does

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.