March 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-466) WSDL Generation from Web Service Models Creates Extraneous Nodes

by Ted Jones (JIRA)

WSDL Generation from Web Service Models Creates Extraneous Nodes ---------------------------------------------------------------- Key: TEIIDDES-466 URL: https://jira.jboss.org/browse/TEIIDDES-466 Project: Teiid Designer Issue Type: Task Components: Modeling Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Generated web service models from a Books VDB which creates operations for getBooks, getAuthors, getBooks_Authors, and getPublishers. A separate port type, binding and port is generated for each operation. Only one port type, binding and port is needed. We should get rid of the extraneous nodes and combine into one port type, binding and port. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-909) Add Categories to Modeling->Actions

by Ted Jones (JIRA)

Add Categories to Modeling->Actions ----------------------------------- Key: TEIIDDES-909 URL: https://issues.jboss.org/browse/TEIIDDES-909 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.3 Reporter: Ted Jones With the increasing number of actions being added to the Modeling menu option, functional categories would be very helpful in presenting the actions in an orderly fashion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-907) In Designer, the default data type length could cause issues when accessing EDS via ODBC

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-907?page=com.atlassian.jira.plug... ] Van Halbert moved SOA-2980 to TEIIDDES-907: ------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-907 (was: SOA-2980) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: Modeling (was: EDS) Security: (was: Public) > In Designer, the default data type length could cause issues when accessing EDS via ODBC > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-907 > URL: https://issues.jboss.org/browse/TEIIDDES-907 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > Customers that are building VDB's to be accessed via ODBC will be wrong when the MAX_INT default is used. The following exception will be seen in the server log when this occurs: > 1 [FunctionExecutionException] ERR.015.001.0033: Error Code:ERR.015.001.0033 Message:Error converting [2,097,152] of type integer to type short > 2 [TransformationException]The Integer value '2,097,152' is outside the of range for Short > at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:259) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:969) > at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:633) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:603) > ... 39 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-907) In Designer, the default data type length could cause issues when accessing EDS via ODBC

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-907?page=com.atlassian.jira.plug... ] Van Halbert reassigned TEIIDDES-907: ------------------------------------ Assignee: Barry LaFond (was: Van Halbert) > In Designer, the default data type length could cause issues when accessing EDS via ODBC > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-907 > URL: https://issues.jboss.org/browse/TEIIDDES-907 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > > Customers that are building VDB's to be accessed via ODBC will be wrong when the MAX_INT default is used. The following exception will be seen in the server log when this occurs: > 1 [FunctionExecutionException] ERR.015.001.0033: Error Code:ERR.015.001.0033 Message:Error converting [2,097,152] of type integer to type short > 2 [TransformationException]The Integer value '2,097,152' is outside the of range for Short > at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:259) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:969) > at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:633) > at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:603) > ... 39 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-906) Several Missing Message Keys for SetConnectionProfile

by Ted Jones (JIRA)

Several Missing Message Keys for SetConnectionProfile ----------------------------------------------------- Key: TEIIDDES-906 URL: https://issues.jboss.org/browse/TEIIDDES-906 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4 Reporter: Ted Jones Using the Set Connection Profile dialog I encountered several "Missing Message Keys": SetConnectionProfileAction.invalidSelectionMessage SetConnectionProfileAction.okSelectionMessage SetConnectionProfileAction.categorySelectionMessage -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-750) The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-750?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-750: ---------------------------------- Fix Version/s: Future (was: 7.4) > The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-750 > URL: https://issues.jboss.org/browse/TEIIDDES-750 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: Future > > > If you open the context menu for a VDB, the top-level menu contains Run As..., Debug As..., and Modeling submenus. I have no idea how Debug As... would even apply, but Run As... certainly seems like the intuitive option to choose if you want to execute a VDB, especially considering the submenu contains the single entry Run on Server. But that, of course, isn't correct and produces nothing more than an error message about no resources being available to execute; the user is supposed to instead choose Modeling > Execute VDB to run the VDB on the server. It seems like we should remove the Execute option under the Modeling submenu and instead intercept the Run As... > Run on Server option to do the right thing, or alternatively, remove/disable the Run As.../Debug As... menu option when a VDB is selected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-750) The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-750?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-750: ------------------------------------- Assignee: (was: Dan Florian) > The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-750 > URL: https://issues.jboss.org/browse/TEIIDDES-750 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Fix For: Future > > > If you open the context menu for a VDB, the top-level menu contains Run As..., Debug As..., and Modeling submenus. I have no idea how Debug As... would even apply, but Run As... certainly seems like the intuitive option to choose if you want to execute a VDB, especially considering the submenu contains the single entry Run on Server. But that, of course, isn't correct and produces nothing more than an error message about no resources being available to execute; the user is supposed to instead choose Modeling > Execute VDB to run the VDB on the server. It seems like we should remove the Execute option under the Modeling submenu and instead intercept the Run As... > Run on Server option to do the right thing, or alternatively, remove/disable the Run As.../Debug As... menu option when a VDB is selected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-876) Exported Model Projects containing Source models may contain user-specific Connection Profile info. Need mechanism to remove/clear these properties at export or import time.

