[JBoss JIRA] (TEIIDDES-381) New Operations and Inputs must be renamed in the Web Service model.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-381?page=com.atlassian.jira.plug... ]
Ted Jones updated TEIIDDES-381:
-------------------------------
Fix Version/s: Future
> New Operations and Inputs must be renamed in the Web Service model.
> -------------------------------------------------------------------
>
> Key: TEIIDDES-381
> URL: https://issues.jboss.org/browse/TEIIDDES-381
> Project: Teiid Designer
> Issue Type: Bug
> Environment: 553 RC1
> Reporter: John Doyle
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: Future
>
>
> When you create a new Operation, or a new Input in a Web Service model, they are provided a default name. In order to provide a new name, you have to use the rename menu item. In contrast, when you create a new Table or Column in a Relational model, the new item is given focus in the model explorer and an edti box is opened to allow you the provide a name right away. We should be consistent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2518) 1024x768 Input set editor issue - not all options are visible
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2518?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2518:
----------------------------------------
Fix was to move the editor to a dialog triggered via an context menu action "Edit Input Set" (see attached images).
Attached a patch containing the changes
> 1024x768 Input set editor issue - not all options are visible
> -------------------------------------------------------------
>
> Key: TEIIDDES-2518
> URL: https://issues.jboss.org/browse/TEIIDDES-2518
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2
> Reporter: Matus Makovy
> Fix For: 9.2, 9.0.3
>
> Attachments: edit-input-set-action.png, edit-input-set-dialog.png, org-teiid-designer-mapping-ui.patch, screen1.png, screen2.png
>
>
> Not all options are visible when Input set editor is opened with resolution 1024 x 768. (screen1)
> Also resizing this model editor seems to produce additional issues. (screen2)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2518) 1024x768 Input set editor issue - not all options are visible
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2518?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2518:
-----------------------------------
Attachment: edit-input-set-dialog.png
edit-input-set-action.png
org-teiid-designer-mapping-ui.patch
> 1024x768 Input set editor issue - not all options are visible
> -------------------------------------------------------------
>
> Key: TEIIDDES-2518
> URL: https://issues.jboss.org/browse/TEIIDDES-2518
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2
> Reporter: Matus Makovy
> Fix For: 9.2, 9.0.3
>
> Attachments: edit-input-set-action.png, edit-input-set-dialog.png, org-teiid-designer-mapping-ui.patch, screen1.png, screen2.png
>
>
> Not all options are visible when Input set editor is opened with resolution 1024 x 768. (screen1)
> Also resizing this model editor seems to produce additional issues. (screen2)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2447:
----------------------------------------
Looks like the next ModeShape 3.8 patch will include the fix for this: MODE-2445 so we'll need to upgrade Designer's MS jars to include this patch version. (9.0.3)
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 9.2, 9.0.3
>
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2447:
-----------------------------------
Priority: Blocker (was: Critical)
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 9.2, 9.0.3
>
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months