Details
-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.1.0.Beta1
-
Fix Version/s: 3.1.0.Beta4
-
Labels:None
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Actually, JpaIdentityStore was doing this a little wrong, and was setting the "role names supported" feature to false even when it should have been true in some cases. I've fixed this for these cases, however the IdentityStore interface in PicketLink is still ambiguous about what the getRelationshipNames() method should be returning if there isn't a formal relationship names table (JpaIdentityStore just returns an empty set).
Show
Shane Bryzak
added a comment - Actually, JpaIdentityStore was doing this a little wrong, and was setting the "role names supported" feature to false even when it should have been true in some cases. I've fixed this for these cases, however the IdentityStore interface in PicketLink is still ambiguous about what the getRelationshipNames() method should be returning if there isn't a formal relationship names table (JpaIdentityStore just returns an empty set).
Shane Bryzak
added a comment - Actually, JpaIdentityStore was doing this a little wrong, and was setting the "role names supported" feature to false even when it should have been true in some cases. I've fixed this for these cases, however the IdentityStore interface in PicketLink is still ambiguous about what the getRelationshipNames() method should be returning if there isn't a formal relationship names table (JpaIdentityStore just returns an empty set). 
I've checked the code for this and it actually is already optional, however we should be checking the feature set of the IdentityStore before calling methods such as getRelationshipNames()