[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1809:
--------------------------------
Fix Version/s: 9.0.5
9.3
(was: 9.0.4)
> WAR File (REST, SOAP) Creation usability enhancements
> ------------------------------------------------------
>
> Key: TEIIDDES-1809
> URL: https://issues.jboss.org/browse/TEIIDDES-1809
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.5, 9.3
>
>
> I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation
> 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create.
> 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide.
> 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2401:
-----------------------------------
Priority: Blocker (was: Major)
> Add support exporting the Designer VDB as Dynamic VDB
> -----------------------------------------------------
>
> Key: TEIIDDES-2401
> URL: https://issues.jboss.org/browse/TEIIDDES-2401
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 9.0.4, 9.2
>
> Attachments: generate-dynamic-vdb-page-1.png
>
>
> When a VDB is developed in the Designer, provide an option to export the given VDB as Dynamic VDB, which is simple XML format using DDL.
> The server already provides mechanism to retrieve the schema (DDL) for a given model. Using this technique of retrieving the DDL, this feature can be built.
> One caveat is support for XML document models in Dynamic VDB. When VDB contains XML document model, do not support this feature.
> This has couple benefits
> * Users can use these in Teiid for simplified usage.
> * Can used to check the models into source repository like GIT or SVN etc and compare with later versions for modifications
> * Open Shift
> As for importing of Dynamic VDB, that can be handled as separate issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months