not compiling class with abstract class ?

hi

i'm trying to do the following - basically get a fieldname from the columnbean, store it as string and put its value into variable x, then make this value a parameter of the getBlobAddNameBean method



i'm getting the following errors though



the thing is columnbean is not abstract according to the api



so how come its saying it is, whats invalid about the method declaration ?

cheers

chris

Chris,

Maybe i'm missing something here, but it looks like you left out the return type:
public getBlobAddNameBean(String x);
should be
public void getBlobAddNameBean...

also,
is this an abstract class? If so, you omitted the word abstract from the class declaration. If it is not an abstract class, then you cannot have the semicolon at the end of the method signature above; instead you need curly braces and a class definition.

Tony

no its not abstract - i've changed tot eh following from // Methods



and i'm getting the following error



i can't see why its doing this as columnbean is not an abstract class and i've already imported it using the import command ??

cheers

chris

The compiler says that the ColumnBean class is abstract. You've shown us all sorts of stuff, but none of it speaks to whether ColumnBean is abstract or not. How about a URL for the Javadoc for this class? How about the source code (or just the class declaration line?)

You're saying it's not abstract, but it apparently is, as that's what the compiler says. We can probably help you figure out how to understand why this is so, but you'll need to provide us some more information.

Chris, if you don't mind my asking, how did you get yourself into this position? Can you afford to take the time to have a step back and attend a Java course -- or read some intro Java books -- and come back to this problem with a little more basic knowledge? You really seem to be biting off way more than you can chew.
[ June 22, 2004: Message edited by: Ernest Friedman-Hill ]

yes, it is abstract - i'd convinced myself it wasn't because it didn't mention it in the javadoc api, i misread the javadoc and it was confirmed when i opened the compiled bean.