June 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1547) Cannot call web service which is created from model without primary key

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1547?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1547: -------------------------------- Fix Version/s: (was: 8.2) > Cannot call web service which is created from model without primary key > ----------------------------------------------------------------------- > > Key: TEIIDDES-1547 > URL: https://issues.jboss.org/browse/TEIIDDES-1547 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.7.1 > Environment: JBDS 5.0.1 > Reporter: Eiichi Nagai > Assignee: Ted Jones > Fix For: 7.7 > > Attachments: TEIIDDES-1547_reproducer.zip > > > The web service which is created from model without primary key (or Access Pattern) cannot be called by the following exceptions. > {noformat} > org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown. > at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111) > at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99) > at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431) > at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) > at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74) > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) > at java.lang.Thread.run(Thread.java:662) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1705) Model imported from DDL is missing relational model extension MED

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1705?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1705: ----------------------------------------- Assignee: Mark Drilling (was: Paul Richardson) This is probably more relevant to you at the moment. > Model imported from DDL is missing relational model extension MED > ----------------------------------------------------------------- > > Key: TEIIDDES-1705 > URL: https://issues.jboss.org/browse/TEIIDDES-1705 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.2 > > > While working on TEIIDDES-1660 noticed that if I re-imported to same model an NPE showed up because the relational MED was not saved in the model. > RelationalPlugin is responding to a New Model event and applying the MED, but later in the importer, the model contents is copied and it loses the MED. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1498) TEIID31100 Parsing error: : Encountered "(" at line 1, column 6.

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1498?page=com.atlassian.jira.plu... ] Johnathon Lee closed TEIIDDES-1498. ----------------------------------- Fix Version/s: (was: 7.7.3) Resolution: Done Committed r2727 to https://svn.jboss.org/repos/tdesigner/branches/7.7.x Removing 7.7.3 in Fix Version as that would be the current version. Once 7.7.4 is added as a selectable option, it can be used to indicate what version had the fix. > TEIID31100 Parsing error: : Encountered "(" at line 1, column 6. > ---------------------------------------------------------------- > > Key: TEIIDDES-1498 > URL: https://issues.jboss.org/browse/TEIIDDES-1498 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.7 > Environment: Windows + JBoss 7.1.1. + TEIID 8.1 + Designer 7.8 (not available in combo) > Reporter: luca gioppo > Assignee: Ted Jones > Fix For: 8.1 > > > As for forum reference: > https://community.jboss.org/thread/205730?start=0&tstart=0 > I seems that Designer is not able to create web service operations without parameters and in the end the war is "not building the query correctly when there are no parameters". > Francly I did not understand who does the error (the web service wizard from the physical model or the cxf wizard from the VBD). > The result is that if there are no parameters in the soap call there is an error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1498) TEIID31100 Parsing error: : Encountered "(" at line 1, column 6.

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1498?page=com.atlassian.jira.plu... ] Johnathon Lee reopened TEIIDDES-1498: ------------------------------------- > TEIID31100 Parsing error: : Encountered "(" at line 1, column 6. > ---------------------------------------------------------------- > > Key: TEIIDDES-1498 > URL: https://issues.jboss.org/browse/TEIIDDES-1498 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.7 > Environment: Windows + JBoss 7.1.1. + TEIID 8.1 + Designer 7.8 (not available in combo) > Reporter: luca gioppo > Assignee: Ted Jones > Fix For: 7.7.3, 8.1 > > > As for forum reference: > https://community.jboss.org/thread/205730?start=0&tstart=0 > I seems that Designer is not able to create web service operations without parameters and in the end the war is "not building the query correctly when there are no parameters". > Francly I did not understand who does the error (the web service wizard from the physical model or the cxf wizard from the VBD). > The result is that if there are no parameters in the soap call there is an error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1763) Remove remaining jar libraries from codebase

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1763: ----------------------------------------- Summary: Remove remaining jar libraries from codebase Key: TEIIDDES-1763 URL: https://issues.jboss.org/browse/TEIIDDES-1763 Project: Teiid Designer Issue Type: Feature Request Components: Build Reporter: Paul Richardson Assignee: Paul Richardson Fix For: 8.2 There still remains external libraries included in various plugins of the designer codebase, eg. jackson and modeshape. These libraries should either be: * depended on in the target platform; * downloaded and added to a lib directory using maven in the same manner as the teiid dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-417) Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-417?page=com.atlassian.jira.plug... ] Mark Drilling resolved TEIIDDES-417. ------------------------------------ Assignee: Mark Drilling Fix Version/s: 8.2 (was: Future) Resolution: Done resolved along with the related issue TEIIDDES-1762 > Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-417 > URL: https://issues.jboss.org/browse/TEIIDDES-417 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.3, 8.0 > Environment: Iced Tea, Teiid Designer 6.3 > Reporter: Paul Nittel > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: IMFTF.jpg > > > I was writing a SWTBot test to create a view model's tables when I ran into this. > Knowing SWTBot can't handle the File Chooser, I was delighted to see I could enter the text file's path and name directly into the importer dialog. It wasn't until some time later that I realized merely typing in the name does nothing; you MUST enter the name using the File Chooser. (Once that's been done, it appears you can use the drop-down to re-select that file, but you need that first time entry.) > What's really bad/confusing is manually entering the file and target location enables the Finish button. Clicking it appears to work, but no tables were added to the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1762) Text File importer dialog has missing i18n properties

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1762?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1762. ------------------------------------- Resolution: Done Added missing i18n properties and set background of uneditable textField. > Text File importer dialog has missing i18n properties > ----------------------------------------------------- > > Key: TEIIDDES-1762 > URL: https://issues.jboss.org/browse/TEIIDDES-1762 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > In the Designer Text Importer, there is an Overwrite notification dialog when merging into an existing model. The dialog i18n properties are missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1762) Text File importer dialog has missing i18n properties

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1762: --------------------------------------- Summary: Text File importer dialog has missing i18n properties Key: TEIIDDES-1762 URL: https://issues.jboss.org/browse/TEIIDDES-1762 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.1 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.2 In the Designer Text Importer, there is an Overwrite notification dialog when merging into an existing model. The dialog i18n properties are missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1757) Model Extensions Not Loading

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1757?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1757: ----------------------------------------- Appears that the issue is due to createExecutableExtension being used in the ExtensionPlugin.start method... Moved the ModelExtensionRegistry initialization out of the ExtensionPlugin start method - now it is initialized on first request after all the plugins are started. https://github.com/Teiid-Designer/teiid-designer/pull/185 > Model Extensions Not Loading > ----------------------------- > > Key: TEIIDDES-1757 > URL: https://issues.jboss.org/browse/TEIIDDES-1757 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.2 > Environment: OSx, Fedora, Windows > Reporter: Ted Jones > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.2 > > > The model extension has errors parsing at startup and doesn't get loaded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1757) Model Extensions Not Loading

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1757?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1757. ------------------------------------- Resolution: Done > Model Extensions Not Loading > ----------------------------- > > Key: TEIIDDES-1757 > URL: https://issues.jboss.org/browse/TEIIDDES-1757 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.2 > Environment: OSx, Fedora, Windows > Reporter: Ted Jones > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.2 > > > The model extension has errors parsing at startup and doesn't get loaded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2013