April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-843) ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-843?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reopened FORGE-843: -------------------------------------- Still another remaining issue... > ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped > ----------------------------------------------------------------------------------------------------------------- > > Key: FORGE-843 > URL: https://issues.jboss.org/browse/FORGE-843 > Project: Forge > Issue Type: Bug > Components: Container > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Alpha3 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-863) Maven mirror settings not used within forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-863?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-863. --------------------------------- Resolution: Done Merged in 832cad6e45ab25f4e3be23acddb32b46bb8297c3 > Maven mirror settings not used within forge > ------------------------------------------- > > Key: FORGE-863 > URL: https://issues.jboss.org/browse/FORGE-863 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.2.3.Final > Reporter: Yann Albou > Assignee: Yann Albou > Labels: maven, mirror, nexus > Fix For: 1.2.4.Final > > > In a Maven/Nexus environnement the settings.xml file is configured to use Maven mirror (see http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-grou...) and because of this we don't need to configure proxy settings (for those who are behing a firewall..) > But it seems Forge don't use mirror information so that Forge project cannot be created/installed and lot of requests timed out... > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-843) ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-843?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-843: ------------------------------------- Summary: ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped (was: ClassCastException when the same addon is deployed in multiple configured repositories) > ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped > ----------------------------------------------------------------------------------------------------------------- > > Key: FORGE-843 > URL: https://issues.jboss.org/browse/FORGE-843 > Project: Forge > Issue Type: Bug > Components: Container > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Alpha3 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-843) ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-843?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-843. ------------------------------------ Resolution: Done Done. > ClassCastException due to CLAC not proxying Iterable, and Proxied parameter Class<?> not being properly unwrapped > ----------------------------------------------------------------------------------------------------------------- > > Key: FORGE-843 > URL: https://issues.jboss.org/browse/FORGE-843 > Project: Forge > Issue Type: Bug > Components: Container > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Alpha3 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-572) Forge scaffold faces creates view beans with Id always Long against user-generated Entities

by claudio perrotta (JIRA)

[ https://issues.jboss.org/browse/FORGE-572?page=com.atlassian.jira.plugin.... ] claudio perrotta commented on FORGE-572: ---------------------------------------- @Vineet i think that the problem is still present and the bug must be reopened, because it's not only related to the UI (that not showing the field like pointed in https://issues.jboss.org/browse/FORGE-870) but, with preloaded data in the database or insert data with PK set to auto increment, i see the entries but if i click it for the detail i have an error like this in console : Provided id of the wrong type for class org.forgetest.model.GeoCities. Expected: class java.lang.String, got class java.lang.Long. Now i have tried to add an id column (BIGINT) to all table and make it PK as a workaround..it works I can add and view data...but i found other three bug. One is https://issues.jboss.org/browse/FORGE-870, i have it for example in all Many-to-Many table. Second is that : if there is a column which reference a PK of the another table the GUI show a dropdown menu( with "non-human meaning" value ). after setting this value and saving, all seems ok, but when i want to modify something for this record the GUI not show me the value that was setted. it's not much clear, i know.. Third (but i think its related to Hibernate) : i have two table with a 1:1 identifying relatioship, and so they have the same PK, when generate entities have a method for the class like public void newStrCustomServices() { this.getStrCustomServices = new StrCustomServices(); } but there isn't any attribute in the class like "getStrCustomServices", to fix i need to change it in "strCustomServices", and so the UI work but with the previous first bug. > 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.2.4.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, 7 months

1
0
0 / 0

[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 closed FORGE-572. --------------------------------- Assignee: Vineet Reynolds > 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.2.4.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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-572) Forge scaffold faces creates view beans with Id always Long against user-generated Entities

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-572?page=com.atlassian.jira.plugin.... ] Vineet Reynolds resolved FORGE-572. ----------------------------------- Assignee: (was: Vineet Reynolds) Fix Version/s: 1.2.4.Final (was: 1.1.0.Final) Resolution: Done Resolved the property based annotation parsing issue. > 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 > Priority: Minor > Labels: starter > Fix For: 1.2.4.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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-572) Forge scaffold faces creates view beans with Id always Long against user-generated Entities

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-572?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-572: --------------------------------------- Claudio, this issue involving Id fields of type Long in the ViewBean should be fixed now, but I'm afraid you might run into FORGE-870 (that would be fixed shortly). > 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 > Priority: Minor > Labels: starter > Fix For: 1.1.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, 7 months

1
0
0 / 0

[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 updated FORGE-572: ---------------------------------- Assignee: Vineet Reynolds > 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.1.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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-870) Faces scaffold does not generate form fields for @Id fields not annotated with @GeneratedValue

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-870: ------------------------------------- Summary: Faces scaffold does not generate form fields for @Id fields not annotated with @GeneratedValue Key: FORGE-870 URL: https://issues.jboss.org/browse/FORGE-870 Project: Forge Issue Type: Bug Components: Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds The Faces scaffold does not generate any form fields for @Id annotated fields. This is because the Metawidget JPAInspector used by the scaffold plugin is configured to hide Ids. This should however be done conditionally, when the @Id field is also annotated with a @GeneratedValue, since attempting to create a new entity instance without a provided id, results in the following error being displayed: {noformat}org.hibernate.id.IdentifierGenerationException: ids for this class must be manually assigned before calling save(){noformat} -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013