Error with throwing different exceptions

[Nepomuk]

I have a encountered a weird problem. I have the following code:

public void connect() 
throws IOException, IllegalAccessException
{
    try
    {
        ftp.connect(server);
        ftp.login(username, password);
        ftp.setFileType(FTP.BINARY_FILE_TYPE);
        String reply = ftp.getReplyString(); 
        if(reply.indexOf("530") != -1) throw new IllegalAccessException(reply);
    }
    catch(SocketException se)
    {
        throw se;
    }
    catch(IOException ioe)
    {
        throw ioe;
    }
}

and I get the following runtime error:

Exception in thread "main" java.lang.Error: Unresolved compilation problem: 
    Exception IllegalAccessException is not compatible with throws clause in DownloadServiceClient.connect()
...

If however I add arguments to the methods call, e.g.

public void connect(int a) 
throws IOException, IllegalAccessException
...

it works perfectly.

I'm using compilance level 1.3, as this project should be runnable on old systems. Oh, and that ftp object is a org.apache.commons.net.ftp.FTPClient (not that that would make any difference at this point, as far as I can tell).

By the way, it doesn't matter, if it's an IllegalAccessException, a FileNotFoundException or any other Exception that I have tested. It's always the same error.

Can anyone help me in my confusion?

Greetings,
Nepomuk

[JosAH]

What exactly is the throws clause of the DownloadServiceClient.connect() method?

kind regards,

Jos

[Nepomuk]

What exactly is the throws clause of the DownloadServiceClient.connect() method?

kind regards,

Jos

OK, I should have specified:

public class DownloadServiceClient {
...
public void connect() 
throws IOException, IllegalAccessException
{
    try
    {
        ftp.connect(server);
        ftp.login(username, password);
        ftp.setFileType(FTP.BINARY_FILE_TYPE);
        String reply = ftp.getReplyString(); 
        if(reply.indexOf("530") != -1) throw new IllegalAccessException(reply);
    }
    catch(SocketException se)
    {
        throw se;
    }
    catch(IOException ioe)
    {
        throw ioe;
    }
}
...
}

So the thows clause is: throws IOException, IllegalAccessException, right?

Greetings,
Nepomuk

[Nepomuk]

Arg, found the error. Sorry, silly mistake. It isn't the class DownloadServiceClient but DownloadServiceFTPClient that method came from, DownloadServiceClient being an interface... Anyway, problem solved. Thanks!

Greetings,
Nepomuk

[JosAH]

So the thows clause is: throws IOException, IllegalAccessException, right?

Yep, as far as I can see; what I don't understand is, you're talking about a Runtime
error while that error diagnostic message is talking about an unresolved compilation
problem. Your compiler must've whined there as well when you were compiling
your class.

kind regards,

Jos

[JosAH]

Anyway, problem solved. Thanks!

What was it then?

kind regards,

Jos

[Nepomuk]

What was it then?

kind regards,

Jos

I have an interface DownloadServiceClient with

/**
 * Connect to the given Server
 */
public void connect() throws IOException;

and a class DownloadServiceFTPClient with two connect methods - one with and one without arguments. I had not added the IllegalAccessException to the throw cause in my interface, so that wouldn't work. The other connect method wasn't interfaced, so it worked fine.
Oh, the thing about the compiler was a bit weird. I'm using Eclipse with jdk1.4.2 and it did say something like "There are errors in your project. Still continue?" It did compile, without complaining further (it should have, shouldn't it?) and then threw the error at runtime.

Anyway, I'm glad the error is resolved.

Greetings,
Nepomuk

[JosAH]

I have an interface DownloadServiceClient with

/**
 * Connect to the given Server
 */
public void connect() throws IOException;

and a class DownloadServiceFTPClient with two connect methods - one with and one without arguments. I had not added the IllegalAccessException to the throw cause in my interface, so that wouldn't work. The other connect method wasn't interfaced, so it worked fine.
Oh, the thing about the compiler was a bit weird. I'm using Eclipse with jdk1.4.2 and it did say something like "There are errors in your project. Still continue?" It did compile, without complaining further (it should have, shouldn't it?) and then threw the error at runtime.

Well, it already complained but you choose to ignore it; never run anything when
Eclipse whines about errors in the project (see those little red marks near the
files in your package browser). Eclipse is ruthless and you get what you deserve ;-)

kind regards,

Jos

[Nepomuk]

Well, it already complained but you choose to ignore it; never run anything when
Eclipse whines about errors in the project (see those little red marks near the
files in your package browser). Eclipse is ruthless and you get what you deserve ;-)

kind regards,

Jos

Actually, I chose to ignore it so as to find a out, where the error would strike. I did find out. In this case, that knowledge was useless, but it won't always be! :-D

Greetings,
Nepomuk