Bug 1056974
Summary: | Designer should not add connection-jndi-name attribute in VDB.xml when no jndi is being referenced | ||
---|---|---|---|
Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Lucie Fabrikova <lfabriko> |
Component: | Tooling | Assignee: | Van Halbert <vhalbert> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | asmigala, atangrin, dlesage, fnguyen, lfabriko, vhalbert |
Target Milestone: | ER2 | ||
Target Release: | 6.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Teiid Designer was adding a connection-jndi-name attribute to the VDB.xml file even when no JNDI was being referenced. This caused an undesired response when running queries against the virtual database. This happened because, when the user blanks out the JNDIreference or it contained space(s), the Designer was incorrectly the connection-jndi-name attribute to the vdb.xml. This behaviour has now been corrected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-17 18:05:13 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lucie Fabrikova
2014-01-23 09:32:08 UTC
You can't just leave the jndi-name blank, cause it will fail (it's a known issue, with a fix targeted to first roll-up). The work-around is to put a space in the jndi name. This is a use case that will rarely come up because the Yahoo translator is not in the product, and the only other translator where no JNDI would be valid is when using loopback (and that's for testing only). Barry LaFond <blafond> updated the status of jira TEIIDDES-2024 to Closed |