[JBoss JIRA] Created: (TEIIDDES-449) Data tools plug-ins have lots of warnings that need to be addressed
by John Verhaeg (JIRA)
Data tools plug-ins have lots of warnings that need to be addressed
-------------------------------------------------------------------
Key: TEIIDDES-449
URL: https://jira.jboss.org/browse/TEIIDDES-449
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: John Verhaeg
I cleaned up some of the warnings, but there are 3 types left that John Doyle needs to address:
1) The most prevalent warnings are about strings that haven't been externalized in the code, the plugin.xml, and the MANIFEST.MF. All of these need to be internationalized or, if not applicable, marked with NLS tags
2) A couple of the attributes specified in the plugin.xml have been deprecated.
3) There are 2 warnings about API baselines not being set on the project. Not sure how or why the API tooling nature got set on these projects, but I removed the nature and builders from the .projects files, along with the .externalBuilder... folders, but still see the warnings for some reason.
--
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
15 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-446) Connection Profile MRU for JDBC Import is not updated when Connection Profile Name is changed in DTP perspective. Results in exception.
by Barry LaFond (JIRA)
Connection Profile MRU for JDBC Import is not updated when Connection Profile Name is changed in DTP perspective. Results in exception.
---------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-446
URL: https://jira.jboss.org/browse/TEIIDDES-446
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.0
Reporter: Barry LaFond
Assignee: John Doyle
Priority: Critical
Fix For: 7.0
Playing with new DTP driven JDBC Importer.
1) Launched JDBC Import wizard and created SQL Server connection profile to books and took default name "New SQL Server"
2) Model New_SQL_Server was created.
3) Opend DTP perspective and performed a "Rename" action to changed "New SQL Server" to "BooksSQL"
4) launched JDBC Import again and the MRU list did not reflect the new name.
5) Selecting "Next" button resulted in exception:
!ENTRY org.teiid.designer.jdbc.ui 4 0 2010-05-24 10:30:42.332
!MESSAGE ConnectionProfile New SQL Server cannot be found
!STACK 1
Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 ConnectionProfile New SQL Server cannot be found null
at com.metamatrix.modeler.internal.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:290)
at com.metamatrix.modeler.internal.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:282)
at com.metamatrix.modeler.internal.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:84)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.teiid.core.designer 4 0 2010-05-24 10:30:42.334
!MESSAGE ConnectionProfile New SQL Server cannot be found
--
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
15 years, 9 months
[JBoss JIRA] Closed: (TEIIDDES-300) Web Service As Relational importer needs to create access patterns and pk-fk pairs to more correctly model how the tables should be queried at run time
by John Doyle (JIRA)
[ https://jira.jboss.org/browse/TEIIDDES-300?page=com.atlassian.jira.plugin... ]
John Doyle closed TEIIDDES-300.
-------------------------------
> Web Service As Relational importer needs to create access patterns and pk-fk pairs to more correctly model how the tables should be queried at run time
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-300
> URL: https://jira.jboss.org/browse/TEIIDDES-300
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.1
> Environment: 5.5SP3 GA Designer on Linux
> Reporter: Greg Haber
> Assignee: John Doyle
> Attachments: FinancialsDemo_20081130_4.zip, no-parameter-stacktrace.txt, StockQuoteService-ghh.wsdl, StockQuoteService.aar, wsTest1.zip
>
>
> When the Web Service as Relational importer creates a source model, it creates a single request table and one or more response tables to model the web service operation. If there are any required parameters in the web service requests (those which do not contain the property "minOccurs=0") the right way to represent this in MetaMatrix would be via an access pattern.
> But the importer does not create such an access pattern on the request tables, which means that if the preview functionality is run against them, it tries to do a query against the table with no parameters specified, resulting in an error from the XML-Relational SOAP connector (stacktrace attached).
> The importer should create such an access pattern to more correctly reflect the actual behavior of the web service (and our connector framework).
> I'm attaching the model project set for my test, the WSDL for the service (as deployed on my machine), and the .aar file for the actual service (to use just deploy the Axis 2 war from http://www.gtlib.gatech.edu/pub/apache/ws/axis2/1_4_1/axis2-1.4.1-war.zip on a server, and then drop the .aar file in the axis2/WEB-INF/services directory that should exist on your server after deployment).
--
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
15 years, 9 months