[JBoss JIRA] Updated: (TEIIDDES-340) Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-340?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-340:
----------------------------------
Fix Version/s: 7.4.2
Assignee: Mark Drilling (was: Barry LaFond)
> Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-340
> URL: https://issues.jboss.org/browse/TEIIDDES-340
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Environment: Fedora 8
> Reporter: Dan Florian
> Assignee: Mark Drilling
> Fix For: 7.5, 7.4.2
>
>
> If you change step 3.3.2.1 of the E2E XML Book Set Mixed Test Script to select the project in the tree not the model, the model deltas are not calculated. Proceed as the test script says until the last page. Change the model name to match the update model and check "update." Now hit "Next >" to go to the last page and notice there are no differences when there should be since the foreign keys are being added. If you click "Finish" nothing is updated. This is because if go back in the wizard after changing the model name, the "Foreign Keys" and "Indexes" checkboxes are now unselected. I did not have this problem when running the same kit under MS Windows.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-1023) CLONE - java.lang.ClassNotFoundException: nu.xom.ParsingException via Import > Teiid Designer > WSDL into Relational Source Model
by Steven Hawkins (JIRA)
CLONE - java.lang.ClassNotFoundException: nu.xom.ParsingException via Import > Teiid Designer > WSDL into Relational Source Model
---------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1023
URL: https://issues.jboss.org/browse/TEIIDDES-1023
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Ted Jones
Fix For: 7.5
1) Import > Teiid Designer > WSDL into Relational Source Model
2) Create New WS Connection Profile by selecting the attached OnHand.wsdl file on your local file system.
3) Finish wizard and get following exception
java.lang.NoClassDefFoundError: nu/xom/ParsingException
at org.teiid.query.sql.lang.XMLTable.compileXqueryExpression(XMLTable.java:120)
at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:357)
at org.teiid.query.sql.lang.XMLTable.acceptVisitor(XMLTable.java:168)
at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:61)
at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:72)
at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:273)
at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:580)
at org.teiid.query.sql.lang.From.acceptVisitor(From.java:146)
at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:61)
at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:235)
at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:106)
at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:294)
at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:147)
at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveEmbeddedCommand(UpdateProcedureResolver.java:338)
at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveStatement(UpdateProcedureResolver.java:189)
at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveBlock(UpdateProcedureResolver.java:164)
at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveCommand(UpdateProcedureResolver.java:147)
at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:294)
at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:168)
at com.metamatrix.modeler.transformation.validation.TransformationValidator.resolveCommand(TransformationValidator.java:431)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-776) Data Roles: After unchecking a model, cannot check subordinate metadata, like columns
by Paul Nittel (JIRA)
Data Roles: After unchecking a model, cannot check subordinate metadata, like columns
-------------------------------------------------------------------------------------
Key: TEIIDDES-776
URL: https://issues.jboss.org/browse/TEIIDDES-776
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1.1
Reporter: Paul Nittel
In the case where an administrator wishes to prevent access to all columns but a relatively few, they should be able to:
Uncheck the model (which causes all subordinate objects to be unchecked)
Check the small number to which access is desired.
What happens is once the model is unchecked, the subordinate objects cannot be checked. (Also, if all subordinate objects are manually unchecked, the model has a grayed-out check as if there is a checked subordinate object. If all objects under a model are unchecked, the model itself should also be unchecked.)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-1005) Getting exception when attempting to do a metadata search in Designer
by Mark Drilling (JIRA)
Getting exception when attempting to do a metadata search in Designer
---------------------------------------------------------------------
Key: TEIIDDES-1005
URL: https://issues.jboss.org/browse/TEIIDDES-1005
Project: Teiid Designer
Issue Type: Bug
Components: Validation
Affects Versions: 7.1.1
Environment: Fedora 14, x64
JDBS 4.0.1
Reporter: Mark Drilling
Assignee: Mark Drilling
I'm getting exceptions when attempting a metadata search - after I've imported and rebuilt a model project in Designer. To reproduce:
1) Import the attached SearchProject.zip into Designer (Import... > General > Existing Projects into Workspace
2) After import the project has (for me) 27 errors. To correct the errors, 1) close project, 2) open project, 3) rebuild project. Then the project is error free.
3) Attempt a metadata search. (Search > Teiid Designer > Metadata...) The search attempt results in the attached stack trace.
4) Either a) Close JBDS and Restart or b) delete the offending VDB from #3 will clear things up and eliminate the exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months