Bug 900086 (JBPAPP6-1579)
| Summary: | hot deployed -ds.xml datasources do not show up as datasources in the admin console | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Burr Sutter <bsutter> | ||||||||||
| Component: | Web Console | Assignee: | Harald Pehl <hpehl> | ||||||||||
| Status: | CLOSED EOL | QA Contact: | Pavel Jelinek <pjelinek> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | unspecified | CC: | brian.stansberry, bsutter, hpehl, ike.braun, jdoyle, jkudrnac, myarboro, smcgowan | ||||||||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||||||||
| Target Release: | EAP 6.4.0 | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1579 | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2019-08-19 12:45:54 UTC | Type: | Feature Request | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1061030 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Burr Sutter
2012-03-23 19:02:21 UTC
I believe hot deployed JBDC drivers do not show up "correctly" in the admin console as well that should be double checked. Attachment: Added: Screen Shot 2012-03-23 at 3.02.54 PM.png Attachment: Added: Screen Shot 2012-03-23 at 3.02.32 PM.png Attachment: Added: Screen Shot 2012-03-23 at 3.00.34 PM.png Attachment: Added: sakila-ds.xml This is by design, see: https://docs.jboss.org/author/display/AS71/DataSource+configuration Specifically, {code} This feature is primarily intended for development, and thus has a few limitations to be aware of. It can not be altered in any of the management interfaces (consle, CLI, etc). Only limited runtime information is available. Also, password vaults and security domains are not deployable, so these can not be bundled with a datasource deployment. {code} That is correct Shelly. The datasources that the console edits are the ones in the management model. Deployed datasources are more limited and can not be modified. We do however make the statistics for them available under the runtime deployment portion in the management model. Note that in domain mode this information (as with other runtime stats) is per Server and can't be globally represented. I'm assigning this to Heiko, so he can comment on whether or not he has the time to represent this in the console somehow. In any case I dont think it makes sense in the main datasources section. OK As a developer, I would like to see that the DS was deployed and I first go to the "datasources" area of the admin console - and it was not there. We use the -ds.xml as the primary solution for allowing JBDS to deploy a datasource. Not a big deal but likely a "gotcha" for the average developer looking inside the admin console. i agree with burr. from a ux perspective this is what you would assume. i can see what we can do. Docs QE Status: Removed: NEW Heiko Braun <ike.braun> updated the status of jira HAL-348 to Closed Heiko Braun <ike.braun> updated the status of jira HAL-348 to Reopened Can be considered for an EAP 7 feature. Heiko Braun <ike.braun> updated the status of jira HAL-348 to Closed |