[JBoss JIRA] Created: (TEIIDDES-406) Design Time Role Management
by Barry LaFond (JIRA)
Design Time Role Management
---------------------------
Key: TEIIDDES-406
URL: https://jira.jboss.org/jira/browse/TEIIDDES-406
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling, Teiid Integration, VDB & Execution
Affects Versions: 7.0
Reporter: Barry LaFond
Priority: Critical
Fix For: 7.0
Role management in "Metamatrix" days was done via it's console. Today, JOPR/JON provides the console-type functionality.
However, the data-role management is being pushed down to design-time.
So Designer needs to take this on, allow data roles (authorization/entitlements) at the column, table and model levels.
In addition there needs to be a way to manage higher-level "security" roles that will be mapped to actual roles when VDB's are deployed to the server.
This will required injecting these roles into the VDB for transport and eventual mapping.
--
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, 8 months
[JBoss JIRA] Created: (TEIIDDES-227) Errors when importing procedures from relational (Oracle) source
by Paul Nittel (JIRA)
Errors when importing procedures from relational (Oracle) source
----------------------------------------------------------------
Key: TEIIDDES-227
URL: https://jira.jboss.org/jira/browse/TEIIDDES-227
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.2.0
Environment: fedora 10, Designer 6.2 RC1
Reporter: Paul Nittel
I tried to import the procedures from the Oracle 10g BQT source and ran into a set of problems.
1 - At the end of the import, a dialog is shown that proclaims the import failed (Unabled to import model into workspace. See log for details). Yes, it does say, "Unabled." In the log file there was this NPE:
!ENTRY org.teiid.designer.jdbc.relational 4 3003 2009-09-22 07:52:50.914
!MESSAGE Import resulted in 1 errors
!SUBENTRY 1 org.teiid.designer.jdbc.relational 4 0 2009-09-22 07:52:50.914
!MESSAGE Unexpected exception while creating relational model from BQT O11
!STACK 0
java.lang.NullPointerException
at com.metamatrix.modeler.jdbc.relational.impl.custom.OracleModelProcessor.computeNameInSource(OracleModelProcessor.java:274)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2441)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createParameters(RelationalModelProcessorImpl.java:2192)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1129)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:816)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:336)
at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:541)
at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:584)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:343)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:319)
at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:309)
at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:677)
at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard$1.run(JdbcImportWizard.java:262)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.teiid.designer.compare 0 60002 2009-09-22 07:52:50.914
!MESSAGE Merging completed
2 - I tried a different approach where I imported tables and then imported (update) to get the procedures. I deselected all procedures and added these: SP_ALL_SMALLA_ROWS, SP_COUNTSMALLA, SP_COUNT_ALL_SMALLA_ROWS, SP_COUNT_ROWS_BETWEEN, and SP_ROWS_BETWEEN. The result was no tables and only the name of the SP_ALL_SMALLA_ROWS procedure (no actual procedure). The Review Updates panel of the wizard shows only one new entry: SP_ALL_SMALLA_ROWS. Clicking Finish produces the error.
--
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, 8 months
[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