[
https://issues.jboss.org/browse/SEAMSECURITY-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653294#comment-12653294
]
John Schneider commented on SEAMSECURITY-138:
---------------------------------------------
Try the following enums for testing:
{code:title=IdentityObjectType.java|borderStyle=solid}
public enum IdentityObjectType {
USER,
GROUP
}
{code}
{code:title=CredentialType.java|borderStyle=solid}
public enum CredentialType {
PASSWORD,
CERTIFICATE
}
{code}
{code:title=RelationshipType.java|borderStyle=solid}
public enum RelationshipType {
JBOSS_IDENTITY_MEMBERSHIP,
JBOSS_IDENTITY_ROLE
}
{code}
> Support enums for IdentityType, CredentialType and RelationshipType in
> JpaIdentityStore
> ---------------------------------------------------------------------------------------
>
> Key: SEAMSECURITY-138
> URL: https://issues.jboss.org/browse/SEAMSECURITY-138
> Project: Seam Security
> Issue Type: Feature Request
> Affects Versions: 3.1.0.Final
> Environment: Glassfish 3.1.1
> Reporter: John Schneider
> Attachments: JpaIdentityStore.diff.txt
>
>
> I thought it would be nice for JPAEntityStore to support enums for
> IdentityType, CredentialType and RelationshipType. That way, we don't need
> to create data tables and entity beans for things that only have a few
> different possible values that are basically constants.
> Please review and try the attached patch to JPAEntityStore. I've done some
> limited testing by creating a new user and a role relationship and find it to
> be working well so far.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
