[JBoss JIRA] (TEIIDDES-3045) Issues with creating SOAP WAR
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3045?page=com.atlassian.jira.plu... ]
Steve Tran updated TEIIDDES-3045:
---------------------------------
Attachment: Screenshot from 2017-02-24 14-40-13.png
> Issues with creating SOAP WAR
> -----------------------------
>
> Key: TEIIDDES-3045
> URL: https://issues.jboss.org/browse/TEIIDDES-3045
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.1, 10.1
> Environment: Windows 7, 64-bit
> JBoss Developer Studio 10.2.0.GA
> JBoss Data Virt Development (Teiid Designer) Integration Stack 10.1.0.GA
>
> Reporter: Steve Tran
> Attachments: Screenshot from 2017-02-24 14-40-13.png
>
>
> Creating the SOAP war file usually works the first time if it's a brand new file, but if I need to regenerate the file for whatever reason, I have to attempt it 3 to 4 times before it will actually work. I thought it was something filesystem related, so after each failed attempt, I would refresh my project tree using the double refresh arrows, or I would right-click on the parent node and click refresh. If I'm lucky, it'll work right after the refresh trick, but it usually takes 3-4 times of trying before it finally takes.
> This was also happening on JBDS 9.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3045) Issues with creating SOAP WAR
by Steve Tran (JIRA)
Steve Tran created TEIIDDES-3045:
------------------------------------
Summary: Issues with creating SOAP WAR
Key: TEIIDDES-3045
URL: https://issues.jboss.org/browse/TEIIDDES-3045
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 10.1, 9.1
Environment: Windows 7, 64-bit
JBoss Developer Studio 10.2.0.GA
JBoss Data Virt Development (Teiid Designer) Integration Stack 10.1.0.GA
Reporter: Steve Tran
Creating the SOAP war file usually works the first time if it's a brand new file, but if I need to regenerate the file for whatever reason, I have to attempt it 3 to 4 times before it will actually work. I thought it was something filesystem related, so after each failed attempt, I would refresh my project tree using the double refresh arrows, or I would right-click on the parent node and click refresh. If I'm lucky, it'll work right after the refresh trick, but it usually takes 3-4 times of trying before it finally takes.
This was also happening on JBDS 9.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3044) Add new Model Editor tab
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3044?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3044:
-----------------------------------
Attachment: Designer 11.1 New Features.pdf
> Add new Model Editor tab
> ------------------------
>
> Key: TEIIDDES-3044
> URL: https://issues.jboss.org/browse/TEIIDDES-3044
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, Modeling
> Affects Versions: 11.1
> Reporter: Barry LaFond
> Priority: Critical
> Fix For: 11.1
>
> Attachments: Designer 11.1 New Features.pdf, new-model-editor-and-data-sources-view.png
>
>
> Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
> The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
> One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
> The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
> Prototype KIT is available at: http://download.jboss.org/teiid/designer/11.0/teiid-designer-neon-prototy...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3044) Add new Model Editor tab
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3044?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3044:
-----------------------------------
Description:
Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
Prototype KIT is available at: teiid-designer-neon-prototype-3044-updatesite.zip
was:
Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
> Add new Model Editor tab
> ------------------------
>
> Key: TEIIDDES-3044
> URL: https://issues.jboss.org/browse/TEIIDDES-3044
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, Modeling
> Affects Versions: 11.1
> Reporter: Barry LaFond
> Priority: Critical
> Fix For: 11.1
>
> Attachments: new-model-editor-and-data-sources-view.png
>
>
> Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
> The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
> One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
> The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
> Prototype KIT is available at: teiid-designer-neon-prototype-3044-updatesite.zip
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3044) Add new Model Editor tab
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3044?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3044:
-----------------------------------
Description:
Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
Prototype KIT is available at: http://download.jboss.org/teiid/designer/11.0/teiid-designer-neon-prototy...
was:
Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
Prototype KIT is available at: teiid-designer-neon-prototype-3044-updatesite.zip
> Add new Model Editor tab
> ------------------------
>
> Key: TEIIDDES-3044
> URL: https://issues.jboss.org/browse/TEIIDDES-3044
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, Modeling
> Affects Versions: 11.1
> Reporter: Barry LaFond
> Priority: Critical
> Fix For: 11.1
>
> Attachments: new-model-editor-and-data-sources-view.png
>
>
> Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
> The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
> One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
> The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
> Prototype KIT is available at: http://download.jboss.org/teiid/designer/11.0/teiid-designer-neon-prototy...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-2990) Strange behaviour with multi-sources in dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2990?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2990:
-----------------------------------
Fix Version/s: 11.0.1
> Strange behaviour with multi-sources in dynamic VDB
> ---------------------------------------------------
>
> Key: TEIIDDES-2990
> URL: https://issues.jboss.org/browse/TEIIDDES-2990
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
> Attachments: ModelSourceVDB-vdb.xml
>
>
> Line 9 and 10 in dynamic VDB describe two sources.
> When you generate static VDB and check Source binding tab there is just one source model.
> He has Source name from line 9 but translator name and JNDI name from line 10.
> Also "Add Column" checkbox is not check.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-2990) Strange behaviour with multi-sources in dynamic VDB
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2990?page=com.atlassian.jira.plu... ]
Matej Kralik reopened TEIIDDES-2990:
------------------------------------
I tried to import dynamic vdb from the Attachments and generated models and static vdb from it. In the vdb editor is still uncheck Add column checkbox. However dynamic VDB contains this element:
{code:java}
<property name="multisource.addColumn" value="true"/>
{code}
What is a function of this checkbox?
> Strange behaviour with multi-sources in dynamic VDB
> ---------------------------------------------------
>
> Key: TEIIDDES-2990
> URL: https://issues.jboss.org/browse/TEIIDDES-2990
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Attachments: ModelSourceVDB-vdb.xml
>
>
> Line 9 and 10 in dynamic VDB describe two sources.
> When you generate static VDB and check Source binding tab there is just one source model.
> He has Source name from line 9 but translator name and JNDI name from line 10.
> Also "Add Column" checkbox is not check.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3044) Add new Model Editor tab
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3044?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3044:
-----------------------------------
Attachment: new-model-editor-and-data-sources-view.png
> Add new Model Editor tab
> ------------------------
>
> Key: TEIIDDES-3044
> URL: https://issues.jboss.org/browse/TEIIDDES-3044
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors, Modeling
> Affects Versions: 11.1
> Reporter: Barry LaFond
> Priority: Critical
> Fix For: 11.1
>
> Attachments: new-model-editor-and-data-sources-view.png
>
>
> Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
> The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
> One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
> The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3044) Add new Model Editor tab
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-3044:
--------------------------------------
Summary: Add new Model Editor tab
Key: TEIIDDES-3044
URL: https://issues.jboss.org/browse/TEIIDDES-3044
Project: Teiid Designer
Issue Type: Enhancement
Components: Editors, Modeling
Affects Versions: 11.1
Reporter: Barry LaFond
Priority: Critical
Fix For: 11.1
Attachments: new-model-editor-and-data-sources-view.png
Teiid Designer is an Eclipse application. We've gotten lots of feedback that the workflow is based on a developer paradigm and not necessarily a data-source/data-service paradigm.
The Model Explorer/Tree view + Properties View + Description View paired up with the Diagram and Table Editor pages do not provide a coherent UI for editing models. Users are required to select an object in the tree or diagram in order to find out what actions are available for that object, whether a Model or a model child (table, view, column, etc.)
One solution is to create a Model Editor page/tab which provides a more model-centric approach to editing a model and providing such actions.
The attached screen cap shows an initial approach which displays a tree view of the model contents and associated Actions, Properties and Description editor tabs which allow managing the majority of the workflow actions and steps.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months