[JBoss JIRA] (TEIIDDES-2542) REST connection profile parameters settings problems (adding + deleting)
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2542?page=com.atlassian.jira.plu... ]
Andrej Šmigala updated TEIIDDES-2542:
-------------------------------------
Fix Version/s: (was: 9.0.2 Beta2)
> REST connection profile parameters settings problems (adding + deleting)
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-2542
> URL: https://issues.jboss.org/browse/TEIIDDES-2542
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 9.0.2
> Environment: MAC OS X
> Reporter: Matus Makovy
> Assignee: Ted Jones
> Priority: Critical
> Fix For: 9.1
>
> Attachments: paramters.mov
>
>
> There is a couple of issues with adding and deleting parameters.
> See attached video.
> Issue discovered on MAC OS X.
> When adding parameter after changes in Type of previously added parameters the dialogue duplicates previously added parameters.
> Afterwards there is problem with deleting parameters.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2541) Issues with Rest connection profile security settings
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2541?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2541:
------------------------------------------
Removed 9.0.2 from Fix version as this is not going to be included in the final build
> Issues with Rest connection profile security settings
> -----------------------------------------------------
>
> Key: TEIIDDES-2541
> URL: https://issues.jboss.org/browse/TEIIDDES-2541
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1
>
>
> When creating REST connection profile there is couple of issues with security settings:
> 1.) When user changes security settings to HTTP basic and doesn't enter any credentials Wizard shows error, but user is able to finish the creation without problems
> 2.) When user changes security settings to HTTP basic and then they want to change it back to 'none', wizard complains that there is no username entered and won't let you finish the creation of the connection profile.
> See video in comments (too big for JIRA)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2532) 1024 x 768 - Reconciler - not all buttons are visible
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2532?page=com.atlassian.jira.plu... ]
Andrej Šmigala updated TEIIDDES-2532:
-------------------------------------
Fix Version/s: (was: 9.0.2)
(was: 9.0.2 Beta2)
> 1024 x 768 - Reconciler - not all buttons are visible
> -----------------------------------------------------
>
> Key: TEIIDDES-2532
> URL: https://issues.jboss.org/browse/TEIIDDES-2532
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 9.0.2
> Environment: Mac OS X
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 8.6.2
>
> Attachments: Screen Shot 2015-05-19 at 1.32.08 PM.png, Screen Shot 2015-05-19 at 1.32.19 PM.png, Screen Shot 2015-05-19 at 1.32.41 PM.png, Screen Shot 2015-05-19 at 1.32.49 PM.png
>
>
> I can not see all buttons in reconciler when it opens. Type resolver button is completely hidden.
> This problem is also in Type resolver dialogue.
> User can enlarge the window and the button will show, but when the dialogue opens user doesn't know that there is Type resolver button.
> Screenshots attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2532) 1024 x 768 - Reconciler - not all buttons are visible
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2532?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2532:
------------------------------------------
Removed 9.0.2 from Fix version as this is not going to be included in the final build
> 1024 x 768 - Reconciler - not all buttons are visible
> -----------------------------------------------------
>
> Key: TEIIDDES-2532
> URL: https://issues.jboss.org/browse/TEIIDDES-2532
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 9.0.2
> Environment: Mac OS X
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 8.6.2
>
> Attachments: Screen Shot 2015-05-19 at 1.32.08 PM.png, Screen Shot 2015-05-19 at 1.32.19 PM.png, Screen Shot 2015-05-19 at 1.32.41 PM.png, Screen Shot 2015-05-19 at 1.32.49 PM.png
>
>
> I can not see all buttons in reconciler when it opens. Type resolver button is completely hidden.
> This problem is also in Type resolver dialogue.
> User can enlarge the window and the button will show, but when the dialogue opens user doesn't know that there is Type resolver button.
> Screenshots attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2456) Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2456?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2456.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2456
> URL: https://issues.jboss.org/browse/TEIIDDES-2456
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 9.0.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: screenshot.png
>
>
> Import using Teiid Connection sometimes fails with the following error message after getting the DDL from server and clicking Next:
> {code}
> Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null"
> {code}
> Stacktrace:
> {code}
> !ENTRY org.teiid.designer.ddl.importer.ui 4 0 2015-03-23 14:58:16.966
> !MESSAGE Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null"
> !STACK 0
> java.lang.Exception: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:54)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:101)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:225)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.core.ModelEditorImpl.getModelName(ModelEditorImpl.java:4971)
> at org.teiid.designer.relational.model.RelationalReferenceFactory.createRelationalModel(RelationalReferenceFactory.java:65)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:188)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:117)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:41)
> ... 3 more
> {code}
> (02:50:28 PM) blafond: I'll need a stack trace to figure it out
> (02:50:35 PM) blafond: check Designer's Error Log view?
> (02:50:39 PM) asmigala: the weird thing is, it sometimes works for the same data source
> (02:50:42 PM) asmigala: ok, hang on a sec
> (02:50:53 PM) asmigala: so this is not something we know about?
> (02:51:34 PM) blafond: not as a reproduceable bug.
> ...
> (02:59:47 PM) asmigala: also, when I copy the DDL, save it to a file and then use the DDL importer, it works correctlu
> 03:05:15 PM) blafond: I think it's a threading/timing issue. The RelationalReferenceFactory is assuming that the new EMF Model already created. Looks like it's still in the process "sometimes" and ends up failing.
> (03:05:45 PM) blafond: I noticed that we don't save the model right after we create it. Maybe that could fix the issue.
> (03:06:05 PM) blafond: Please log a JIRA/BZ and include all of this conversation
> (03:06:59 PM) asmigala: yes, that makes sense, I generally don't see it when stepping through the test
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2456) Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2456?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2456:
--------------------------------------
Reopening to set label
> Teiid Connection Importer: IllegalArgumentException after obtaining the DDL from server
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2456
> URL: https://issues.jboss.org/browse/TEIIDDES-2456
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 9.0.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: screenshot.png
>
>
> Import using Teiid Connection sometimes fails with the following error message after getting the DDL from server and clicking Next:
> {code}
> Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null"
> {code}
> Stacktrace:
> {code}
> !ENTRY org.teiid.designer.ddl.importer.ui 4 0 2015-03-23 14:58:16.966
> !MESSAGE Error encountered while importing the DDL: "java.lang.IllegalArgumentException: Expected argument to be non-null but got null"
> !STACK 0
> java.lang.Exception: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:54)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:101)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:225)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.core.ModelEditorImpl.getModelName(ModelEditorImpl.java:4971)
> at org.teiid.designer.relational.model.RelationalReferenceFactory.createRelationalModel(RelationalReferenceFactory.java:65)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:188)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:117)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:41)
> ... 3 more
> {code}
> (02:50:28 PM) blafond: I'll need a stack trace to figure it out
> (02:50:35 PM) blafond: check Designer's Error Log view?
> (02:50:39 PM) asmigala: the weird thing is, it sometimes works for the same data source
> (02:50:42 PM) asmigala: ok, hang on a sec
> (02:50:53 PM) asmigala: so this is not something we know about?
> (02:51:34 PM) blafond: not as a reproduceable bug.
> ...
> (02:59:47 PM) asmigala: also, when I copy the DDL, save it to a file and then use the DDL importer, it works correctlu
> 03:05:15 PM) blafond: I think it's a threading/timing issue. The RelationalReferenceFactory is assuming that the new EMF Model already created. Looks like it's still in the process "sometimes" and ends up failing.
> (03:05:45 PM) blafond: I noticed that we don't save the model right after we create it. Maybe that could fix the issue.
> (03:06:05 PM) blafond: Please log a JIRA/BZ and include all of this conversation
> (03:06:59 PM) asmigala: yes, that makes sense, I generally don't see it when stepping through the test
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2454) Create feature to generate REST-enabled virtual procedures from selected views
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2454?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2454:
--------------------------------------
Reopening to set label
> Create feature to generate REST-enabled virtual procedures from selected views
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-2454
> URL: https://issues.jboss.org/browse/TEIIDDES-2454
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Web Services Support
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 9.0.2
>
> Attachments: generate-rest-vps-dialog.png, generate-rest-vps-example-results.png, generate-rest-vps-menu.png
>
>
> The WebUI data service functionality features auto-generating a REST-enabled virtual procedure which, when deployed in Teiid, get's exposed as a REST web service.
> To facilitate this same functionality in Designer....
> 1) Create *Modeling > Create REST Procedures*
> - enable only for Virtual Model selection or one or more virtual tables selected
> 2) Present a wizard containing a check-box list of views within the virtual model that have NOT been
> 3) List would include SELECT ALL, DESELECT ALL buttons
> - Could also use our Accumulator panel since some views may already have an associated REST procedure.
> 4) May require one or more design-time only extension properties to keep track of what views have generated REST procedures and which don't.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2454) Create feature to generate REST-enabled virtual procedures from selected views
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2454?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2454.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Create feature to generate REST-enabled virtual procedures from selected views
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-2454
> URL: https://issues.jboss.org/browse/TEIIDDES-2454
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Web Services Support
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 9.0.2
>
> Attachments: generate-rest-vps-dialog.png, generate-rest-vps-example-results.png, generate-rest-vps-menu.png
>
>
> The WebUI data service functionality features auto-generating a REST-enabled virtual procedure which, when deployed in Teiid, get's exposed as a REST web service.
> To facilitate this same functionality in Designer....
> 1) Create *Modeling > Create REST Procedures*
> - enable only for Virtual Model selection or one or more virtual tables selected
> 2) Present a wizard containing a check-box list of views within the virtual model that have NOT been
> 3) List would include SELECT ALL, DESELECT ALL buttons
> - Could also use our Accumulator panel since some views may already have an associated REST procedure.
> 4) May require one or more design-time only extension properties to keep track of what views have generated REST procedures and which don't.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2446) Transformation editor fails to open
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2446?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2446.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Transformation editor fails to open
> -----------------------------------
>
> Key: TEIIDDES-2446
> URL: https://issues.jboss.org/browse/TEIIDDES-2446
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 9.0.2 Beta2, 9.0.2
>
>
> Transformation editor fails to open when Designer is set to connect with later versions of the Teiid.
> 1) it should work with later versions Teiid
> 2) It should always should be able to open the transformation editor
> The below is the exception in the .log file
> !ENTRY org.teiid.designer.transformation 4 0 2015-03-09 09:57:40.875
> !MESSAGE java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> !STACK 0
> java.lang.RuntimeException: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2199)
> at org.teiid.designer.transformation.aspects.sql.SqlTransformationMappingRootSqlAspect.parseSQL(SqlTransformationMappingRootSqlAspect.java:522)
> at org.teiid.designer.transformation.aspects.sql.SqlTransformationMappingRootSqlAspect.getTransformationInfo(SqlTransformationMappingRootSqlAspect.java:386)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
> at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
> at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
> at org.teiid.designer.core.index.Index.add(Index.java:127)
> at org.teiid.designer.core.index.ModelIndexer.indexResource(ModelIndexer.java:240)
> at org.teiid.designer.core.builder.VdbModelBuilder.indexResource(VdbModelBuilder.java:265)
> at org.teiid.designer.core.builder.VdbModelBuilder.indexResources(VdbModelBuilder.java:290)
> at org.teiid.designer.core.builder.VdbModelBuilder.indexResources(VdbModelBuilder.java:281)
> at org.teiid.designer.core.builder.VdbModelBuilder.buildResources(VdbModelBuilder.java:125)
> at org.teiid.designer.vdb.VdbIndexedEntry.synchronizeIndex(VdbIndexedEntry.java:199)
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:612)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:444)
> at org.teiid.designer.vdb.Vdb.addEntry(Vdb.java:358)
> at org.teiid.designer.runtime.preview.jobs.CreatePreviewVdbJob.runImpl(CreatePreviewVdbJob.java:170)
> at org.teiid.designer.runtime.preview.jobs.WorkspacePreviewVdbJob.runInWorkspace(WorkspacePreviewVdbJob.java:129)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2197)
> ... 20 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2520) Teiid Connection Import fails when model name is set before model location
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2520?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2520.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Teiid Connection Import fails when model name is set before model location
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2520
> URL: https://issues.jboss.org/browse/TEIIDDES-2520
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.2
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta2, 9.0.2 Beta2, 9.0.2, 8.6.2
>
>
> When going through the Teiid Connection Import wizard, setting model name before selecting the model project on the _Select the target model for the import_ page causes the import to fail. This happens when no model project was previously selected.
> When a model project is already selected, changing the model project on that page, after setting the model name, causes the new model to be created in the wrong project.
> Selecting the model project first and then setting the model name does not cause any of these issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years