[
https://jira.jboss.org/jira/browse/JBSEAM-3466?page=com.atlassian.jira.pl...
]
Shane Bryzak closed JBSEAM-3466.
--------------------------------
Resolution: Done
Implemented in SVN. Could you please test this with latest SVN trunk and let me know if
it works with your application? There should be no additional configuration required, as
there's some magic within the changes that auto-detects the correct properties to set
in the cross-reference table.
@UserRoles only works when using one ManyToMany-Relation instead of
two OneToMany-Relations
-------------------------------------------------------------------------------------------
Key: JBSEAM-3466
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3466
Project: Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.1.0.BETA1
Environment: EJB 3.0, JBOSS 4.2, SEAM 2.1, RichFaces (3.2)
Reporter: nimo stephan
Assignee: Shane Bryzak
Fix For: 2.1.0.GA
@UserRoles only works in ManyToMany-Relation.
If we provide two @OneToMany-relations instead of one @ManyToMany, then @UserRoles does
not work!
The UserRolesProperty returns the UserRoles-Instance instead of the Roles-Instance.
However, when having additional attributes in UserRoles we should better use two
@OneToMany-Relations -
but then @UserRoles does not work.
As Shane said:
"I don't think that we currently support cross reference tables in this manner,
although we should. "
Yes, it would be fine:-)
thanks.
--
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