-
1. Re: Seam-gen problem with 2 foriegn keys for the same table
dsailer.d.sailer.comcast.net Apr 5, 2009 5:34 PM (in response to ahmadadly)this is a known issue. I recall seeing a jira for it. It really comes down to the fact that it's not possible to generate an intelligent CRUD app without having more context than just the hibernate relationship annotations. You will most likely find yourself changing a lot of what seam-gen generates anyway and having to understand how it works. I found it a good way to learn seam. But to start out, just delete one of the two currentyHome's.
-
2. Re: Seam-gen problem with 2 foriegn keys for the same table
dan.j.allen Apr 5, 2009 9:30 PM (in response to ahmadadly)I fixed seam-gen in SVN so that it only creates one of the injection points. Unfortunately, you cannot establish the relationship in the UI because it's just outside of what we can accomplish with the reverse engineering without introducing unnecessary complexity. Therefore, it will be up to you to make the UI work. At least it compiles now ;)
-
3. Re: Seam-gen problem with 2 foriegn keys for the same table
ahmadadly Apr 6, 2009 11:50 AM (in response to ahmadadly)Thanks Dan Allen and d sailer for your reply and help
-
4. Re: Seam-gen problem with 2 foriegn keys for the same table
ahmadadly Apr 9, 2009 2:22 PM (in response to ahmadadly)Hi agian,
I have removed the duplicated instance from my class. But I got another problem, which is the 2 relations will reflect each other.
By another meaning, when I try to create new record of the TransactionHistory in the web application and try to select specific From Currency instance, I found that the To Currency instance is the same in TransactionHistoryEdit.seam!
Can anyone help in this?