October 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-147) Use directives to encapsulate the logic for ui <-> model synchronization

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-147: -------------------------------------------- Summary: Use directives to encapsulate the logic for ui <-> model synchronization Key: FORGEPLUGINS-147 URL: https://issues.jboss.org/browse/FORGEPLUGINS-147 Project: Forge Plugins Issue Type: Enhancement Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds The AngularJS scaffold creates controllers that contain logic to synchronize the UI with the model. Controllers should not contain this logic ideally, and as such this should be encapsulated into a directive. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1294) Create Faces Commands to create new ValueChangeListener methods

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1294: ----------------------------------------- Summary: Create Faces Commands to create new ValueChangeListener methods Key: FORGE-1294 URL: https://issues.jboss.org/browse/FORGE-1294 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 2.0.0.Alpha14 Reporter: Lincoln Baxter III Priority: Minor Fix For: 2.x Future -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1293) Create Faces Commands to create new ValueChangeListener objects

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1293: ----------------------------------------- Summary: Create Faces Commands to create new ValueChangeListener objects Key: FORGE-1293 URL: https://issues.jboss.org/browse/FORGE-1293 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 2.0.0.Alpha14 Reporter: Lincoln Baxter III Priority: Minor Fix For: 2.x Future -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported

by Hanine Hanynowsky (JIRA)

[ https://issues.jboss.org/browse/FORGE-911?page=com.atlassian.jira.plugin.... ] Hanine Hanynowsky commented on FORGE-911: ----------------------------------------- a JPA/Eclipselink model can be downloaded from here: https://www.dropbox.com/sh/whxqy7w67ytze90/I-p91nOR9Z - See the Expertise & Book Entities. https://www.dropbox.com/sh/pg4wg3dvj3g6chc/4og2q8Za7A - Database: https://www.dropbox.com/s/ygn3q3qkah1q28w/prototype.sql Thanks in advance > 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: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final, 1.3.0.Final > Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1 > Reporter: Hanine Hanynowsky > Assignee: Vineet Reynolds > Fix For: 1.x Future > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported

by Hanine Hanynowsky (JIRA)

[ https://issues.jboss.org/browse/FORGE-911?page=com.atlassian.jira.plugin.... ] Hanine Hanynowsky commented on FORGE-911: ----------------------------------------- Hi Reynolds! Dorry for the delay! In the screenshot above, there are two tables (Expertise & Book) having a M-2-M identifying relationship; yet the Expertise table has a composite primary key, which involves the join table having also 3 primary keys. Hibernate seems to be unable to handle this kind of join tables as it expects only 2 primary key columns and hence fires the following exception error message: "org.hibernate.AnnotationException: A Foreign key refering org.otika.prototype.model.Expertise from org.otika.prototype.model.Book has the wrong number of column. should be 2". I would probably test this use case againt JPA through EclipseLink and check whether the same error is reproduced, since I am not sure whether it's Hibernate core or forge scaffolfing being responsible of that issue! > 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: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final, 1.3.0.Final > Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1 > Reporter: Hanine Hanynowsky > Assignee: Vineet Reynolds > Fix For: 1.x Future > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported

by Hanine Hanynowsky (JIRA)

[ https://issues.jboss.org/browse/FORGE-911?page=com.atlassian.jira.plugin.... ] Hanine Hanynowsky edited comment on FORGE-911 at 10/27/13 5:55 AM: ------------------------------------------------------------------- Hi Reynolds! Sorry for the delay! In the screenshot above, there are two tables (Expertise & Book) having a M-2-M identifying relationship; yet the Expertise table has a composite primary key, which involves the join table having also 3 primary keys. Hibernate seems to be unable to handle this kind of join tables as it expects only 2 primary key columns and hence fires the following exception error message: "org.hibernate.AnnotationException: A Foreign key refering org.otika.prototype.model.Expertise from org.otika.prototype.model.Book has the wrong number of column. should be 2". I would probably test this use case againt JPA through EclipseLink and check whether the same error is reproduced, since I am not sure whether it's Hibernate core or forge scaffolfing being responsible of that issue! was (Author: hanynowsky): Hi Reynolds! Dorry for the delay! In the screenshot above, there are two tables (Expertise & Book) having a M-2-M identifying relationship; yet the Expertise table has a composite primary key, which involves the join table having also 3 primary keys. Hibernate seems to be unable to handle this kind of join tables as it expects only 2 primary key columns and hence fires the following exception error message: "org.hibernate.AnnotationException: A Foreign key refering org.otika.prototype.model.Expertise from org.otika.prototype.model.Book has the wrong number of column. should be 2". I would probably test this use case againt JPA through EclipseLink and check whether the same error is reproduced, since I am not sure whether it's Hibernate core or forge scaffolfing being responsible of that issue! > 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: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final, 1.3.0.Final > Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1 > Reporter: Hanine Hanynowsky > Assignee: Vineet Reynolds > Fix For: 1.x Future > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1290) Split PersistenceFacet into JPA 2.0 and JPA 2.1 facets

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1290?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1290. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta1 (was: 2.x Future) Resolution: Done > Split PersistenceFacet into JPA 2.0 and JPA 2.1 facets > ------------------------------------------------------ > > Key: FORGE-1290 > URL: https://issues.jboss.org/browse/FORGE-1290 > Project: Forge > Issue Type: Enhancement > Components: Java EE APIs > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta1 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1292) JPA Setup Wizard should allow configuring unit properties

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1292: -------------------------------------- Summary: JPA Setup Wizard should allow configuring unit properties Key: FORGE-1292 URL: https://issues.jboss.org/browse/FORGE-1292 Project: Forge Issue Type: Feature Request Components: Java EE APIs Affects Versions: 2.0.0.Alpha14 Reporter: George Gastaldi Fix For: 2.x Future The JPA Setup wizard should allow the configuration of Persistence unit Properties -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1291) Create Faces commands to create/register new PhaseListener objects

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1291: ----------------------------------------- Summary: Create Faces commands to create/register new PhaseListener objects Key: FORGE-1291 URL: https://issues.jboss.org/browse/FORGE-1291 Project: Forge Issue Type: Feature Request Components: Builtin Plugins, Java EE APIs Affects Versions: 2.0.0.Alpha14 Reporter: Lincoln Baxter III Fix For: 2.x Future -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1290) Split PersistenceFacet into JPA 2.0 and JPA 2.1 facets

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1290: -------------------------------------- Summary: Split PersistenceFacet into JPA 2.0 and JPA 2.1 facets Key: FORGE-1290 URL: https://issues.jboss.org/browse/FORGE-1290 Project: Forge Issue Type: Enhancement Components: Java EE APIs Affects Versions: 2.0.0.Alpha14 Reporter: George Gastaldi Fix For: 2.x Future -- 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2013