Created attachment 932663 [details] tar with vdb, resource-adapter and queries definitions Description of problem: When querying vdb whose source is a webservice, then following exception occurs: ERROR [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue77) Connector worker process failed for atomic-request=bl5M9qEZIVcU.13.1.20: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException . . . Caused by: java.lang.ClassNotFoundException: javax.ws.rs.client.ClientException from [Module "org.apache.cxf.impl.frontend-jaxrs:main" from local module loader @11c836e8 (finder: local module finder @6f8cc276 (roots: /home/jstastny/DV-6.1.0/jboss-eap-6.3/modules,/home/jstastny/DV-6.1.0/jboss-eap-6.3/modules/system/layers/dv,/home/jstastny/DV-6.1.0/jboss-eap-6.3/modules/system/layers/base))] . . . Version-Release number of selected component (if applicable): DV 6.1.0-ER1 (also DV 6.1.0-DR2) How reproducible: Each time the vdb is queried. Steps to Reproduce: 1. add resource-adapter to standalone.xml 2. deploy vdb 3. start server 4. either connect with teiid-driver from a sql querying tool, or with SQLBulkQueryTool and execute one of given queries 5. run a query Actual results: ClassNotFoundException Expected results: Result set Additional info:
*** This bug has been marked as a duplicate of bug 1130665 ***
This problem still occurs. This bug was marked as duplicate of a bug within dom4j module. The "dom4j bug" should have been resolved with ER2. I don't know how to check that one, but my issue (which is marked as duplicate) still remains. I assume that referenced "bug 1130665" was successfully resolved in ER2 as there is no activity on that one, therefore I reopen this bug as it seems that it should not have been considered as duplicate of mentioned bug.
<jdc> vhalbert: I think that it would be cleanest to provide our own javax/ws/rs/api/main module, replacing jboss-jaxrs-api_1.1_spec-1.0.1.Final-redhat-2.jar with javax.ws.rs-api.2.0.1.jar.
*** Bug 1146952 has been marked as a duplicate of this bug. ***
It has been validated by TEIIDDES-2284 that applying the updated jar fixes the issue.
Ted Jones <tejones> updated the status of jira TEIIDDES-2284 to Resolved
Teiid has committed the fix upstream to add the use of the 2.0 version as slot=2.0. No need for productization to add an override to the build.
TEIID kit will be updated to have the spring framework 3.2.12 version (https://bugzilla.redhat.com/show_bug.cgi?id=1166378) and the ClassNotFoundException will be fixed by changing to use name="javax.ws.rs.api" slot="2.0". This is all associated with updating the connector-ws.
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2284 to Closed