[
https://jira.jboss.org/jira/browse/JBAS-6669?page=com.atlassian.jira.plug...
]
Charles Crouch commented on JBAS-6669:
--------------------------------------
Ok, so the real issue is that we should not even expose the "config-property"
prop for Datasource, all of its underlying name/value pairs should have other top level
read/write properties. So if "config-property" is in the rhq plugin
configuration descriptor then it needs to be removed.
EMBJOPR-58 discusses making it read-only but i dont think even that should be needed.
when new items are added to the "config-property" composite
ManagedProperty on a Datasource component, after updateComponent() is called, the items
that were added are gone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6669
URL:
https://jira.jboss.org/jira/browse/JBAS-6669
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
I'm assuming this may be because the "config-property" prop is meant to be
read-only on Datasources. If that is the case, the ManagedProperty just needs to be marked
as read-only once that API has been added.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira