August 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1803) Error generating JBossWS-CXF war

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1803?page=com.atlassian.jira.plu... ] Van Halbert edited comment on TEIIDDES-1803 at 8/9/13 9:08 AM: --------------------------------------------------------------- Attached the Sample.vdb. I'm on the 8.2.0.Alpha2-v20130719-0009-B2361 version of designer. Also, after shutting down and restarting JBDS, I retried the generate the war this morning, and the same error occurred. was (Author: van.halbert): Attached the Sample.vdb. I'm on the 8.2.0.Alpha2-v20130719-0009-B2361 version of designer. > Error generating JBossWS-CXF war > -------------------------------- > > Key: TEIIDDES-1803 > URL: https://issues.jboss.org/browse/TEIIDDES-1803 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.2 > > Attachments: Sample.vdb > > > Attached is the Sample.vdb that was used to try to generate the JBossWS-CXF war. The following error occurred: > java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>". > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718) > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476) > 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) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1127) Auto-generate REST Procedures

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1127?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1127: -------------------------------- Fix Version/s: (was: 8.2) > Auto-generate REST Procedures > ----------------------------- > > Key: TEIIDDES-1127 > URL: https://issues.jboss.org/browse/TEIIDDES-1127 > Project: Teiid Designer > Issue Type: Enhancement > Components: Web Services Support > Affects Versions: 7.5 > Reporter: Ted Jones > Assignee: Ted Jones > > Need way to auto-generate procedures exposed over REST. Will need some sort of wizard so the user can name the procedures, REST-METHOD and set the URI. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1803) Error generating JBossWS-CXF war

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1803?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1803: --------------------------------------- Attached the Sample.vdb. I'm on the 8.2.0.Alpha2-v20130719-0009-B2361 version of designer. > Error generating JBossWS-CXF war > -------------------------------- > > Key: TEIIDDES-1803 > URL: https://issues.jboss.org/browse/TEIIDDES-1803 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.2 > > Attachments: Sample.vdb > > > Attached is the Sample.vdb that was used to try to generate the JBossWS-CXF war. The following error occurred: > java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>". > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718) > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476) > 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) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1803) Error generating JBossWS-CXF war

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1803?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1803: ---------------------------------- Attachment: Sample.vdb > Error generating JBossWS-CXF war > -------------------------------- > > Key: TEIIDDES-1803 > URL: https://issues.jboss.org/browse/TEIIDDES-1803 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.2 > > Attachments: Sample.vdb > > > Attached is the Sample.vdb that was used to try to generate the JBossWS-CXF war. The following error occurred: > java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>". > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718) > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476) > 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) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1289) After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1289?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1289. ------------------------------------- Resolution: Done - Moved the point at which the ConnectionProfile is injected into the ModelResource in JdbcImportWizard. retested ok. - Added Modeshape translator to JdbcTranslatorHelper, since it was not being set correctly. Pull request: https://github.com/Teiid-Designer/teiid-designer/pull/222 > After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1289 > URL: https://issues.jboss.org/browse/TEIIDDES-1289 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2 > > > After importing the metadata using the modeshape jdbc driver, I created the ModeShape.vdb and tried to deploy. It wouldn't deploy because the connection information was not in the ModeShape.xmi 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1822 at 8/8/13 4:51 PM: ---------------------------------------------------------------- Our server framework caches the VDB's which are backed by VdbMetadata. Deleting a data source does not yet result in that cache being updated, hence the VDB's do not yet show an "INVALID" state. Refreshing the Server does end up showing invalid (missing data sources) state. However, recreating the Data Source and refreshing the server does NOT end up with an "ACTIVE" VDB, it's still INACTIVE was (Author: blafond): Our server framework caches the VDB's which are backed by VdbMetadata. Deleting a data source does not yet result in that cache being updated, hence the VDB's do not yet show an "INVALID" state. Refreshing the Server does end up showing invalid (missing data sources) state. > Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1822 > URL: https://issues.jboss.org/browse/TEIIDDES-1822 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Fix For: 8.2.GA > > > 1) Set-up simple JDBC source/model/vdb and test/execute VDB > 2) Delete the Data Source in the Server view > 3) Try and execute the VDB again and get exception logged in console > Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1822: ---------------------------------------- Our server framework caches the VDB's which are backed by VdbMetadata. Deleting a data source does not yet result in that cache being updated, hence the VDB's do not yet show an "INVALID" state. Refreshing the Server does end up showing invalid (missing data sources) state. > Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1822 > URL: https://issues.jboss.org/browse/TEIIDDES-1822 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Fix For: 8.2.GA > > > 1) Set-up simple JDBC source/model/vdb and test/execute VDB > 2) Delete the Data Source in the Server view > 3) Try and execute the VDB again and get exception logged in console > Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1821) Modeshape JDBC import option does not work

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1821?page=com.atlassian.jira.plu... ] Dan Florian updated TEIIDDES-1821: ---------------------------------- Attachment: modeshape-client-3.4-SNAPSHOT.jar Attaching ModeShape 3.4 client jar (current as of Aug 6 source code) which contains the ModeShape JDBC driver. > Modeshape JDBC import option does not work > ------------------------------------------ > > Key: TEIIDDES-1821 > URL: https://issues.jboss.org/browse/TEIIDDES-1821 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: 8.2 > > Attachments: modeshape-client-3.4-SNAPSHOT.jar > > > Current Modeshape JDBC importer was based off of 2.2 Modeshape release. > MS is now at 3.3/3.4 and has changed their URL definition in the meantime, so the current import option is broken. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1821) Modeshape JDBC import option does not work

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1821?page=com.atlassian.jira.plu... ] Dan Florian updated TEIIDDES-1821: ---------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/221 > Modeshape JDBC import option does not work > ------------------------------------------ > > Key: TEIIDDES-1821 > URL: https://issues.jboss.org/browse/TEIIDDES-1821 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: 8.2 > > > Current Modeshape JDBC importer was based off of 2.2 Modeshape release. > MS is now at 3.3/3.4 and has changed their URL definition in the meantime, so the current import option is broken. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1822: -------------------------------------- Summary: Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value Key: TEIIDDES-1822 URL: https://issues.jboss.org/browse/TEIIDDES-1822 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 8.2 Reporter: Barry LaFond Fix For: 8.2.GA 1) Set-up simple JDBC source/model/vdb and test/execute VDB 2) Delete the Data Source in the Server view 3) Try and execute the VDB again and get exception logged in console Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2013