Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1057076

Summary:	Querying webservice of VDB throws javax.naming.NameNotFoundException
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Lucie Fabrikova <lfabriko>
Component:	Tooling	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, fnguyen, lfabriko, vhalbert
Target Milestone:	---
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-17 13:27:36 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 12:38:55 UTC

Description of problem:
Querying (via soapui) a webservice created from VDB which contains a model without a JNDI name (model MarketData with yahoo translator, viz TDES-2024), server throws exception javax.naming.NameNotFoundException.
If the model without JNDI is removed from VDB, the query is successful.

(the models in project were created via "Consume a SOAP web service" cheat sheet from DV6 doc., detailed instructions in TestSpecs/Designer8-updatedE2eConsumeSoapWS-cheatSheetCompletion.odt)


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. deploy countryInfoNoJNDI.vdb to DV server in JBDS

in jboss-cli:
2. add datasource
data-source add --name=countryinfonojndi --driver-name=teiid --connection-url=jdbc:teiid:countryInfoNoJNDI@mm://localhost:31000 --jndi-name=java:/countryinfonojndi --user-name=user --password=user
3. enable datasource (data-source enable --name=countryinfonojndi), reload (/:reload)
4. deploy countryInfoNoJNDI.war

5. run soapui (http://localhost:8080/countryInfoNoJNDI/CountryInfoServiceView_Result, select getResult -> Request 1, enter e.g. <sCountryISOCode>USA</sCountryISOCode>)


Actual results:


Expected results:


Additional info:

Comment 2 Van Halbert 2014-01-23 13:31:38 UTC

How did you go about setting the JNDI name when defining the VDB?  You can't just leave it 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).

Comment 3 JBoss JIRA Server 2014-01-23 16:22:57 UTC

Lucie Fabrikova <lfabriko> updated the status of jira TEIIDDES-2030 to Closed

Comment 4 Lucie Fabrikova 2014-01-23 16:25:18 UTC

It related to TEIDDES-2024, all is fixed in nightly build.