Bug 780264 (SOA-2661) - The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS
Summary: The ability to execute a Teiid VDB seems in conflict with the Run As... optio...
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2661
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling, EDS
Version: 5.1.0.ER5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-09 19:45 UTC by John Verhaeg
Modified: 2011-09-15 19:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-15 19:55:34 UTC
Type: Feature Request


Attachments (Terms of Use)


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

Description John Verhaeg 2010-12-09 19:45:55 UTC
project_key: SOA

If you open the context menu for a VDB, the top-level menu contains Run As..., Debug As..., and Modeling submenus.  I have no idea how Debug As... would even apply, but Run As... certainly seems like the intuitive option to choose if you want to execute a VDB, especially considering the submenu contains the single entry Run on Server.  But that, of course, isn't correct and produces nothing more than an error message about no resources being available to execute; the user is supposed to instead choose Modeling > Execute VDB to run the VDB on the server.  It seems like we should remove the Execute option under the Modeling submenu and instead intercept the Run As... > Run on Server option to do the right thing, or alternatively, remove/disable the Run As.../Debug As... menu option when a VDB is selected.

Comment 1 Barry LaFond 2010-12-13 19:58:24 UTC
Link: Added: This issue Cloned to SOA-2682


Comment 2 Anne-Louise Tangring 2010-12-14 19:05:03 UTC
This is a candidate for SOA 5.1.0. Ken and Van to discuss

Comment 4 Dana Mison 2011-01-05 00:08:20 UTC
Writer: Added: Darrin


Comment 5 Van Halbert 2011-05-11 19:43:34 UTC
Link: Added: This issue is duplicated by SOA-2867


Comment 6 Van Halbert 2011-05-11 19:44:10 UTC
Link: Removed: This issue is duplicated by SOA-2867 


Comment 7 Van Halbert 2011-09-15 19:55:34 UTC
This was an internally logged jira, for which the engineers are even considering rejecting.   This is one request that probably won't get fixed unless a client would make this an issue, but then a new jira could be opened.  Therefore, at this point, this is being rejected.


Note You need to log in before you can comment on or make changes to this bug.