exceptions = member classes ?

[Andy Jung]

Hi all,

The assignment says:

Any unimplemented exceptions in this interface must all be created as member classes of the suncertify.db package.

"Java in a Nutshell" defines member classes this way:

A member class is a class that is declared as a non-static member of a containing class.

I just placed those exceptions (RecordNotFoundException, DuplicateKeyException, SecurityException) in package suncertify.db,
without making them inner classes to any containing class.

Did I violate this requirement ?

Kind regards,
Andy

[Roel De Nijs]

Your exception classes should just be classes inside the db-package, not as inner classes of the Data class.

[Roberto Perillo]

Roel De Nijs wrote:Your exception classes should just be classes inside the db-package, not as inner classes of the Data class.

Agreed. And do not forget the constructors specified in the assignment!

[Andy Jung]

... ok, that's fine, I submitted the project yesterday anyways ...

[Matheus Mendes]

The spec says:

" ... member classes of the suncertify.db package..."

. Just put inside the package and it's alright.

Good lucky and keep on touch to let us know the positive result.

[David Kachen]

Hi All,

I do not think that the use of javax.ejb.DuplicateKeyException - is good. I think that we should make a new Exception.

I did as follows:
SecurityException already exists (in java.lang). RecordNotFoundException and DuplicateKeyException I have extends from java.lang.IllegalArgumentException.

A javax.ejb.DuplicateKeyException designed specifically for the EJB.

Best Regards..

[David Kachen]

I guess I was a little mistaken. I'm new at this forum, please forgive me if I'm wrong. In the first message I passed on the link and got to DuplicateKeyException javax.ejb.DuplicateKeyException. I thought that the developer decided not to create a DuplicateKeyException and instead use javax.ejb.DuplicateKeyException.
And as it turned out, the editor himself makes reference to the message.

Best Regards

[Roel De Nijs]

David Kachen wrote:I did as follows:
SecurityException already exists (in java.lang).

Javadoc of the SecurityException says:

Thrown by the security manager to indicate a security violation.

So i think you should create your own SecurityException instead of reusing this one (because your code will throw the exception and not a security manager)

Kind regards,
Roel

[David Kachen]

Thanks Roel, I think that you are right.