This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
We have one AppException extending Exception and this is thrown from a session bean and caught by the client. The client is not doing any thing with this exception, not even printing its message. What I observe is that constructor AppException(String message) is being invoked on the client side. Why is this happening ?
Why is what happening? The only thing that is happening is that someone is ignoring an exception. Why? Because that person needs to learn correct software design practices. I can offer no further explanation.
What's the protocol between client & server? If it's just a plain old Java call I'm confused. If it's something remote like EJB or RMI the local end of the protocol is probably deserializing the exception so it can throw it in the client JVM.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
This is an EJB scenario thru RemoteInterfaces. I am assuming that Constructors (in this case) would not be invoked during deserialization - would they ?? Also, it the MyException(message) constructor which is invoked always - not the default constructor. For the record - the server is weblogic81 and jdk 142.