Bug 1316144

Summary: Resource adapter salesforce-34 has wrong slot configured
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Jan Stastny <jstastny>
Component: TeiidAssignee: Van Halbert <vhalbert>
Status: CLOSED CURRENTRELEASE QA Contact: Filip Elias <felias>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: aszczucz, blafond, jolee, jstastny, mbaluch, thauser, vhalbert
Target Milestone: ER2   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-24 11:47:29 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 Jan Stastny 2016-03-09 14:09:12 UTC
Description of problem:
In DV there is ra with id="salesforce-34" defined. But it should have slot="34" instead of slot="main" in its definition. (Using standalone.xml fragments to describe).

Affected version:
DV 6.3.0 ER1

Comment 1 Van Halbert 2016-03-09 14:20:28 UTC
Looking at ER1:

resource-adapter module:

<module xmlns="urn:jboss:module:1.1" name="org.jboss.teiid.resource-adapter.salesforce" slot="34">


standalone.xml:

            <translator name="salesforce-34" module="org.jboss.teiid.translator.salesforce" slot="34"/>


Not sure where you are seeing its not defined in slot=34.

Comment 2 Jan Stastny 2016-03-09 14:28:18 UTC
Hi Van,
the slot is wrong with resource-adapter salesforce-34 in standalone.xml: 

<resource-adapter id="salesforce-34">
    <module slot="main" id="org.jboss.teiid.resource-adapter.salesforce"/>
</resource-adapter>

I am sorry for the confusion there.

Comment 3 Van Halbert 2016-03-09 15:25:52 UTC
It appears we're running into an EAP issue when a CLI script is run that contains the SLOT, it doesn't recognize it.

Comment 4 JBoss JIRA Server 2016-03-13 21:54:41 UTC
Ramesh Reddy <rareddy> updated the status of jira TEIID-4028 to Resolved