[JBoss JIRA] (TEIIDDES-1998) Connection Profile loses Binding Type
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1998?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1998:
-----------------------------------
Fix Version/s: 8.6
> Connection Profile loses Binding Type
> -------------------------------------
>
> Key: TEIIDDES-1998
> URL: https://issues.jboss.org/browse/TEIIDDES-1998
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration, Modeling
> Affects Versions: 8.3
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.3.4, 8.6
>
>
> Whenever importing WSDL into Source model, the connection profile loses it's binding info and I am required to edit the CP and add the binding info with each import. We should find a way to persist it or some other way to get the binding for import.
> The error is: "Connection Profile is invalid since it does not contain the required property DefaultBinding".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 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:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1136771|https://bugzilla.redhat.com/show_bug.cgi?id=1136771] from NEW to ASSIGNED
> 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: Mark Drilling
> Fix For: 8.7, 8.3.5
>
> 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.1#6329)
11 years, 7 months
[JBoss JIRA] (TEIIDDES-2247) Identify a framework for warning when a function is not compatible with a Designer version
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2247?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2247:
-----------------------------------
Fix Version/s: 8.3.5
(was: 8.3.4)
> Identify a framework for warning when a function is not compatible with a Designer version
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2247
> URL: https://issues.jboss.org/browse/TEIIDDES-2247
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Dialogs
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.5, 8.3.5
>
>
> When a vdb is created in Designer 8.5 and includes a data-role, this adds to the vdb.xml the grant-all element. This element is not applicable to Designer versions older that 8.5 hence any attempt to open this vdb in Designer 8.3.4 results in a cvc exception. Rather than allowing display of a cryptic error, it would be better to display a warning/error message that the vdb concerned is not compatible with the older version of Designer due to the grant-all element.
> Create a generic framework that can be plugged into such errors so that a standard message can be returned and it becomes trivial to insert checks into older Designer versions for 'future' functionality.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months