[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2259:
-----------------------------------
Attachment: Step2.png
Step3.png
Step4.png
new screenshots 8.3.4.
> Edit VDB Data Role dialogue doesn't check off checkboxes properly
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2259
> URL: https://issues.jboss.org/browse/TEIIDDES-2259
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Attachments: ReuseVDB_Dataroles.zip, screen1.png, Step2.png, Step3.png, Step4.png
>
>
> When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached
> JBDS 7.1.1.GA + Teiid Designer 8.3.3
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2259:
-----------------------------------
Attachment: ReuseVDB_Dataroles.zip
project
> Edit VDB Data Role dialogue doesn't check off checkboxes properly
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2259
> URL: https://issues.jboss.org/browse/TEIIDDES-2259
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Attachments: ReuseVDB_Dataroles.zip, screen1.png, Step2.png, Step3.png, Step4.png
>
>
> When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached
> JBDS 7.1.1.GA + Teiid Designer 8.3.3
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2401:
--------------------------------------
Summary: 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
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.3.8#6338)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2346) Deployment and undepoyment of Dynamic VDBs is not yet supported
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2346?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2346:
-----------------------------------
Fix Version/s: 9.1
> Deployment and undepoyment of Dynamic VDBs is not yet supported
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2346
> URL: https://issues.jboss.org/browse/TEIIDDES-2346
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.6
> Reporter: Barry LaFond
> Fix For: 9.1
>
>
> Attempted to *undeploy* a dynamic VDB on my server and Designer threw an exception. (see below)
> We should detect dynamic VDBs in our local VDB cache and maybe display differently (decoration) as well as dissallow Undeploy VDB on selection, or call the approprieate method *undeployDynamicVdb()* instead.
> {code}
> org.teiid.adminapi.AdminProcessingException: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014807: Management resource '[(\"deployment\" => \"DynamicProducts.vdb\")]' not found"}}
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.execute(Admin8Factory.java:548)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.undeploy(Admin8Factory.java:782)
> at org.teiid.runtime.client.admin.v8.Admin8Spec.undeploy(Admin8Spec.java:73)
> at org.teiid.runtime.client.admin.ExecutionAdmin.undeployVdb(ExecutionAdmin.java:773)
> at org.teiid.designer.runtime.TeiidServer.undeployVdb(TeiidServer.java:669)
> at org.teiid.designer.runtime.ui.views.TeiidServerActionProvider$4.run(TeiidServerActionProvider.java:236)
> {code}
> 1) ExecutionAdmin.undeployVdb() calls: *adminSpec.undeploy(admin, appendVdbExtension(vdbName), vdb.getVersion())*, so this call is assuming a *.vdb* extension, which fails for dynamic VDBs.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2389) Add ui support for whole texttable no trim
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2389?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2389:
-----------------------------------
Fix Version/s: 9.1
> Add ui support for whole texttable no trim
> ------------------------------------------
>
> Key: TEIIDDES-2389
> URL: https://issues.jboss.org/browse/TEIIDDES-2389
> Project: Teiid Designer
> Issue Type: Enhancement
> Environment: Teiid 8.8.0 Final
> Reporter: Shiveeta Mattoo
> Labels: File-connector, TEXTTABLE, TRIM
> Fix For: 9.1
>
>
> TEIID-3167 allows for NO TRIM to be specified against the whole texttable regardless of whether it is fixed width or delimited. If delimited, then unqualified entries will not be trimmed. For example:
> a , "b"
> would be parsed as
> a ,b - such that the space is preserved after a, but the qualified entry is unaffected.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2331) Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2331?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2331:
---------------------------------------------------
Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1136771|https://bugzilla.redhat.com/show_bug.cgi?id=1136771] from ASSIGNED to MODIFIED
> Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)
> -------------------------------------------------------------------
>
> Key: TEIIDDES-2331
> URL: https://issues.jboss.org/browse/TEIIDDES-2331
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.4, 8.6
> Environment: Windows 7
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 8.6.1, 9.0.1, 9.0
>
> Attachments: Dataroles_project.zip, log.log, screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png, screenshot5.png
>
>
> There is couple of issues with renaming source model that is referenced in some view model.
> I am using project Dataroles_project.zip (attached)
> 1. I tried to rename Products_source.xmi to Products_source1.xmi
> * this generates some error in log but it works...
> *[screenshot1.png]
> 2. Rename Products_source1.xmi to Products_source2.xmi
> * this fails to rewrite the reference in view model
> * I changed the references manually
> *[screenshot2.png and screenshot3.png]
> 3. Remane Products_source2.xmi to Products_source3.xmi
> * this deletes tables from view model
> *[screenshot4.png and screenshot5.png]
> This problem occurs only on Windows, Linux is fine...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months