• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

What's wrong with this code????

 
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I get the following error message on compiling this code. Whats wrong with this I cannot figure out!!
Exception java.sql.SQLException is never thrown in the body of the corresponding try statement.


(edited by Cindy to format code - also hmehta,

Please change your name to be compliant with JavaRanch's naming policy.
Your displayed name should be 2 separate names with more than 1 letter each. We really would prefer that you use your REAL name.
You can change your name: here.
Thanks,
Cindy)

[ September 03, 2002: Message edited by: Cindy Glass ]
 
Ranch Hand
Posts: 396
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi hmehta,
This error comes when u r unnecessarily catching an exception. so it seems that throughout ur try block u r not using any function/statement that throws SQLException and still u r catching it. that's why compiler is complaining.
juct remove the try catch block and see if the program compiles.
regards
deekasha
 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi
you got the answer or not. what i'm thinking is, i can add any number of exception in such a order. Right!. But one guy is replied like, remove the exception, it will work.
let me know the status.
with regards
Prakash.M
(prakashem@rediffmail.com)
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
In my code ,i have called one method which might throw the exception. But in that method definition i just say throws Exception.
But the method in which i called this method should handle the SQLException seperatly.
Please help me regarding this.
 
Ranch Hand
Posts: 1056
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You are not allowed to catch a checked exception (such as SQLException) that can never be thrown.
Which method are you calling that should be throwing SQLException ?
 
Ranch Hand
Posts: 1879
MySQL Database Suse
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hmehta,
Please use the
UBB code tags when posting code. It is hard to read your post.
Besides your stated problem, heads up for this one:
if(status == "Available")
status is a String so you must compare the values of the String objects like this:
if( status.equals( "Available" ) )
or if( "Available".equals( status ) )
otherwise, you are comparing the references rather than the value of Strings.
Jamie
 
Jamie Robertson
Ranch Hand
Posts: 1879
MySQL Database Suse
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Another heads up for this potential problem:
...
+ " a.bkg_purpose = '" + bookingtext + "'"
+ status_sql;
where status_sql = "and a.bkg_confirmed = 'Y'" (or some other value)

When you go to execute your SQL, you are missing a space between the value of status_sql and the line before it. It will translate to something like " a.bkg_purpose = 'bookingtext_value'and a.bkg_confirmed = 'Y'"
Jamie
 
lakshmanan eswaramoorthy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
I didn't throw the exception in called method to the calling method . After throwing the exception,the code compiles correctly.
The wrong code
import java.sql.*;
class UseDBConn
{
public static void main(String[] args)
{
try
{
DBConn db = new DBConn;
String name=dbl.getName();
}
catch (SQLException e)
{
System.out.println("SQL Exception handled ");
}
catch (Exception e)
{
System.out.println("Exception throws");
}


}
}
public class DBConn
{
public String getName() {
try
{
//Some SQL Statements
}
catch (Exception e)
{
e.printStackTrace();

}finally{ con.close(); }
return //A string variable
}
}
Corrected Code
import java.sql.*;
class UseDBConn
{
public static void main(String[] args)
{
try
{
DBConn db = new DBConn;
String name=dbl.getName();
}
catch (SQLException e)
{
System.out.println("SQL Exception handled ");
}
catch (Exception e)
{
System.out.println("Exception throws");
}


}
}
public class DBConn
{
public String getName() throws Exception {
try
{
//Some SQL Statements
}
catch (Exception e)
{
e.printStackTrace();
throw e;
}finally{ con.close(); }
return //A string variable
}
}
Here I have one doubt.
Do i need to rethrow the exception in catch block?
Because i have given throws Exception in method definition
Thank you
 
Jamie Robertson
Ranch Hand
Posts: 1879
MySQL Database Suse
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"Here I have one doubt.
Do i need to rethrow the exception in catch block?
Because i have given throws Exception in method definition"
This is more of a design question. Do I want to deal with the exception in the method that it occurs, then use try/catch block. If you want to deal with the exception in the calling method, then you would not have any try/catch blocks in your method, but the method would have a throws clause. I guess that you could have a try/catch block, then throw another exception in the catch block ( deal with the problem, then pass it up as well ), but why would you need to deal with the same problem twice?
[ August 30, 2002: Message edited by: Jamie Robertson ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic