[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1966:
----------------------------------------
Mark tested on his Fedora and I tested on Ubuntu with no issues. Van tested on his MAC and reproduced it.
Can you attach a Model Project set containing your models and the offending VDB?
> Failed in Making a Multi-source Binding
> ---------------------------------------
>
> Key: TEIIDDES-1966
> URL: https://issues.jboss.org/browse/TEIIDDES-1966
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Environment: Mac OS X 10.9, Eclipse
> Reporter: yapeng shen
> Assignee: Barry LaFond
> Labels: regression
> Fix For: 8.3
>
>
> I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9.
>
> In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support.
>
> As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1966:
----------------------------------------
That is not true, I have reproduced it in Fedora 18, with JDK 1.6. But it should be tested on Windows to be sure.
> Failed in Making a Multi-source Binding
> ---------------------------------------
>
> Key: TEIIDDES-1966
> URL: https://issues.jboss.org/browse/TEIIDDES-1966
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Environment: Mac OS X 10.9, Eclipse
> Reporter: yapeng shen
> Assignee: Barry LaFond
> Labels: regression
> Fix For: 8.3
>
>
> I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9.
>
> In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support.
>
> As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1952) Create an ODA Flat File connection profile "next" button does become active
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1952?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1952.
------------------------------------
Resolution: Cannot Reproduce Bug
Cannot reproduce.
> Create an ODA Flat File connection profile "next" button does become active
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-1952
> URL: https://issues.jboss.org/browse/TEIIDDES-1952
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: Fedoa 18, JDK 1.6
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Create an ODA Flat File connection profile - the Finish or Next button are
> inactive after the selection of the folder where the file is located, when the "Validate Home Folder" is checked (default checked). Test Connection has no effect, when you uncheck "validate home folder" then the buttons light up
> Looks like the the validation is not being done auto-matically nor when the Test Connection is clicked.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1966:
----------------------------------------
This appears to be another MAC issue. Cannot reproduce on Fedora or Ubuntu Linux.
> Failed in Making a Multi-source Binding
> ---------------------------------------
>
> Key: TEIIDDES-1966
> URL: https://issues.jboss.org/browse/TEIIDDES-1966
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Environment: Mac OS X 10.9, Eclipse
> Reporter: yapeng shen
> Assignee: Barry LaFond
> Labels: regression
> Fix For: 8.3
>
>
> I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9.
>
> In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support.
>
> As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1963) Designer Create User Defined Function Dialog contains Result Set Tab
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1963?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1963:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035356|https://bugzilla.redhat.com/show_bug.cgi?id=1035356] from ASSIGNED to MODIFIED
> Designer Create User Defined Function Dialog contains Result Set Tab
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1963
> URL: https://issues.jboss.org/browse/TEIIDDES-1963
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Original Description below, however, investigation determined that UDF's should now allow creating Result Set children, so the Result Set tab needs to be removed.
> Description of problem:
> Following the E2E Yahoo UDF Test Script, I tried to create the UDF. When I got to the part to create the return parameter for the function the "Add" column button could not be enabled.
> 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:
> Happens every time.
> Steps to Reproduce:
> Using Designer:
> 1. Create a new relational model
> 2. New Child > Procedure > User Defined Function > OK
> 3. Enter a function "Name" and a "Java Class" (to get rid of error message)
> 4. Click the "Result Set" tab
> 5. There is no way to add a result set column
> Actual results:
> Unable to create a return parameter for relational UDF model. But the model can be created and the return parameter can be added later using the New Child menu option.
> Expected results:
> The "Add" button in the wizard should enable so that a return parameter can be entered.
> Additional info:
> None
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1939) Preview VDB operation should validate first if there is existing Data Source
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1939?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1939:
-----------------------------------------
I tried several scenarios to try to get this to fail, but could not reproduce. Recommend we close as 'Not reproducible' unless you can come up with steps to reproduce.
> Preview VDB operation should validate first if there is existing Data Source
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-1939
> URL: https://issues.jboss.org/browse/TEIIDDES-1939
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> I am trying to create a file based source model using the "Flat File Importer". In the step one, I created a file connection factory and tried to create a source and view model based on TEXTTABLE creation wizard. This failed (this will be another defect once I figure out why). I tried to redo the wizard steps all over once I deleted empty source model it created in the last step. Every thing went OK, but after generating the source and view models I see a dialog pop-up with following exception
> {code}
> An error synchronizing and saving the Preview VDB for model "/RecursiveXMLTest/EmployeeData.xmi" occurred.
> TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.file.PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_EmployeeData is already registered
> {code}
> and Exception from Server log
> {code}
> 10:55:05,063 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 23) JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "file"),
> ("connection-definitions" => "PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_EmployeeData")
> ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.resourceadapters.ra.file.PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_EmployeeData is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:561) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:989) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.connector.subsystems.resourceadapters.ConnectionDefinitionAdd.performRuntime(ConnectionDefinitionAdd.java:84)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_35]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_35]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_35]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
> {code}
> Looks like we are trying to create the data source again, or did not cleanup the data source from before.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1965) builtinDatatypes.xsd file is not found when running on a windows machine
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1965?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1965:
--------------------------------
Fix Version/s: 8.3
> builtinDatatypes.xsd file is not found when running on a windows machine
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-1965
> URL: https://issues.jboss.org/browse/TEIIDDES-1965
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.3
> Environment: Windows
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 8.3
>
>
> Bug: in windows: SimpleDatatypes in a model used for Web Service generation causing xsds to include an irresolvable import. It causes the xsd window to freeze until the import timeout and the CXF WAR to completely fail. Apparently the builtinDatatypes.xsd that resides in one of the Teiid designer's jars can't be found under windows which causes all the urLocation fields of the import to be used. Since the url is pointing to the old metamatrix.com site the problem arises.
--
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, 7 months