Bug 816307 - Adding Teiid VDB as a local tx datasource requires Security Deployment Type
Summary: Adding Teiid VDB as a local tx datasource requires Security Deployment Type
Keywords:
Status: CLOSED DUPLICATE of bug 752399
Alias: None
Product: RHQ Project
Classification: Other
Component: Operations
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-25 18:45 UTC by Paul Nittel
Modified: 2013-01-10 23:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-25 18:55:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Paul Nittel 2012-04-25 18:45:11 UTC
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 18:55:37 UTC
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.