[JBoss JIRA] (TEIIDDES-1823) Update Modeshape Jars to MS 3.4 Release
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1823:
--------------------------------------
Summary: Update Modeshape Jars to MS 3.4 Release
Key: TEIIDDES-1823
URL: https://issues.jboss.org/browse/TEIIDDES-1823
Project: Teiid Designer
Issue Type: Task
Components: Release Work
Affects Versions: 8.2.GA
Reporter: Barry LaFond
Assignee: Dan Florian
Fix For: 8.2.GA
Modeshape 3.3.x or 3.4 Final jars should be included with the product release.
Update the pom.xml to pull from 3.4 Final bits
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1544) Error While Generating WAR in Teiid 8.0
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1544?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1544:
-----------------------------------
Fix Version/s: 8.2.GA
(was: 8.2)
> Error While Generating WAR in Teiid 8.0
> ---------------------------------------
>
> Key: TEIIDDES-1544
> URL: https://issues.jboss.org/browse/TEIIDDES-1544
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.0
> Reporter: Ajit Kumar Nayak
> Assignee: Ted Jones
> Fix For: 8.2.GA
>
>
> Hi,
> I am using
> JBOSS AS 7.1.1
> teiid-8.0.0.Final-jboss-dist
> teiid-designer-8.0.0.Beta1-v20121114-1958-H144.zip
> jbossws-cxf-4.1.0.Final
> I am getting error while creating CXF-WAR for my VDB
> As
> java.lang.RuntimeException: File SimpleDatatypes-instance does not exist.
> 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:472)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1811:
-----------------------------------
Fix Version/s: 8.3
(was: 8.2)
Priority: Minor (was: Critical)
Can't reproduce.
Adding additional artifacts for a failing case might help to reproduce. Pushing to 8.3
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Minor
> Fix For: 8.3
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1811:
----------------------------------------
Again tried to reproduce.
1) Imported BQT2 model from SQL Server, created View Model containing Procedures
2) Created and deployed BQT VDB containing source and view model
3) Imported this VDB and was able to see/create VDB Source model via JDBC import wizard.
All parameters for all procedures were visible.
Still not able to reproduce
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Critical
> Fix For: 8.2
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1767?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-1767:
------------------------------------
Fix Version/s: 8.2.GA
(was: 8.2)
> Cannot redeploy a vdb with webservice datasource
> ------------------------------------------------
>
> Key: TEIIDDES-1767
> URL: https://issues.jboss.org/browse/TEIIDDES-1767
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Paul Richardson
> Assignee: Mark Drilling
> Fix For: 8.2.GA
>
>
> When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed.
> 1. Delete all vdb's data sources, including the WSDL webservice data source;
> 2. Deploy the vdb
> 3. Observe the following error
> {code}
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314
> !MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> !STACK 0
> org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239)
> at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
> Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed.
> Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question...
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1803) Error generating JBossWS-CXF war
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1803?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1803:
--------------------------------
Assignee: Ted Jones (was: Van Halbert)
> 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: Ted Jones
> 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
12 years, 8 months