Bug 780527 (SOA-2962) - Importing ESB 5 examples, with a mis-named SOA5 runtime does not display the same level or detail of error as if no SOA5 runtime was installed
Summary: Importing ESB 5 examples, with a mis-named SOA5 runtime does not display the ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2962
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA
Assignee: Brian Fitzpatrick
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-04 02:57 UTC by Len DiMaggio
Modified: 2011-11-08 22:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-08 22:04:38 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2962 0 None None None Never

Description Len DiMaggio 2011-03-04 02:57:30 UTC 
project_key: SOA

Platform JIRA for project issue:  https://issues.jboss.org/browse/JBIDE-8516
Comment 1 Len DiMaggio 2011-03-04 02:58:13 UTC 
Link: Added: This issue depends JBIDE-8516
Comment 2 Brian Fitzpatrick 2011-06-21 20:15:00 UTC 
Based in JBIDE-8516, this has been resolved for JBDS 4.1 (in the M1 milestone), which will be supporting SOA-P 5.2.
Comment 3 Brian Fitzpatrick 2011-06-21 20:15:12 UTC 
See previous comment.
Comment 4 Len DiMaggio 2011-08-30 01:51:46 UTC 
Verified with:

SOA-P 5.2 ER3

and

JBDS
Version: 4.1.0.GA
Build id: v20110801-1408-H978-GA
Build date: 20110801-1408
Comment 5 David Le Sage 2011-11-08 01:27:27 UTC 
Temporarily reopening to update release note info.
Comment 6 David Le Sage 2011-11-08 22:04:17 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2962

If the user tried to import ESB5 examples and the SOA run-time was misnamed, it would display a different level of error and, subsequently, less detail than if no SOA run-time was installed at all.  The code has now been altered so that it displays the correct error level and details.
Note You need to log in before you can comment on or make changes to this bug.