[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1389: -------------------------------------- Assignee: Barry LaFond -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1389 at 5/29/12 10:29 AM: ------------------------------------------------------------------ The action sets have been designed to handle mostly NEW objects (models, projects, VDBs) and do not take into account users will want to select and operate on EXISTING objects. I have the basic Action Set "stuff" ready to go so I'll try and check that in before lunch. TASKS: BARRY: 1, 2, 3 TED: 6 and 8 I think we can get this done... even maybe today :) 1) Create Project (BARRY) *(Think we need to turn this action into a CREATE OR SELECT project) 2) Create or Select "View" table (BARRY) *This action/dialog does NOT exist yet - correct *Thinking this dialog would have 2 parts *Model/Location with "New" and "Browse" buttons *Current View with "New" and "Browse" buttons *NEW would launch the "Create View" action or maybe combine 2 & 3? We could. I think "2" would/could be a re-usable action/dialog. If we customize it for this use-case be hard to re-use ok gotcha 3) Create REST procedure (BARRY ONLY CREATE BASIC EMPTY Procedure with name dialog) *This action/dialog does NOT exist yet - correct *What SQL would we generate here? Just the SQL from the Template dialog? That should work, at least for the GET *Looks like the Result set is just XML_Literal? Yes *Then we'd need to allow defining input parameters? Yes, or we could get the parameters from the inputs (if any) into the SELECT for the target virtual table 4) Create VDB *will already automatically add the "View" model which will add the sources as dependencies *Do we want to allow Selecting EXISTING VDB and add too it? *Users may already have a VDB with the EXISTING View model in it and just need to "Synchronize" ?? 5) Deploy VDB 6) Generate DS for VDB (TED) *Does this action exist yet ?? Don't think so 7) Generate REST WAR *Action Exists 8) Deploy REST WAR (TED) *Is this a "Designer Action" or JBDS? JBDS... "Mark as Deployable". Would need a server defined. *How do we access/perform this through Designer actions then?? Not sure we can *Then do we throw up a dialog that provides detailed instructions? or *... do we just set these instructions as the "Description" on action selection? *If user is d-clicking each Action, then maybe just a "Dialog" *Would be a new action/dialog which has as an input "description" or a custom "Instructions Panel" ?? Instructions panel? Seems like a dialog is fine. *Action & dialog should go in "designer.ui.common" ?? sure was (Author: blafond): The action sets have been designed to handle mostly NEW objects (models, projects, VDBs) and do not take into account users will want to select and operate on EXISTING objects. I have the basic Action Set "stuff" ready to go so I'll try and check that in before lunch. TASKS: BARRY: 1, 2, 3 TED: 6 and 8 I think we can get this done... even maybe today :) 1) Create Project (BARRY) *(Think we need to turn this action into a CREATE OR SELECT project) 2) Create or Select "View" table (BARRY) *This action/dialog does NOT exist yet - correct Thinking this dialog would have 2 parts *Model/Location with "New" and "Browse" buttons *Current View with "New" and "Browse" buttons NEW would launch the "Create View" action or maybe combine 2 & 3? We could. I think "2" would/could be a re-usable action/dialog. If we customize it for this use-case be hard to re-use ok gotcha 3) Create REST procedure (BARRY ONLY CREATE BASIC EMPTY Procedure with name dialog) *This action/dialog does NOT exist yet - correct *What SQL would we generate here? Just the SQL from the Template dialog? That should work, at least for the GET *Looks like the Result set is just XML_Literal? Yes *Then we'd need to allow defining input parameters? Yes, or we could get the parameters from the inputs (if any) into the SELECT for the target virtual table 4) Create VDB *will already automatically add the "View" model which will add the sources as dependencies *Do we want to allow Selecting EXISTING VDB and add too it? *Users may already have a VDB with the EXISTING View model in it and just need to "Synchronize" ?? 5) Deploy VDB 6) Generate DS for VDB (TED) *Does this action exist yet ?? Don't think so 7) Generate REST WAR *Action Exists 8) Deploy REST WAR (TED) *Is this a "Designer Action" or JBDS? JBDS... "Mark as Deployable". Would need a server defined. *How do we access/perform this through Designer actions then?? Not sure we can *Then do we throw up a dialog that provides detailed instructions? or *... do we just set these instructions as the "Description" on action selection? *If user is d-clicking each Action, then maybe just a "Dialog" *Would be a new action/dialog which has as an input "description" or a custom "Instructions Panel" ?? Instructions panel? Seems like a dialog is fine. *Action & dialog should go in "designer.ui.common" ?? sure -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1389 at 5/29/12 10:33 AM: ------------------------------------------------------------------ The action sets have been designed to handle mostly NEW objects (models, projects, VDBs) and do not take into account users will want to select and operate on EXISTING objects. I have the basic Action Set "stuff" ready to go so I'll try and check that in before lunch. TASKS: BARRY: 1, 2, 3 TED: 6 and 8 I think we can get this done... even maybe today :) *1* Create Project (BARRY) * (Think we need to turn this action into a CREATE OR SELECT project) *2* Create or Select "View" table (BARRY) * This action/dialog does NOT exist yet - correct * Thinking this dialog would have 2 parts * Model/Location with "New" and "Browse" buttons * Current View with "New" and "Browse" buttons * NEW would launch the "Create View" action or maybe combine 2 & 3? We could. I think "2" would/could be a re-usable action/dialog. If we customize it for this use-case be hard to re-use ok gotcha *3* Create REST procedure (BARRY ONLY CREATE BASIC EMPTY Procedure with name dialog) * This action/dialog does NOT exist yet - correct * What SQL would we generate here? Just the SQL from the Template dialog? That should work, at least for the GET * Looks like the Result set is just XML_Literal? Yes * Then we'd need to allow defining input parameters? Yes, or we could get the parameters from the inputs (if any) into the SELECT for the target virtual table *4* Create VDB * will already automatically add the "View" model which will add the sources as dependencies * Do we want to allow Selecting EXISTING VDB and add too it? * Users may already have a VDB with the EXISTING View model in it and just need to "Synchronize" ?? *5* Deploy VDB *6* Generate DS for VDB (TED) *Does this action exist yet ?? Don't think so *7* Generate REST WAR * Action Exists *8* Deploy REST WAR (TED) * Is this a "Designer Action" or JBDS? JBDS... "Mark as Deployable". Would need a server defined. * How do we access/perform this through Designer actions then?? Not sure we can * Then do we throw up a dialog that provides detailed instructions? or * ... do we just set these instructions as the "Description" on action selection? * If user is d-clicking each Action, then maybe just a "Dialog" * Would be a new action/dialog which has as an input "description" or a custom "Instructions Panel" ?? Instructions panel? Seems like a dialog is fine. * Action & dialog should go in "designer.ui.common" ?? sure was (Author: blafond): The action sets have been designed to handle mostly NEW objects (models, projects, VDBs) and do not take into account users will want to select and operate on EXISTING objects. I have the basic Action Set "stuff" ready to go so I'll try and check that in before lunch. TASKS: BARRY: 1, 2, 3 TED: 6 and 8 I think we can get this done... even maybe today :) # Create Project (BARRY) * (Think we need to turn this action into a CREATE OR SELECT project) # Create or Select "View" table (BARRY) * This action/dialog does NOT exist yet - correct * Thinking this dialog would have 2 parts * Model/Location with "New" and "Browse" buttons * Current View with "New" and "Browse" buttons * NEW would launch the "Create View" action or maybe combine 2 & 3? We could. I think "2" would/could be a re-usable action/dialog. If we customize it for this use-case be hard to re-use ok gotcha # Create REST procedure (BARRY ONLY CREATE BASIC EMPTY Procedure with name dialog) * This action/dialog does NOT exist yet - correct * What SQL would we generate here? Just the SQL from the Template dialog? That should work, at least for the GET * Looks like the Result set is just XML_Literal? Yes * Then we'd need to allow defining input parameters? Yes, or we could get the parameters from the inputs (if any) into the SELECT for the target virtual table # Create VDB * will already automatically add the "View" model which will add the sources as dependencies * Do we want to allow Selecting EXISTING VDB and add too it? * Users may already have a VDB with the EXISTING View model in it and just need to "Synchronize" ?? # Deploy VDB # Generate DS for VDB (TED) *Does this action exist yet ?? Don't think so # Generate REST WAR * Action Exists # Deploy REST WAR (TED) * Is this a "Designer Action" or JBDS? JBDS... "Mark as Deployable". Would need a server defined. * How do we access/perform this through Designer actions then?? Not sure we can * Then do we throw up a dialog that provides detailed instructions? or * ... do we just set these instructions as the "Description" on action selection? * If user is d-clicking each Action, then maybe just a "Dialog" * Would be a new action/dialog which has as an input "description" or a custom "Instructions Panel" ?? Instructions panel? Seems like a dialog is fine. * Action & dialog should go in "designer.ui.common" ?? sure -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1389 at 5/29/12 10:34 AM: ------------------------------------------------------------------ The action sets have been designed to handle mostly NEW objects (models, projects, VDBs) and do not take into account users will want to select and operate on EXISTING objects. I have the basic Action Set "stuff" ready to go so I'll try and check that in before lunch. TASKS: BARRY: 1, 2, 3 TED: 6 and 8 I think we can get this done... even maybe today :) 1) Create Project (BARRY) * Think we need to turn this action into a CREATE OR SELECT project 2) Create or Select "View" table (BARRY) * This action/dialog does NOT exist yet - correct * Thinking this dialog would have 2 parts * Model/Location with "New" and "Browse" buttons * Current View with "New" and "Browse" buttons * NEW would launch the "Create View" action or maybe combine 2 & 3? We could. I think "2" would/could be a re-usable action/dialog. If we customize it for this use-case be hard to re-use ok gotcha 3) Create REST procedure (BARRY ONLY CREATE BASIC EMPTY Procedure with name dialog) * This action/dialog does NOT exist yet - correct * What SQL would we generate here? Just the SQL from the Template dialog? That should work, at least for the GET * Looks like the Result set is just XML_Literal? Yes * Then we'd need to allow defining input parameters? Yes, or we could get the parameters from the inputs (if any) into the SELECT for the target virtual table 4) Create VDB * will already automatically add the "View" model which will add the sources as dependencies * Do we want to allow Selecting EXISTING VDB and add too it? * Users may already have a VDB with the EXISTING View model in it and just need to "Synchronize" ?? 5) Deploy VDB 6) Generate DS for VDB (TED) *Does this action exist yet ?? Don't think so 7) Generate REST WAR * Action Exists 8) Deploy REST WAR (TED) * Is this a "Designer Action" or JBDS? JBDS... "Mark as Deployable". Would need a server defined. * How do we access/perform this through Designer actions then?? Not sure we can * Then do we throw up a dialog that provides detailed instructions? or * ... do we just set these instructions as the "Description" on action selection? * If user is d-clicking each Action, then maybe just a "Dialog" * Would be a new action/dialog which has as an input "description" or a custom "Instructions Panel" ?? Instructions panel? Seems like a dialog is fine. * Action & dialog should go in "designer.ui.common" ?? sure was (Author: blafond): The action sets have been designed to handle mostly NEW objects (models, projects, VDBs) and do not take into account users will want to select and operate on EXISTING objects. I have the basic Action Set "stuff" ready to go so I'll try and check that in before lunch. TASKS: BARRY: 1, 2, 3 TED: 6 and 8 I think we can get this done... even maybe today :) 1) Create Project (BARRY) * (Think we need to turn this action into a CREATE OR SELECT project) 2) Create or Select "View" table (BARRY) * This action/dialog does NOT exist yet - correct * Thinking this dialog would have 2 parts * Model/Location with "New" and "Browse" buttons * Current View with "New" and "Browse" buttons * NEW would launch the "Create View" action or maybe combine 2 & 3? We could. I think "2" would/could be a re-usable action/dialog. If we customize it for this use-case be hard to re-use ok gotcha 3) Create REST procedure (BARRY ONLY CREATE BASIC EMPTY Procedure with name dialog) * This action/dialog does NOT exist yet - correct * What SQL would we generate here? Just the SQL from the Template dialog? That should work, at least for the GET * Looks like the Result set is just XML_Literal? Yes * Then we'd need to allow defining input parameters? Yes, or we could get the parameters from the inputs (if any) into the SELECT for the target virtual table 4) Create VDB * will already automatically add the "View" model which will add the sources as dependencies * Do we want to allow Selecting EXISTING VDB and add too it? * Users may already have a VDB with the EXISTING View model in it and just need to "Synchronize" ?? 5) Deploy VDB 6) Generate DS for VDB (TED) *Does this action exist yet ?? Don't think so 7) Generate REST WAR * Action Exists 8) Deploy REST WAR (TED) * Is this a "Designer Action" or JBDS? JBDS... "Mark as Deployable". Would need a server defined. * How do we access/perform this through Designer actions then?? Not sure we can * Then do we throw up a dialog that provides detailed instructions? or * ... do we just set these instructions as the "Description" on action selection? * If user is d-clicking each Action, then maybe just a "Dialog" * Would be a new action/dialog which has as an input "description" or a custom "Instructions Panel" ?? Instructions panel? Seems like a dialog is fine. * Action & dialog should go in "designer.ui.common" ?? sure -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1389: ----------------------------------- Summary: Create Action Sets for REST WAR Generation (was: Create Action Sets for REST/SOAP WAR Generation) Description: We need action sets for WAR generation: REST War actions set: Create project Create View (Full CRUD, if updated are required) Create procedure Assign REST properties Create VDB Add Models Deploy VDB Generate DS for VDB Generate REST WAR Deploy REST WAR was: We need action sets for WAR generation: REST War actions set: Create project Create View (Full CRUD, if updated are required) Create procedure Assign REST properties Create VDB Add Models Deploy VDB Generate DS for VDB Generate REST WAR Deploy REST WAR JBossWS-CXF (SOAP) War actions set: Create project Create Web Service Models Create VDB Add Models Deploy VDB Generate DS for VDB Generate JBossWS-CXF WAR Deploy JBossWS-CXF WAR -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-1389: ------------------------------------- Verbiage for the deploy WAR dialog: Deploying the generated WAR file: There are several ways to accomplish this: 1. If running Teiid Designer from JBDS or JBossTools: a.) Configure the target JBossAS. b.) Find the WAR file to your workspace (or add it if not there), right-click on the WAR file, and select "Mark as Deployable". The WAR will be automatically deployed to your configures JBossAS instance. OR 2. Copy the WAR file directly the deploy folder of the target JBossAS profile. OR 3. Use the administration console that comes with JBossAS located at http://{host:port}/admin-console/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1389?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1389. ------------------------------------ Resolution: Done DONE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira