[GERONIMO-581] Deployer unaware of org.tranql.ql.QueryException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-M3
• Fix Version/s: 1.0-M4
• Component/s: deployment, OpenEJB
• Assignee: Gianny Damour
• Reporter: Aaron Mulder
• Created: 13/Feb/05 14:01
• Updated: 07/Aug/06 15:05
• Resolved: 12/Mar/05 15:56

Description

When an EJB deployment throws a TranQL QueryException, the deployer just gets a big stack trace for a ClassNotFoundException, concealing the actual exception. We usually put exceptions of this nature in Geronimo/Common. It looks like in this case we wrap the TranQL exception in a Geronimo DeploymentException before throwing it, but the Geronimo exception uses the TranQL exception as a chained exception (enough to cause the CNFE) and does not itself contain the error message. So the DeploymentException should have no chained exception, and should itself contain the error message.

Issue Links

• is duplicated by: GERONIMO-874 Deployer should not throw exceptions that cannot be deserialized