July 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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on FORGE-974: ----------------------------------------------- Vineet Reynolds <vpereira(a)redhat.com> changed the Status of [bug 978076|https://bugzilla.redhat.com/show_bug.cgi?id=978076] from NEW to CLOSED > 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 > Priority: Critical > > 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on FORGE-914: ----------------------------------------------- Vineet Reynolds <vpereira(a)redhat.com> changed the Status of [bug 977956|https://bugzilla.redhat.com/show_bug.cgi?id=977956] from NEW to CLOSED > Rework the handling of 1:M relationships by the Faces/RichFaces scaffold > ------------------------------------------------------------------------ > > Key: FORGE-914 > URL: https://issues.jboss.org/browse/FORGE-914 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > Fix For: 1.x Future > > > The generated Faces scaffold for 1:M relationships does not handle certain usability aspects. > For example, a new row is automatically added by default when displaying a 1:M relationship upon create. However, unless the add button is clicked, the contents of the row are not added to the underlying managed bean. If the add button is not clicked, the contents of the row are not treated as a new item to be added. This is very confusing. > Also, if bean validation is performed on the entities (in the rows of the 1:M relationship), and if it fails, then the contents need to be corrected, even though they may not be persisted in the database. Again, this is confusing behavior. > Additionally, deletion of entities from the collection (1-side of the association) seems to be broken (FORGE-974). -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-990) Upgrade to Arquillian 1.1.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-990?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-990. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Alpha7 (was: 2.x Future) Resolution: Done > Upgrade to Arquillian 1.1.0.Final > --------------------------------- > > Key: FORGE-990 > URL: https://issues.jboss.org/browse/FORGE-990 > Project: Forge > Issue Type: Component Upgrade > Components: Test Harness > Affects Versions: 2.0.0.Alpha6 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha7 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-803) Promote usage of ShrinkWrap Resolver instead of using Aether directly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-803?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-803. --------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Deferred Since Forge 2 uses Maven 3.1.0 + Eclipse Aether due to major perfomance increase, this should only happen when ShrinkWrap Resolver changes the implementation to be the same. > Promote usage of ShrinkWrap Resolver instead of using Aether directly > --------------------------------------------------------------------- > > Key: FORGE-803 > URL: https://issues.jboss.org/browse/FORGE-803 > Project: Forge > Issue Type: Enhancement > Components: Build Tools - Maven > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > > The MavenDependencyResolver should use ShrinkWrap Resolver APIs instead of using the Aether APIs directly. > This is believed to bring some performance enhancements also, due to internal improvements in the latest version of SWR. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-554?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-554: ---------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final (was: 1.x Future) Resolution: Done Pushed upstream: https://github.com/forge/core/commit/4d643cff5f60071dca160d5c615fef3815c3... > Tab AutoCompletion in forge ignores already typed options > --------------------------------------------------------- > > Key: FORGE-554 > URL: https://issues.jboss.org/browse/FORGE-554 > Project: Forge > Issue Type: Bug > Components: UI - Shell, Usability, Windows > Environment: Windows 7 64bits > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-791) Forge auto complete in windows doesn't display command until after I forge again

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-791?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-791: ---------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final (was: 1.x Future) Resolution: Done Pushed upstream: https://github.com/forge/core/commit/27a7a77deb763fbc075f9c4743c5482cee86... > Forge auto complete in windows doesn't display command until after I forge again > -------------------------------------------------------------------------------- > > Key: FORGE-791 > URL: https://issues.jboss.org/browse/FORGE-791 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > If I attempt to type in "sp" then tab, the screen fills with some blanks, then tells me the command was not filled in properly. So it identified the command I wanted, but didn't show it on the screen. > {code} > [ooph] ooph $ sp ^C > spartajs.io > ***ERROR*** [spartajs.io] Missing command for plugin [spartajs.io], available commands: [addRestResource, addJackson, remove, setup, add, javascriptModel] > [ooph] ooph $ > [ooph] ooph $ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 1.2.1.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > {code} > After hitting forge again it does auto complete properly. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-942) CommandHistory / Doskey display is not working in Windows.

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-942?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-942: ---------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final (was: 1.x Future) Resolution: Done Pushed upstream: https://github.com/forge/core/commit/27a7a77deb763fbc075f9c4743c5482cee86... > CommandHistory / Doskey display is not working in Windows. > ---------------------------------------------------------- > > Key: FORGE-942 > URL: https://issues.jboss.org/browse/FORGE-942 > Project: Forge > Issue Type: Bug > Components: Windows > Affects Versions: 1.3.0.Final > Environment: Windows XP, java version "1.7.0_21", Forge 1.3.0-Final > Reporter: Rajmahendra Hegde > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > When I try to use Forege in command prompt in Windows, After executing couple of forge commands and try to use arrow key Up and Down. I cant see the command history. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1012) Forge occassionally requires an additional keystroke to be terminated

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1012?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1012: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/345a0e87f143d444f7c6e8df8df4a2f3387c... > Forge occassionally requires an additional keystroke to be terminated > --------------------------------------------------------------------- > > Key: FORGE-1012 > URL: https://issues.jboss.org/browse/FORGE-1012 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: 1.3.4.Final > > > This is related to the behavior described in FORGE-593. In that bug, a keystroke consumed by Forge was lost due to the blocking thread. The bugfix for that issue did not involve any fixes around the blocking read on System.in. > Hence, the reader thread continues to block when reading System.in, thus requiring users to send another keystroke (again to be consumed by the blocking reader) on exiting Forge (since the reader operates in a non-daemon thread). -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-606) Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-606?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-606: ---------------------------------- Priority: Critical (was: Major) > Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities > ---------------------------------------------------------------------------------------------- > > Key: FORGE-606 > URL: https://issues.jboss.org/browse/FORGE-606 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: Vineet Reynolds > Priority: Critical > Fix For: 1.x Future > > > Currently the REST plugin generates broken endpoints if there are cyclic references in the JPA entities. Forge should provide a plugin to hep the developer resolve these references to get past this bump in the road. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-914: ---------------------------------- Priority: Critical (was: Major) > Rework the handling of 1:M relationships by the Faces/RichFaces scaffold > ------------------------------------------------------------------------ > > Key: FORGE-914 > URL: https://issues.jboss.org/browse/FORGE-914 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > Fix For: 1.x Future > > > The generated Faces scaffold for 1:M relationships does not handle certain usability aspects. > For example, a new row is automatically added by default when displaying a 1:M relationship upon create. However, unless the add button is clicked, the contents of the row are not added to the underlying managed bean. If the add button is not clicked, the contents of the row are not treated as a new item to be added. This is very confusing. > Also, if bean validation is performed on the entities (in the rows of the 1:M relationship), and if it fails, then the contents need to be corrected, even though they may not be persisted in the database. Again, this is confusing behavior. > Additionally, deletion of entities from the collection (1-side of the association) seems to be broken (FORGE-974). -- 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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013