Bug 780490 (SOA-2919)

Summary:	EDS exceptions are very vague
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Martin Vecera <mvecera>
Component:	EDS	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.CR1	CC:	vhalbert
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2919
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-24 18:28:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Martin Vecera 2011-02-16 15:05:47 UTC

project_key: SOA

Exceptions thrown by EDS are not very helpful and descriptive. The messages are like "Error occured".
User might not recognize where a problem is. It is hard to develop applications with EDS since the bug tracking is very difficult without proper error message.

Comment 1 Van Halbert 2011-02-16 15:15:43 UTC

Link: Added: This issue Cloned to SOA-2920

Comment 2 Van Halbert 2011-02-17 20:11:51 UTC

(Per Steve Hawkins) This seems overly general. Teiid exceptions generally contain detailed messages and a detailed exception chain. Can you provide examples when this is occurring and what you would like to see instead?

Comment 3 Van Halbert 2011-02-24 18:28:14 UTC

Marking as incomplete until additional information / examples are provided.