[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-911?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-911:
---------------------------------------
Also please test against 1.3.0.Final to confirm this wasn't already fixed.
> Scaffolding from a Join table with more than two primary key columns is not supported
> -------------------------------------------------------------------------------------
>
> Key: FORGE-911
> URL: https://issues.jboss.org/browse/FORGE-911
> Project: Forge
> Issue Type: Story
> Components: Scaffold
> Affects Versions: 1.2.3.Final
> Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1
> Reporter: Hanine Hanynowsky
>
> Using JForge (latest version); one will have a hibernate error complaining about the M2M join table (linking two objects) having more than 2 key columns.
> Naturally, if you join a table with one key column with a another table with a composite primary key (two columns key), in order to get a Many to Many relationship, you'll end up with a join table that has three key columns.
>
> When Forge finished scaffolding no error is displayed. You get the error when deploying to the container (JBoss as 7.1.1 for example). And the app is not deployed (rolled back).
>
> Is this a bug? A feature request?
>
> It seems to me that with the EmbeddedId bug, this one is also serious stuff!!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-572) Forge scaffold faces creates view beans with Id always Long against user-generated Entities
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-572?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-572:
---------------------------------------
Hi Hanine,
Forge 1.3.0.Final was released in May 15th. You may download it and use it anytime! :)
Best Regards,
George Gastaldi
> Forge scaffold faces creates view beans with Id always Long against user-generated Entities
> -------------------------------------------------------------------------------------------
>
> Key: FORGE-572
> URL: https://issues.jboss.org/browse/FORGE-572
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.0.2.Final
> Environment: JBoss Developer Studio 5 Beta 2, Embedded Forge 1.0.2.Final
> Reporter: Will Dinyes
> Assignee: Vineet Reynolds
> Priority: Minor
> Labels: starter
> Fix For: 1.3.0.Final
>
>
> When running:
> scaffold from-entity ~.domain.* --overwrite
> The generated view Bean will always use an id field as a long, even if the entity uses a different type for the @Id. For instance, this code, in an Entity class called ValMealtype:
> @Id
> @GeneratedValue(strategy=GenerationType.IDENTITY)
> @Column(unique=true, nullable=false, length=20)
> private String meal;
> Generates, in ValMealtypeBean:
> private Long id;
> <-- associated gettters and setters -->
> And, later in the class:
> return ValMealtypeBean.this.entityManager.find(ValMealtype.class, Long.valueOf(value));
> That line in particular doesn't work at all, of course, since a Long can't be parsed out of a non-numeric String. I suppose I could name my meals with hex digits . . . CAFE . . . BEEF . . . but sadly, Chicken isn't going to fly.
> Basically, scaffold probably needs to look at the type of @Id in the entity and use that to set the id field type in the generated bean.
> As this is reported against a non-current release, I understand it may be fixed already. In this case, a new Beta of JBDS 5 is probably in order, as that's where I'm seeing this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported
by Hanine Hanynowsky (JIRA)
Hanine Hanynowsky created FORGE-911:
---------------------------------------
Summary: Scaffolding from a Join table with more than two primary key columns is not supported
Key: FORGE-911
URL: https://issues.jboss.org/browse/FORGE-911
Project: Forge
Issue Type: Story
Components: Scaffold
Affects Versions: 1.2.3.Final
Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1
Reporter: Hanine Hanynowsky
Using JForge (latest version); one will have a hibernate error complaining about the M2M join table (linking two objects) having more than 2 key columns.
Naturally, if you join a table with one key column with a another table with a composite primary key (two columns key), in order to get a Many to Many relationship, you'll end up with a join table that has three key columns.
When Forge finished scaffolding no error is displayed. You get the error when deploying to the container (JBoss as 7.1.1 for example). And the app is not deployed (rolled back).
Is this a bug? A feature request?
It seems to me that with the EmbeddedId bug, this one is also serious stuff!!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-910) In View Beans, Search predicate for boolean fields is not supported
by Hanine Hanynowsky (JIRA)
Hanine Hanynowsky created FORGE-910:
---------------------------------------
Summary: In View Beans, Search predicate for boolean fields is not supported
Key: FORGE-910
URL: https://issues.jboss.org/browse/FORGE-910
Project: Forge
Issue Type: Story
Components: Scaffold
Affects Versions: 1.2.3.Final
Environment: Linux 3.8, Firefox.
Reporter: Hanine Hanynowsky
Priority: Minor
In View Beans, Search predicate for boolean fields is not supported.
Jboss Forge generates the View Bean with search support using JPA criteria expressions for fields of type String and Entity objects but it does not for boolean fields.
Is this not supported? A bug? A feature request? Or simply that it's not possible to use boolean fields with JPA predicate isLike & equ
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-873) Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky edited comment on FORGE-873 at 5/20/13 10:57 PM:
-------------------------------------------------------------------
Guys! I always used : public String toString {return someattribute;} in the entities. That allows to display a human-readable string representation of a drop down object instead of its Java reference!
In some lazy cases, I did as Claudia did. But that's too much modification if you have tons of entities....
Wouldn't adding toString method be a fix for this bug? (The Entity generation plugin should pick the ID field and the first following field as String representation for the toString method). no?
was (Author: hanynowsky):
Guys! I always used : public String toString {return someattribute;} in the entities. That allows to display a human-readable string representation of a drop down object instead of its Java reference!
In some lazy cases, I did as Claudia did. But that's too much modification if you have tons of entities....
Wouldn't adding toString method a fix for this bug? (The Entity generation plugin should pick the ID field and the first following field as String representation for the toString method). no?
> Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-873
> URL: https://issues.jboss.org/browse/FORGE-873
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.2.3.Final
> Environment: JBoss 7.1.1 final , Hibernate 4.2.0.final,
> Reporter: claudio perrotta
> Assignee: Vineet Reynolds
>
> For a table with a foreign key the UI permits to select the possible values, but this values are listed in a dropdown menu in a form like "org.forgetest.model.Entity@5f9ba38e" (would be preferable that the string present be relative to the PK referenced)
> Anyway, after setting this field and submitting the form, the data are inserted in the table correctly but when i want to modify the record, the UI doesn't show the setted value for the foreign key and i must set it again before saving.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-873) Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky commented on FORGE-873:
-----------------------------------------
Guys! I always used : public String toString {return someattribute;} in the entities. That allows to display a human-readable string representation of a drop down object instead of its Java reference!
In some lazy cases, I did as Claudia did. But that's too much modification if you have tons of entities....
Wouldn't adding toString method a fix for this bug? (The Entity generation plugin should pick the ID field and the first following field as String representation for the toString method). no?
> Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-873
> URL: https://issues.jboss.org/browse/FORGE-873
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.2.3.Final
> Environment: JBoss 7.1.1 final , Hibernate 4.2.0.final,
> Reporter: claudio perrotta
> Assignee: Vineet Reynolds
>
> For a table with a foreign key the UI permits to select the possible values, but this values are listed in a dropdown menu in a form like "org.forgetest.model.Entity@5f9ba38e" (would be preferable that the string present be relative to the PK referenced)
> Anyway, after setting this field and submitting the form, the data are inserted in the table correctly but when i want to modify the record, the UI doesn't show the setted value for the foreign key and i must set it again before saving.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-572) Forge scaffold faces creates view beans with Id always Long against user-generated Entities
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-572?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky commented on FORGE-572:
-----------------------------------------
I have the same issue with 1.2.3 (Int or String ids are translated into Long in the view Beans). Happy this is gonna be fixed in the newt release!
> Forge scaffold faces creates view beans with Id always Long against user-generated Entities
> -------------------------------------------------------------------------------------------
>
> Key: FORGE-572
> URL: https://issues.jboss.org/browse/FORGE-572
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.0.2.Final
> Environment: JBoss Developer Studio 5 Beta 2, Embedded Forge 1.0.2.Final
> Reporter: Will Dinyes
> Assignee: Vineet Reynolds
> Priority: Minor
> Labels: starter
> Fix For: 1.3.0.Final
>
>
> When running:
> scaffold from-entity ~.domain.* --overwrite
> The generated view Bean will always use an id field as a long, even if the entity uses a different type for the @Id. For instance, this code, in an Entity class called ValMealtype:
> @Id
> @GeneratedValue(strategy=GenerationType.IDENTITY)
> @Column(unique=true, nullable=false, length=20)
> private String meal;
> Generates, in ValMealtypeBean:
> private Long id;
> <-- associated gettters and setters -->
> And, later in the class:
> return ValMealtypeBean.this.entityManager.find(ValMealtype.class, Long.valueOf(value));
> That line in particular doesn't work at all, of course, since a Long can't be parsed out of a non-numeric String. I suppose I could name my meals with hex digits . . . CAFE . . . BEEF . . . but sadly, Chicken isn't going to fly.
> Basically, scaffold probably needs to look at the type of @Id in the entity and use that to set the id field type in the generated bean.
> As this is reported against a non-current release, I understand it may be fixed already. In this case, a new Beta of JBDS 5 is probably in order, as that's where I'm seeing this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-909) Sub-folders not displaying in Directory Picker
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/FORGE-909?page=com.atlassian.jira.plugin.... ]
Koen Aers resolved FORGE-909.
-----------------------------
Resolution: Won't Fix
This is an issue (probably only on OSX) that is not proper to Forge. You can also reproduce it while navigating folders on your machine when e.g. importing Maven projects. A workaround is to click another folder and then click on the target folder again, the contents should appear.
> Sub-folders not displaying in Directory Picker
> ----------------------------------------------
>
> Key: FORGE-909
> URL: https://issues.jboss.org/browse/FORGE-909
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha4
> Reporter: Lincoln Baxter III
> Assignee: Koen Aers
> Fix For: 2.0.0.Alpha5
>
>
> i noticed in the F2 new-project wizard, that when you click on a folder in the directory picker, things kind-of lock up and wait forever, never showing the sub-folders to choose. then if you click OK, and re-enter the picker, you can select sub-folders again normally, then it locks again and you have to repeat.
> 9:00 any ideas about that?
> YouTube video showing the problem - https://www.youtube.com/watch?v=skhbUz37ZPU
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-909) Sub-folders not displaying in Directory Picker
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-909?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-909:
-------------------------------------
Description:
i noticed in the F2 new-project wizard, that when you click on a folder in the directory picker, things kind-of lock up and wait forever, never showing the sub-folders to choose. then if you click OK, and re-enter the picker, you can select sub-folders again normally, then it locks again and you have to repeat.
9:00 any ideas about that?
YouTube video showing the problem - https://www.youtube.com/watch?v=skhbUz37ZPU
was:
i noticed in the F2 new-project wizard, that when you click on a folder in the directory picker, things kind-of lock up and wait forever, never showing the sub-folders to choose. then if you click OK, and re-enter the picker, you can select sub-folders again normally, then it locks again and you have to repeat.
9:00 any ideas about that?
> Sub-folders not displaying in Directory Picker
> ----------------------------------------------
>
> Key: FORGE-909
> URL: https://issues.jboss.org/browse/FORGE-909
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha4
> Reporter: Lincoln Baxter III
> Assignee: Koen Aers
> Fix For: 2.0.0.Alpha5
>
>
> i noticed in the F2 new-project wizard, that when you click on a folder in the directory picker, things kind-of lock up and wait forever, never showing the sub-folders to choose. then if you click OK, and re-enter the picker, you can select sub-folders again normally, then it locks again and you have to repeat.
> 9:00 any ideas about that?
> YouTube video showing the problem - https://www.youtube.com/watch?v=skhbUz37ZPU
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (FORGE-909) Sub-folders not displaying in Directory Picker
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/FORGE-909?page=com.atlassian.jira.plugin.... ]
Koen Aers reassigned FORGE-909:
-------------------------------
Assignee: Koen Aers
> Sub-folders not displaying in Directory Picker
> ----------------------------------------------
>
> Key: FORGE-909
> URL: https://issues.jboss.org/browse/FORGE-909
> Project: Forge
> Issue Type: Bug
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha4
> Reporter: Lincoln Baxter III
> Assignee: Koen Aers
> Fix For: 2.0.0.Alpha5
>
>
> i noticed in the F2 new-project wizard, that when you click on a folder in the directory picker, things kind-of lock up and wait forever, never showing the sub-folders to choose. then if you click OK, and re-enter the picker, you can select sub-folders again normally, then it locks again and you have to repeat.
> 9:00 any ideas about that?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months