Bug 816307 - Adding Teiid VDB as a local tx datasource requires Security Deployment Type
Adding Teiid VDB as a local tx datasource requires Security Deployment Type
Status: CLOSED DUPLICATE of bug 752399
Product: RHQ Project
Classification: Other
Component: Operations (Show other bugs)
x86_64 Linux
unspecified Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2012-04-25 14:45 EDT by Paul Nittel
Modified: 2013-01-10 18:24 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-25 14:55:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Nittel 2012-04-25 14:45:11 EDT
Description of problem:
Previously specifying the Security Deployment Type was not required

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

How reproducible:
Take a deployed Teiid VDB and make it a datasource (ModeShape ought to work fine)

Steps to Reproduce:
1. Navigate to Datsources Local TX Datasources
2. Add a new resource
3. Give it a JNDI name
4. Provide a username and password
5. For the JDBC Driver use: org.teiid.jdbc.TeiidDriver
6. For the URL use: jdbc:teiid:ModeShape@mm://localhost:31000
7. Save the new datasource
Actual results:
Get an error dialog containing:
java.lang.IllegalArgumentException:item value org.jboss.resource.metadata.mcf.SecurityDeploymentType{[NONE, APPLICATION, DOMAIN, DOMAIN_AND_APPLICATION]}:null for item name securityDeploymentType is not a org.jboss.resource.metadata.mcf.SecurityDeploymentType{[NONE, APPLICATION, DOMAIN, DOMAIN_AND_APPLICATION]}

Expected results:
Should just get a successfully deployed datasource

Additional info:
Comment 1 Paul Nittel 2012-04-25 14:55:37 EDT
Whoops. It's the same as Bug 752399 - [as5] Unable to create datasource

*** This bug has been marked as a duplicate of bug 752399 ***

Note You need to log in before you can comment on or make changes to this bug.