[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Cristiano Nicolai commented on TEIID-1331:
------------------------------------------
It's sounds a bit confusing, what do you mean is that the properties manipulated in
this class should be considered as read-only right? If this is true, I think that this
properties should be showed in the admin-console as read-only as well. My point is that
the Teiid JOPR plugin cant have different behaviour running in the Embedded JOPR or in a
JON/RHQ agent. In fact I think that the mapped roles is a important case to be changed via
plugin where admins can grant or revoke access without redeploying the VDB. I made some
tests with the changes that I reported and changing the roles during the runtime worked as
expected, restricting or granting access straight away and the changes still working after
server restart.
VDBMetaDataInstanceClassFactory is using old value
--------------------------------------------------
Key: TEIID-1331
URL:
https://jira.jboss.org/browse/TEIID-1331
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Affects Versions: 7.1
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Ramesh Reddy
Fix For: 7.1.1
Attachments: TeiidManagement.java
When updating ManagementComponent values via ProfileService,
VDBMetaDataInstanceClassFactory class is using ManagedProperty.getValue to retrieve the
updated value instead of MetaValue value received parameter. The value returned by
ManagedProperty.getValue is the actual one, not the new value that was submitted.
Basically should use:
MetaValueFactory.getInstance().unwrap(value);
Instead of:
MetaValueFactory.getInstance().unwrap(property.getValue());
In all properties manipulated by the setValue method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira