6:32 p.m.
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.2
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
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
6:36 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Cristiano Nicolai commented on TEIID-1331:
------------------------------------------
This problem was evident when I was trying to use the JOPR Plugin with JON/RHQ but I made
some tests and the proposed solution worked fine in both scenario: Embedded JOPR and
JON/RHQ Agent.
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.2
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
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
6:42 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Cristiano Nicolai updated TEIID-1331:
-------------------------------------
Attachment: TeiidManagement.java
Java test class
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.2
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
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
7:20 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy updated TEIID-1331:
--------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
Fix Version/s: 7.1.1
Affects Version/s: 7.1
(was: 7.2)
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
11:17 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy commented on TEIID-1331:
-------------------------------------
The reason they are coded that way because they are considered as read-only properties.
There are only few properties on the MO that are allowed for updating. We could set them
as "readOnly" in the annotations, however when the update file is written, it
writes with out "read only" fields, thus it can never merge correctly with MO
from deployer and MO from update, next time the Server starts.
So, we allowed writes all fields, but wrote the old values into it thus we controlled
"readOnly" on fields we want. Then on JOPR plugin, we actually represented them
in UI. However, if one uses the Profile Service API directly to update then they will see
the behaviour you are seeing.
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
6:14 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
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
11:45 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy commented on TEIID-1331:
-------------------------------------
The JOPR plugin does indeed marks all the fields "read-only", not editable. On a
VDB you can only edit
1) Connection Type
2) Model -> Source -> JNDI Name
3) Data Source -> Mapped Role Name
4) multisource suff
everything else are "read-only". If you are seeing them in JON as writeable,
then we have an issue. I agree with your comment about "mapped roles", and it is
writeable in the JOPR and Admin API, and I just tested the functionality.
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
5:24 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy commented on TEIID-1331:
-------------------------------------
Ted, please confirm the above mis-match if you are seeing in the JOPR, otherwise I am
inclined to reject this issue
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:05 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://jira.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy resolved TEIID-1331.
---------------------------------
Resolution: Rejected
Per Ted, the JON and JOPR consoles behave the same way. If one is coding directly against
the Profile Service, the same may not be true as per the editability of it. So, the
enforcement is on the GUI side, not in the Server side.
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:32 a.m.
New subject: [JBoss JIRA] Closed: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value
[
https://issues.jboss.org/browse/TEIID-1331?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1331.
---------------------------------
VDBMetaDataInstanceClassFactory is using old value
--------------------------------------------------
Key: TEIID-1331
URL: https://issues.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5015
days inactive
5091
days old
9 comments
3 participants
participants (3)
-
Cristiano Nicolai (JIRA) -
Ramesh Reddy (JIRA)
-
Steven Hawkins (JIRA)