[JBoss JIRA] Created: (TEIIDDES-222) Hide "Connector Types" by default in Connector window
by Ramesh Reddy (JIRA)
Hide "Connector Types" by default in Connector window
-----------------------------------------------------
Key: TEIIDDES-222
URL: https://jira.jboss.org/jira/browse/TEIIDDES-222
Project: Teiid Designer
Issue Type: Task
Components: VDB & Execution
Affects Versions: 6.1.0
Reporter: Ramesh Reddy
When user creates a Connector binding manually or one created automatically due to the import process, the created binding will not readily visible in the "Connectors" window, thus confuses the user. in rder to find the newly created "Connector", they need to scroll down or "hide connector types" before it can be found.
It would be better the "Connector Types" are hidden by default, as they do not provide any real information by being visible. They are only required by the user during the creation of the "Connector" where they are shown anyway.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-224) The ConfigurationInfo.def file has verbose settings for the ComponentTypes
by Ramesh Reddy (JIRA)
The ConfigurationInfo.def file has verbose settings for the ComponentTypes
--------------------------------------------------------------------------
Key: TEIIDDES-224
URL: https://jira.jboss.org/jira/browse/TEIIDDES-224
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 6.1.0
Reporter: Ramesh Reddy
Fix For: 6.2.0
Currently when VDB is written, the <ComponentTypes> section in the ConfigurationInfo.def file defines the component types for all the bindings defined. However the number of properties defined for each component type include all the properties in hierarchy of that Component Type. Which verbose and confusing.
For example in Configuration.XML file a "Oracle Connector" defined with it's hierarchy as
Oracle Connector --> JDBC Connector --> Connector
where Teiid defines properties at each level, but when the def file these properties are flattened and all properties are written under component type "Oracle Connector".
Looking at the issue, "ComponentType" fragment of the XML is optional, if the connector type is already in the "configuration.xml". However, designer still need to write the ComponentType information for custom connector types as that information will not be in the configuration.xml file.
To determine, if a connector type is already in the "configuration.xml", the designer can check a property called "standard", if the value is "true" it can safely ignore adding the component type to the .def file.
Teiid will supply the configuration.xml file with "standard" property set on all the built in types.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-243) Request to have Root cause of connector error in designer SQL Explorer dialog instead of 'CapabilitiesMessage'
by Debbie Steigner (JIRA)
Request to have Root cause of connector error in designer SQL Explorer dialog instead of 'CapabilitiesMessage'
--------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-243
URL: https://jira.jboss.org/jira/browse/TEIIDDES-243
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Debbie Steigner
Fix For: 6.1.0
In the designer, when a connector can't start and throws an exception, it pops up a dialog that says:
"Unable to create a connection for request com.metamatrix.dqp.message.CapabilitiesMessage@1cee695"
However, this is not the root cause exception, so every time it happens, one must find the exception in the log and find the root cause. The root cause is often something to do with bad credentials, or an expired password, or the like. Not having this is really irritating and needlessly time-consuming.
So, the feature request is to drill down in the exception stack trace to the root cause and report it's message in the dialog.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-223) Loaded Connectors dialog is empty
by Ramesh Reddy (JIRA)
Loaded Connectors dialog is empty
---------------------------------
Key: TEIIDDES-223
URL: https://jira.jboss.org/jira/browse/TEIIDDES-223
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 6.2.0
Reporter: Ramesh Reddy
I then defined my connector and dragged my model into it. That part
> seems to be fine.
>
> Just when I go to my VDB definition, on the "Execute" page, I need to
> assign a connector in order for my VDB to be able to execute.
>
> But I just cannot select my pre-defined connector there as the "Loaded
> Connectors" tab is empty. I can define a new connector there, using the
> same properties as my existing connector, but just using a different
> name, and it will work fine.
Loaded Bindings must have shown my previous binding to select from.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-200) Source Model Not Added To VDB Execution Page Of VDB Editor
by Dan Florian (JIRA)
Source Model Not Added To VDB Execution Page Of VDB Editor
----------------------------------------------------------
Key: TEIIDDES-200
URL: https://jira.jboss.org/jira/browse/TEIIDDES-200
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 6.1.0
Environment: Ubuntu 8.04
Reporter: Dan Florian
Fix For: Future
Attachments: BookSetMixed.zip
Add BooksDoc to the VDB then go to the Execution tab. This shows in the log:
Unable to resolve reference to a resource with the URI file:/home/dflorian/Runtime-Workspaces/.metadata/.plugins/org.teiid.designer.vdb.edit/vdbWorkingFolder/1243886654886_6290397909764948307/Book%20Set%20Mixed/BookDatatypes.xsd
Notice that Books.xmi is NOT added but BooksSS.xmi is added. If you add Books.xmi by itself it DOES getting added OK.
Added model project set as an attachment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months