I didn't realize you could do that. Of course until today I hadn't
found any reason why I'd want too :).
Guess you learn something new every day!
---Steve
> Actually an interface class can extend multiple interface classes.
> This sounds a bit strange but is very useful. A common usage in EJB
> is to create a business interface for a bean that is extended by the
> remote interface and implemented by the bean class. This allows
> signature errors to be caught at compile time instead of deployment time.
>
> A concrete or abstract class cannot extend multiple concrete or
> abstract classes.
>
> Scot.
>
> Steve Stearns wrote:
>
>>> It sure looks like everything is OK since public interface Category
>>> extends
>>> EJBObject and EJBObject is serializable. Often the problem is that the
>>> method arguments don't implement java.io.Serializable. Try
>>> explicitly making
>>> Category extend java.io.Serializable as well.
>>
>>
>> Java doesn't permit classes to extend more than one class. Since
>> Category is already extending EJBObject, I cannot also have it extend
>> Serializable. Also, since Category is itself an Interface I cannot
>> have it implement the Serializable interface.
>>
>> ---Steve
>>
>>
>>
>> --
>> --------------------------------------------------------------
>> To subscribe: [EMAIL PROTECTED]
>> To unsubscribe: [EMAIL PROTECTED]
>> List Help?: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
