February 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2041) Null Pointer Exception creating DB2 JDBC Connection

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2041?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2041: ---------------------------------------- The stack trace indicates you are trying to connect from the Eclipse Data Source Explorer and it appears it's an Eclipse Data Tools issue ? The issue will have to be logged at: https://bugs.eclipse.org/bugs/ In the meantime, you might have more luck changing your connection profile type. There are specific JDBC connection profiles for DB2. You could try using that profile instead of "Generic JDBC" profile. For my DB2 connections I use the driver jar: *db2jcc4.jar* > Null Pointer Exception creating DB2 JDBC Connection > --------------------------------------------------- > > Key: TEIIDDES-2041 > URL: https://issues.jboss.org/browse/TEIIDDES-2041 > Project: Teiid Designer > Issue Type: Bug > Environment: Designer 8.3.1.Final-v20140122-1920-B21. Running in eclipse Kepler on Windows 7 with jdk1.7.0_45 > Reporter: Jim Riley > > When trying to Make a JDBC connection to DB2 Database a Null Pointer Exception is encountered. The Ping to test the connection is successful. > I tried connecting to a AIX DB2 instance and a Mainframe instance. The result was the same. > The detailed messages is: > Could not connect to New Generic JDBC. > Error creating SQL Model Connection connection to New Generic JDBC. (Error: null) > java.lang.NullPointerException > OK > The log file contains: > !ENTRY org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 > !MESSAGE Could not connect to DMS Net Driver JDBC. > !SUBENTRY 1 org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 > !MESSAGE Error creating SQL Model Connection connection to DMS Net Driver JDBC. (Error: null) > !STACK 0 > java.lang.NullPointerException > at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.getCatalogDatabase(DatabaseProviderHelper.java:37) > at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.setDatabase(DatabaseProviderHelper.java:47) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:718) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38) > at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59) > at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114) > at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163) > at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > !SUBENTRY 1 unknown 0 0 2014-02-06 10:18:14.869 -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2042) Preview Parser on Flat File Import Wizard shows incorrect data

by Debbie Steigner (JIRA)

Debbie Steigner created TEIIDDES-2042: ----------------------------------------- Summary: Preview Parser on Flat File Import Wizard shows incorrect data Key: TEIIDDES-2042 URL: https://issues.jboss.org/browse/TEIIDDES-2042 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.3, 7.7.4 Reporter: Debbie Steigner Attachments: sample.csv Using the "Parse Selected Row" inside of the File Source(Flat) importer ignores, blanks. I'm attaching a sample.csv. i.e. AgencyId,Area,CaseNumber,CaseStatusCode,CaseTypeCode 714,,,ACTI,M The parser in the importer, will give results: AgencyId=714 Area=ACTI CaseNumber=M it should be AgencyId=714 Area= CaseNumber= CaseStatusCode=ACTI CaseTypeCode=M -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2042) Preview Parser on Flat File Import Wizard shows incorrect data

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2042?page=com.atlassian.jira.plu... ] Debbie Steigner updated TEIIDDES-2042: -------------------------------------- Attachment: sample.csv > Preview Parser on Flat File Import Wizard shows incorrect data > -------------------------------------------------------------- > > Key: TEIIDDES-2042 > URL: https://issues.jboss.org/browse/TEIIDDES-2042 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.4, 8.3 > Reporter: Debbie Steigner > Attachments: sample.csv > > > Using the "Parse Selected Row" inside of the File Source(Flat) importer ignores, blanks. I'm attaching a sample.csv. > i.e. > AgencyId,Area,CaseNumber,CaseStatusCode,CaseTypeCode > 714,,,ACTI,M > The parser in the importer, will give results: > AgencyId=714 > Area=ACTI > CaseNumber=M > it should be > AgencyId=714 > Area= > CaseNumber= > CaseStatusCode=ACTI > CaseTypeCode=M -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2041) Null Pointer Exception creating DB2 JDBC Connection

by Jim Riley (JIRA)