by Barry LaFond (JIRA)

Exported Model Projects containing Source models may contain user-specific Connection Profile info. Need mechanism to remove/clear these properties at export or import time. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-876 URL: https://issues.jboss.org/browse/TEIIDDES-876 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview, Import/Export, VDB & Execution Affects Versions: 7.3 Reporter: Barry LaFond Priority: Critical Fix For: 7.4 The FinancialDemos.zip project (attached) contains source models with oodles of connection profile info (required for Preview Data) that was probably set during initial model import. If other users import this example, this connection profile may or may not be valid. We need to be able to clear these properties for the user. Options: 1) Simple "Remove Connection Profile" modeling action 2) Add a "Clear" option in the "Set Connection Profile" action 3) Add a "Clean up Preview 'stuff'" action on a model project? 4) Add "Clean up Preview 'stuff'" on Export Model Project Set (tough to do) 5) Add option during Import Model Project Set to "Clean up preview stuff" (clear connection info from source models) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-904) Add JDBC import support for Intersystems Cache

by Ramesh Reddy (JIRA)

Add JDBC import support for Intersystems Cache ---------------------------------------------- Key: TEIIDDES-904 URL: https://issues.jboss.org/browse/TEIIDDES-904 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: Ramesh Reddy Please add JDBC import for Intersystems Cache database http://www.intersystems.com/cache/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-329) Operations Editor does not correctly wrap user-entered SQL with CREATE... and END

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-329?page=com.atlassian.jira.plug... ] Ted Jones resolved TEIIDDES-329. -------------------------------- Resolution: Cannot Reproduce Bug > Operations Editor does not correctly wrap user-entered SQL with CREATE... and END > --------------------------------------------------------------------------------- > > Key: TEIIDDES-329 > URL: https://issues.jboss.org/browse/TEIIDDES-329 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1.1 > Environment: fedora 10, Designer build 3257 > Reporter: Paul Nittel > Assignee: Ted Jones > Fix For: 7.4 > > > I ran across this while running the E2E Updateable Web Service Test Script. > After creating the Web Service interface and initial steps of creating the InsertProduct operation, I pasted in the SQL. When I validated the SQL, the Designer wrapped it, beginning with the CREATE, and ending with END. Unfortunately, the terminating END is placed immedately after the END in the pasted in text. The validation then fails when it reaches the new word, "ENDEND". (the user needs to separate the "ENDEND" into "END END" and it will parse correctly. > The error message is: > The query is not parsable. > Parsing error: Encountered "<EOF>" at line 1, column 464. > Was expecting: > "=" ... > The SQL winds up being: > CREATE VIRTUAL PROCEDURE BEGIN DECLARE string VARIABLES.IN_ID = xpathvalue(ProductsWebSvc.ProdInterface.DeleteProduct.ProductIdIn, '/*:InstrIdInput/*:ID'); DECLARE integer VARIABLES.delete_count = 0; VARIABLES.DELETE_COUNT = DELETE FROM Updates.UpdateProduct WHERE Updates.UpdateProduct.INSTR_ID = VARIABLES.IN_ID; IF(VARIABLES.DELETE_COUNT = 1) BEGIN SELECT * FROM ProductDoc.goodResultsDocument; END ELSE BEGIN SELECT * FROM ProductDoc.badResultsDocument; ENDEND -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2011