[JBoss JIRA] Created: (TEIID-358) Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing
by Paul Nittel (JIRA)
Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing
--------------------------------------------------------------------------------
Key: TEIID-358
URL: https://jira.jboss.org/jira/browse/TEIID-358
Project: Teiid
Issue Type: Bug
Components: Documentation
Affects Versions: 6.0.0
Environment: fedora 10
Reporter: Paul Nittel
Assignee: Steven Hawkins
I ran into this while assisting user Bribek.
When the Derby source is created and imported, a connector binding is built in the Designer. The one thing Designer does not do is place the jar file where it needs to be for previewing. The Quick Start Example needs to add the step of adding the derbyclient.jar file using the UDFs view and "Import UDF Extension Jar Files" action.
IMHO, the Quick Start needs to be revisited to determine exactly what the required minimum effort is for a user to get through this. Perhaps on the Teiid side avoid all modeling and add a Quick Start on the Designer side that builds the VDB. If Teiid can do the Quick Start with just a VDB, that might be preferable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (TEIID-429) Use DataSources in creating the ConnectorBindings instead of creating one using the Driver
by Ramesh Reddy (JIRA)
Use DataSources in creating the ConnectorBindings instead of creating one using the Driver
------------------------------------------------------------------------------------------
Key: TEIID-429
URL: https://jira.jboss.org/jira/browse/TEIID-429
Project: Teiid
Issue Type: Task
Affects Versions: 6.x
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.0.0
Currently when we have separate configurations for XA sources and Non-XA sources, these should be combined into one definition, and by default we should make attempt use the data sources instead of Drivers. This will make it easy on the user in specifying the properties rather than coming up with unique URL for the data source.
This will add
DatabaseName
ServerName
Port
properties in addition to already provided,
User
Password
URL -> expert=true
properties. The URL property will be set to "expert", so that if one needs to use the Driver, you can still use it. In addition this needs to provide support to add additional properties that may be needed by the specific data source. For this add
OptionalProperties
This should be supplied in the format [name=value;name=value] and runtime engines should support these to add these properties as DataSource bean properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months