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.
posted 10 years ago
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.