June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-974: --------------------------------------- Some technical details: Collection members of an entity are displayed in a datatable. When an item is deleted from this table, it is deleted from the underlying collection through an EL expression: {noformat} #{_collection.remove(_item)} {noformat} This EL expression is not aware of the participation of the collection in a bi-directional relationship. When the composing entity is merged back into the persistence context, any deletions of instances from the collection are not recorded since they need to be done on both sides. > Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-974 > URL: https://issues.jboss.org/browse/FORGE-974 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. > This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. > Addition of members to the collection property are however performed correctly. Since the Faces scaffold does not allow updates to properties of the the individual members in the collection, no other issue is observed, except for the inability to update the collection state correctly. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-974: ---------------------------------- Description: The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. Addition of members to the collection property are however performed correctly. Since the Faces scaffold does not allow updates to properties of the the individual members in the collection, no other issue is observed, except for the inability to update the collection state correctly. was: The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. > Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-974 > URL: https://issues.jboss.org/browse/FORGE-974 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. > This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. > Addition of members to the collection property are however performed correctly. Since the Faces scaffold does not allow updates to properties of the the individual members in the collection, no other issue is observed, except for the inability to update the collection state correctly. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-974: ---------------------------------- Summary: Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity (was: Faces scaffolding does not correctly update collection members involved in bi-directional relationships) > Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-974 > URL: https://issues.jboss.org/browse/FORGE-974 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: Vineet Reynolds > > The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. > This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-974: ------------------------------------- Assignee: Vineet Reynolds > Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-974 > URL: https://issues.jboss.org/browse/FORGE-974 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. > This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-974: ------------------------------------- Summary: Faces scaffolding does not correctly update collection members involved in bi-directional relationships Key: FORGE-974 URL: https://issues.jboss.org/browse/FORGE-974 Project: Forge Issue Type: Bug Components: Scaffold Affects Versions: 1.3.1.Final Reporter: Vineet Reynolds The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-440: ------------------------------------------ Hey Lennart! I'd love to show you around the code. You can find the maven POM stuff here, but as you can see, unfortunately it's not very ... open for extension: https://github.com/forge/core/blob/2.0/maven/impl-projects/src/main/java/... However, the thought came to my mind, that m2eclipse must be supporting this somehow, so we should see what they do and find out if it can be re-used. Otherwise we'll need to re-implement this functionality using the Forge XML Parser, which would be... a shame to have to do. I'd love to get this solved. What do you think? ~Lincoln > A pom.xml which contains comments loses all of them after Forge operates on it. > ------------------------------------------------------------------------------- > > Key: FORGE-440 > URL: https://issues.jboss.org/browse/FORGE-440 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.0.6.Final > Environment: HEAD > Reporter: Pete Muir > Fix For: 2.x Future > > > Also looses formatting, but this is less of an 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-926) It should be : maxlength instead of maxLength

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-926?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-926: ---------------------------------- Assignee: Vineet Reynolds > It should be : maxlength instead of maxLength > --------------------------------------------- > > Key: FORGE-926 > URL: https://issues.jboss.org/browse/FORGE-926 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.0.Final, 1.2.1.Final, 1.2.2.Final, 1.3.0.Final > Environment: Any > Reporter: Hanine Hanynowsky > Assignee: Vineet Reynolds > Priority: Minor > Fix For: 1.3.3.Final > > > The JBoss Forge UI scaffold uses maxLength as the attribute name instead of maxlength, when generating <h:inpuText /> components, in .xhtml files. > So this is a typo error (capital L instead of a lowercase l). > People using Eclipse or JBoss developer might notice it since, these IDEs do not complain about it. If you use Netbeans or IntelliJidea, you would be prompted to correct the error. > This has no critical consequences so far, but should be changed to correct name. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-926) It should be : maxlength instead of maxLength

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-926?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-926: ---------------------------------- Fix Version/s: 1.3.3.Final (was: 1.x Future) > It should be : maxlength instead of maxLength > --------------------------------------------- > > Key: FORGE-926 > URL: https://issues.jboss.org/browse/FORGE-926 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.0.Final, 1.2.1.Final, 1.2.2.Final, 1.3.0.Final > Environment: Any > Reporter: Hanine Hanynowsky > Priority: Minor > Fix For: 1.3.3.Final > > > The JBoss Forge UI scaffold uses maxLength as the attribute name instead of maxlength, when generating <h:inpuText /> components, in .xhtml files. > So this is a typo error (capital L instead of a lowercase l). > People using Eclipse or JBoss developer might notice it since, these IDEs do not complain about it. If you use Netbeans or IntelliJidea, you would be prompted to correct the error. > This has no critical consequences so far, but should be changed to correct name. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-973) Upgrade Metawidget to 3.4

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-973?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-973: ---------------------------------- Fix Version/s: 1.3.3.Final (was: 1.3.2.Final) > Upgrade Metawidget to 3.4 > ------------------------- > > Key: FORGE-973 > URL: https://issues.jboss.org/browse/FORGE-973 > Project: Forge > Issue Type: Component Upgrade > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.3.3.Final > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-973) Upgrade Metawidget to 3.4

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-973?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-973: ------------------------------------- Assignee: Vineet Reynolds (was: George Gastaldi) As requested. > Upgrade Metawidget to 3.4 > ------------------------- > > Key: FORGE-973 > URL: https://issues.jboss.org/browse/FORGE-973 > Project: Forge > Issue Type: Component Upgrade > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.3.2.Final > > -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013