[JBoss JIRA] (TEIIDDES-1323) NPE in XML Import Wizard When Source Model Does Not Exist
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-1323:
-----------------------------------
Summary: NPE in XML Import Wizard When Source Model Does Not Exist
Key: TEIIDDES-1323
URL: https://issues.jboss.org/browse/TEIIDDES-1323
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.7
Reporter: Ted Jones
Fix For: 7.7.1
In the XML Import wizard, if you enter a new source model name to import into, an NPE is thrown at generation (after clicking finish).
java.lang.NullPointerException
at com.metamatrix.modeler.transformation.ui.wizards.xmlfile.TeiidXmlFileImportProcessor.addProcedureToRelationalSourceModel(TeiidXmlFileImportProcessor.java:131)
at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportProcessor.createProceduresInExistingSourceModelInTxn(TeiidMetadataImportProcessor.java:312)
at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportProcessor.access$1(TeiidMetadataImportProcessor.java:307)
at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportProcessor$1.execute(TeiidMetadataImportProcessor.java:76)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
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 com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportProcessor.execute(TeiidMetadataImportProcessor.java:91)
at com.metamatrix.modeler.transformation.ui.wizards.xmlfile.TeiidXmlImportWizard$1.run(TeiidXmlImportWizard.java:71)
at com.metamatrix.ui.internal.util.UiUtil.runInSwtThread(UiUtil.java:459)
at com.metamatrix.modeler.transformation.ui.wizards.xmlfile.TeiidXmlImportWizard.finish(TeiidXmlImportWizard.java:68)
at com.metamatrix.ui.internal.wizard.AbstractWizard.performFinish(AbstractWizard.java:355)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
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:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (TEIIDDES-1317) wrong type on model in VDB definition
by luca gioppo (JIRA)
luca gioppo created TEIIDDES-1317:
-------------------------------------
Summary: wrong type on model in VDB definition
Key: TEIIDDES-1317
URL: https://issues.jboss.org/browse/TEIIDDES-1317
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.6
Environment: Windows
Reporter: luca gioppo
In a VDB created for transforming relational data to XML from exixting XSD the VDB insert "TYPE" in the model description in the manifest file as shown below:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<vdb version="1" name="libri">
<property value="false" name="preview"/>
<model visible="true" type="PHYSICAL" name="local_book" path="/books/local_book.xmi">
<property value="1841187605" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="440299790.INDEX" name="indexName"/>
<source translator-name="mysql5" connection-jndi-name="java:/local_book" name="local_book"/>
</model>
<model visible="true" type="TYPE" name="Books" path="/books/Books.xsd">
<property value="2392354248" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="4008441630.INDEX" name="indexName"/>
<property value="/books/BookDatatypes.xsd" name="imports"/>
</model>
<model visible="true" type="TYPE" name="BookDatatypes" path="/books/BookDatatypes.xsd">
<property value="3412846293" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="3680615365.INDEX" name="indexName"/>
</model>
<model visible="true" type="VIRTUAL" name="libro" path="/books/libro.xmi">
<property value="1493944231" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="2863148665.INDEX" name="indexName"/>
<property value="/books/Books.xsd" name="imports"/>
<property value="/books/BookDatatypes.xsd" name="imports"/>
<property value="/books/local_book.xmi" name="imports"/>
<validation-error path="bookListingDocument/bookListing/sequence/book/type" severity="WARNING">The XML Schema component type for "type" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/isbn" severity="WARNING">The XML Schema component type for "isbn" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/Mapping Class Set Container/Mapping Classes/book" severity="WARNING">Possible cross-join: Group/s '[local_book.aria.books, local_book.aria.publishers]' are not joined either directly or transitively to other groups through a join criteria. Check all queries in the transformation.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">"edition" has a fixed or default value and should not be mapped. (See validation Preferences)</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/title" severity="WARNING">The XML Schema component type for "title" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">The XML Schema component type for "edition" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/publishDate" severity="WARNING">The XML Schema component type for "publishDate" must be marked as an enterprise datatype to be used in this model.</validation-error>
</model>
</vdb>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (TEIIDDES-1234) Generate WAR action processes with workspace models instead of model entries in the selected VDB
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1234:
--------------------------------------
Summary: Generate WAR action processes with workspace models instead of model entries in the selected VDB
Key: TEIIDDES-1234
URL: https://issues.jboss.org/browse/TEIIDDES-1234
Project: Teiid Designer
Issue Type: Bug
Components: Web Services Support
Affects Versions: 7.7
Reporter: Barry LaFond
Assignee: Ted Jones
Priority: Critical
Fix For: 7.7
GenerateWarAction.selectionChanged() appears to be mixing apples and oranges. (See below)
I think the intent was to get the VdbModelEntry objects and cache up a list of WS Models for later use generating the proper procedure calls/URLs??
The colde below, however, is finding the corresponding ModelResource in the workspace for each entry, which could easily be "out of sync". Users would be unaware that the WAR they are creating might not be what they expect.
wsModelResources = new ArrayList<ModelResource>();
for (VdbModelEntry vdbModelEntry : modelEntrySet) {
final ModelResource modelResource = ModelerCore.getModelWorkspace().findModelResource(vdbModelEntry.getName());
if (ModelIdentifier.isWebServicesViewModel(modelResource)) {
enable = true;
// Add to our ArrayList of ModelResources. These
// will be used to generate the war artifacts.
wsModelResources.add(modelResource);
}
}
So I think we either not allow users to perform this action if the VDB was "out of sync" (probably not the best option)
or
Find another way to pass the model info necessary for the generator to perform whats needed.
Note that in VdbEditor class there is an example of creating a "Temporary" EMF model container in order to interrogate the models. So I believe it should be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (TEIIDDES-1329) CLONE - wrong type on model in VDB definition
by Steven Hawkins (JIRA)
Steven Hawkins created TEIIDDES-1329:
----------------------------------------
Summary: CLONE - wrong type on model in VDB definition
Key: TEIIDDES-1329
URL: https://issues.jboss.org/browse/TEIIDDES-1329
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.6
Environment: Windows
Reporter: luca gioppo
In a VDB created for transforming relational data to XML from exixting XSD the VDB insert "TYPE" in the model description in the manifest file as shown below:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<vdb version="1" name="libri">
<property value="false" name="preview"/>
<model visible="true" type="PHYSICAL" name="local_book" path="/books/local_book.xmi">
<property value="1841187605" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="440299790.INDEX" name="indexName"/>
<source translator-name="mysql5" connection-jndi-name="java:/local_book" name="local_book"/>
</model>
<model visible="true" type="TYPE" name="Books" path="/books/Books.xsd">
<property value="2392354248" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="4008441630.INDEX" name="indexName"/>
<property value="/books/BookDatatypes.xsd" name="imports"/>
</model>
<model visible="true" type="TYPE" name="BookDatatypes" path="/books/BookDatatypes.xsd">
<property value="3412846293" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="3680615365.INDEX" name="indexName"/>
</model>
<model visible="true" type="VIRTUAL" name="libro" path="/books/libro.xmi">
<property value="1493944231" name="checksum"/>
<property value="false" name="builtIn"/>
<property value="2863148665.INDEX" name="indexName"/>
<property value="/books/Books.xsd" name="imports"/>
<property value="/books/BookDatatypes.xsd" name="imports"/>
<property value="/books/local_book.xmi" name="imports"/>
<validation-error path="bookListingDocument/bookListing/sequence/book/type" severity="WARNING">The XML Schema component type for "type" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/isbn" severity="WARNING">The XML Schema component type for "isbn" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/Mapping Class Set Container/Mapping Classes/book" severity="WARNING">Possible cross-join: Group/s '[local_book.aria.books, local_book.aria.publishers]' are not joined either directly or transitively to other groups through a join criteria. Check all queries in the transformation.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">"edition" has a fixed or default value and should not be mapped. (See validation Preferences)</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/title" severity="WARNING">The XML Schema component type for "title" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">The XML Schema component type for "edition" must be marked as an enterprise datatype to be used in this model.</validation-error>
<validation-error path="bookListingDocument/bookListing/sequence/book/sequence/publishDate" severity="WARNING">The XML Schema component type for "publishDate" must be marked as an enterprise datatype to be used in this model.</validation-error>
</model>
</vdb>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (TEIIDDES-392) WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-392?page=com.atlassian.jira.plug... ]
Ted Jones commented on TEIIDDES-392:
------------------------------------
The new SOAP CP needs credentials added to it. The REST CP can be used as a reference, since it already provides credentials (security type, username, password). We can remove the WS-Security option for now. Also, I don't believe we really need it in the REST CP either.
Then the WSDL to web service importer needs to use the credentials to retrieve the WSDL. An example of how to do this can be found in the Teiid source code (org.teiid.resource.adapter.ws.WSConnectionImpl.invoke()).
> WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs.
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-392
> URL: https://issues.jboss.org/browse/TEIIDDES-392
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 6.0.0, 7.3
> Reporter: John Doyle
> Assignee: Paul Richardson
> Fix For: 7.7.1
>
>
> The SOAP-Relational importer can import WSDLs from URLs or the file system. WSDLs offered by SAP Netweaver via URSs do not validate because SAP requires HTTP basic auth to get the WSDL. The importer should support this and the new Web Service connection profile should provide the credentials.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (TEIIDDES-1324) In-line rename of table/column in Diagram will remove characters after colon
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1324:
--------------------------------------
Summary: In-line rename of table/column in Diagram will remove characters after colon
Key: TEIIDDES-1324
URL: https://issues.jboss.org/browse/TEIIDDES-1324
Project: Teiid Designer
Issue Type: Bug
Components: Diagrams
Affects Versions: 7.7
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.7.1
Working with XML > relational importer, there could be relational objects with names containing a colon ':' character.
Renaming an object in the diagram results in the characters after and including the colon to be dropped. This is a fault of the rename action that is looking for possible datatypes defined during the rename action (i.e. user could type "firstName : string(255)") and designer will set the datatype to "string" and the "length" to 255.
Probably need to look for the "Last" colon, determine if the "last" segement IS a valid datatype. If it is, parse the last segment as D-type. if NOT, then set the whole input string as the object's name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (TEIIDDES-1312) Change Configuration Files So That Local Builds WIll Work
by Dan Florian (JIRA)
Dan Florian created TEIIDDES-1312:
-------------------------------------
Summary: Change Configuration Files So That Local Builds WIll Work
Key: TEIIDDES-1312
URL: https://issues.jboss.org/browse/TEIIDDES-1312
Project: Teiid Designer
Issue Type: Task
Components: Build
Affects Versions: 7.7
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 7.7.1
In order to get a local build working a change to our root pom (trunk/pom.xml) is required. Also, our update site configuration files should be change to remove some deprecated tag values and file names. Specifically, the site.xml file should be renamed to category.xml; and the pom.xml packaging type of "eclipse-update-site" should be changed to "eclipse-repository" in order to work better with source features. All this per Mickael Istria. Once these changes are made, the following command will do a local build (leaving off -D option if you want to run tests):
mvn install -P jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,unified.target -Dswtbot.test.skip=true
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months