Jim Riley created TEIIDDES-2041: ----------------------------------- Summary: Null Pointer Exception creating DB2 JDBC Connection Key: TEIIDDES-2041 URL: https://issues.jboss.org/browse/TEIIDDES-2041 Project: Teiid Designer Issue Type: Bug Environment: Designer 8.3.1.Final-v20140122-1920-B21. Running in eclipse Kepler on Windows 7 with jdk1.7.0_45 Reporter: Jim Riley When trying to Make a JDBC connection to DB2 Database a Null Pointer Exception is encountered. The Ping to test the connection is successful. I tried connecting to a AIX DB2 instance and a Mainframe instance. The result was the same. The detailed messages is: Could not connect to New Generic JDBC. Error creating SQL Model Connection connection to New Generic JDBC. (Error: null) java.lang.NullPointerException OK The log file contains: !ENTRY org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 !MESSAGE Could not connect to DMS Net Driver JDBC. !SUBENTRY 1 org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 !MESSAGE Error creating SQL Model Connection connection to DMS Net Driver JDBC. (Error: null) !STACK 0 java.lang.NullPointerException at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.getCatalogDatabase(DatabaseProviderHelper.java:37) at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.setDatabase(DatabaseProviderHelper.java:47) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:718) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38) at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45) at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59) at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114) at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163) at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 unknown 0 0 2014-02-06 10:18:14.869 -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2011) Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2011?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2011: --------------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1047930|https://bugzilla.redhat.com/show_bug.cgi?id=1047930] from VERIFIED to CLOSED > Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2011 > URL: https://issues.jboss.org/browse/TEIIDDES-2011 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.1 > > Attachments: modeshape-client-3.3.6.GA-redhat-3.jar, modeshape-roles.properties, modeshape-users.properties, module.xml > > > Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile. > Results in java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory trying to connect to MS repo via JDBC. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1969) Newly Created VDB Editor Does Not Show UDF JAR

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1969?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1969: --------------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1036644|https://bugzilla.redhat.com/show_bug.cgi?id=1036644] from VERIFIED to CLOSED > Newly Created VDB Editor Does Not Show UDF JAR > ---------------------------------------------- > > Key: TEIIDDES-1969 > URL: https://issues.jboss.org/browse/TEIIDDES-1969 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.3 > > > Using Teiid Designer: > Description of problem: > I created a VDB and added models from the workspace. One of these models, was a relational function model that had a UDF JAR associated with it. When the VDB is created and the VDB editor is shown for the first time, selecting the "UDF Jars" tab does not show the UDF JAR that was added to the VDB when the VDB was created. > Version-Release number of selected component (if applicable): > DV 6.0.0 ER4 > JBDS 7.1.0 CR1 > JBIS 4.1.3 Beta5 > Teiid Designer 8.3.0 CR1 > OS X 10.9 > How reproducible: > Always. > Steps to Reproduce (using the E2EYahooUdfTestScript): > 1. New > Teiid VDB > 2. Select models from workspace. One of which is relational function with UDF JAR. > 3. Click on "UDF Jars" tab of the VDB editor. > Actual results: > The "UDF Jars" tab of VDB editor does not show the UDF JAR file associated with the relational function model. > Expected results: > The UDF JAR file should be displayed when the VDB is first created. > Additional info: > If the VDB editor is closed and reopened, the UDF JAR is shown in the editor. So it is obviously being added to the VDB. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1942) Oracle import not setting columns to correct types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1942?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1942: --------------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1035471|https://bugzilla.redhat.com/show_bug.cgi?id=1035471] from VERIFIED to CLOSED > Oracle import not setting columns to correct types > -------------------------------------------------- > > Key: TEIIDDES-1942 > URL: https://issues.jboss.org/browse/TEIIDDES-1942 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Reporter: Mark Drilling > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.3 > > > Import from Oracle is setting some column types to object. Regression was introduced with TEIIDDES-1918 -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1100) Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1100?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1100: --------------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 780971|https://bugzilla.redhat.com/show_bug.cgi?id=780971] from VERIFIED to CLOSED > Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file > ------------------------------------------------------------------------- > > Key: TEIIDDES-1100 > URL: https://issues.jboss.org/browse/TEIIDDES-1100 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Environment: Windows > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: test.csv > > > Trying to use the Import from Flat File option, but it doesn't recognize linefeeds of "\n" or "\r\n". > This also occurs for the DDL importer. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1917) Can't delete source model which imports VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1917?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1917: --------------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1026728|https://bugzilla.redhat.com/show_bug.cgi?id=1026728] from VERIFIED to CLOSED > Can't delete source model which imports VDB > ------------------------------------------- > > Key: TEIIDDES-1917 > URL: https://issues.jboss.org/browse/TEIIDDES-1917 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.3 > > > Source model that imports VDB can't be deleted. > Environment JBDS 7.0.0 GA > Tooling 4.1.3.Beta5 (http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...) > Steps to reproduce: > 1. Select File -> Import -> JDBC Database >> Source Model > 2. Create connection profile for VDB (Select Teiid as Connection profile type) > 3. Make sure that Import as VDB source model is checked > 4. Create the source Model > 5. Right-click on the source model and try to delete it, but Delete is inactive -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1894) Importing DB2 JDBC Data Source throwing java.lang.NullPointerException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1894?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1894: --------------------------------------------------- Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1021699|https://bugzilla.redhat.com/show_bug.cgi?id=1021699] from VERIFIED to CLOSED > Importing DB2 JDBC Data Source throwing java.lang.NullPointerException > ---------------------------------------------------------------------- > > Key: TEIIDDES-1894 > URL: https://issues.jboss.org/browse/TEIIDDES-1894 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.3, 7.7.5 > > Attachments: db2jcc4.jar, db2jcc_license_cu-3.8.47.jar > > > Importing DB2 JDBC Source in Designer is throwing a java.lang.NullPointerException. It happens after tables has been selected while trying to do import. Driver used db2jcc4.jar. I was trying to import jdbc:db2://vmg06.mw.lab.eng.bos.redhat.com:50000/jbossqa user:bqt2 pw:mm Using JBDS 7.0.0.GA and Designer 8.2.0 > java.lang.NullPointerException > at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.initializeInTransaction(JdbcImportOptionsPage.java:486) > at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.setVisible(JdbcImportOptionsPage.java:394) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) -- 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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2014