[
http://jira.jboss.com/jira/browse/JBSEAM-1126?page=all ]
Dan Allen updated JBSEAM-1126:
------------------------------
Attachment: JBSEAM-1126-v1.txt
Essentially, the naming conventions and navigation used by seam-gen make it impossible to
select the same related entity to satisfy two different relationships. However, we can at
least prevent the compile error from occurring by eliminating duplicate references to the
same home. I have included a patch which incorporates this logic. It has the same effect
as removing the duplicate reference.
Generate-entities creates a class with the error
------------------------------------------------
Key: JBSEAM-1126
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1126
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 1.2.1.GA, 1.2.0.GA
Reporter: Alex Narinsky
Priority: Minor
Attachments: JBSEAM-1126-v1.txt, JBSEAM-1126-v1.txt
I am using generate-entities. Prior to version 1.2 this worked fine. Starting from
version 1.2 one generated class contains the error - double definition of one
"In" element.
Please, see the text below
@Name("moviesHome")
public class MoviesHome extends EntityHome<Movies> {
@In(create = true)
ContactsHome contactsHome;
@In(create = true)
ProjectsHome projectsHome;
@In(create = true)
ContactsHome contactsHome;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira