November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-982) Rework the Query By Example widget in the Faces scaffold to use String based search criteria for fields with primitive types

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-982?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-982: ------------------------------------- Fix Version/s: 2.x Future > Rework the Query By Example widget in the Faces scaffold to use String based search criteria for fields with primitive types > ---------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-982 > URL: https://issues.jboss.org/browse/FORGE-982 > Project: Forge > Issue Type: Task > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > As seen in FORGE-910 and FORGE-981, String based search criteria should be used for primitive fields. This will avoid the type coercion issues that are specific to JSF input fields backed by primitive types. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1000) Forge scaffold should allow newly created un-persisted instances to be associated with each other in the views

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1000?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1000: -------------------------------------- Fix Version/s: 2.x Future > Forge scaffold should allow newly created un-persisted instances to be associated with each other in the views > -------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1000 > URL: https://issues.jboss.org/browse/FORGE-1000 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > This is from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2]. > In the create stores screen, we have new Staff that can be added to a store, as well as a manager (another Staff) that can be assigned to a store. The manager to be assigned to the store is not nullable (and is required to be provided when creating/editing a store; see FORGE-999). When no Staff has been created yet, the list of staff that can be assigned as a manager is empty, thus making it impossible to create a new Store without modifying the scaffold. > This could be improved by allowing new Staff to be created in the Create Stores screen, and allowing the newly created but un-persisted Staff to be assigned as Managers to the Store. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1011. ------------------------------------- Resolution: Done > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Plugin API > Affects Versions: 1.3.2.Final, 1.3.3.Final > Reporter: Lennart Jörelid > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha14 > > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1011: -------------------------------------- Fix Version/s: 2.0.0.Alpha14 > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Plugin API > Affects Versions: 1.3.2.Final, 1.3.3.Final > Reporter: Lennart Jörelid > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha14 > > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-1011: --------------------------------------- Assignee: Lincoln Baxter III > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Plugin API > Affects Versions: 1.3.2.Final, 1.3.3.Final > Reporter: Lennart Jörelid > Assignee: Lincoln Baxter III > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1011. ------------------------------------- Resolution: Won't Fix Due to the fact that Forge 1 is in feature lockdown, and Forge 2 inherently resolves these issues, I am closing this issue. > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Plugin API > Affects Versions: 1.3.2.Final, 1.3.3.Final > Reporter: Lennart Jörelid > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 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

1
0
0 / 0

[JBoss JIRA] (FORGE-981) The generated Faces scaffold ignores the search criteria in certain cases for primitive numerical types

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-981?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-981: ------------------------------------- Fix Version/s: 2.x Future > The generated Faces scaffold ignores the search criteria in certain cases for primitive numerical types > ------------------------------------------------------------------------------------------------------- > > Key: FORGE-981 > URL: https://issues.jboss.org/browse/FORGE-981 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > The Faces scaffold treats numerical search criteria as absent if the value is 0. Hence, one cannot search explicitly for this value, since this criteria will be ignored during construction of the search predicates. Searches for 0 will result in all values being returned. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-998) xml-parser: Ability to insert an xml node after or before another one

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-998?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-998: ------------------------------------- Fix Version/s: 2.x Future > xml-parser: Ability to insert an xml node after or before another one > --------------------------------------------------------------------- > > Key: FORGE-998 > URL: https://issues.jboss.org/browse/FORGE-998 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.3.2.Final, 2.0.0.Alpha6 > Reporter: Yann Albou > Fix For: 2.x Future > > > Ability to insert an xml node after or before another one. > For instance in the web.xml file when we want to add a new servlet + servlet-mapping nodes -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1002) Faces scaffold should treat properties lacking suitable converters differently

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1002?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1002: -------------------------------------- Fix Version/s: 2.x Future > Faces scaffold should treat properties lacking suitable converters differently > ------------------------------------------------------------------------------ > > Key: FORGE-1002 > URL: https://issues.jboss.org/browse/FORGE-1002 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > This is from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2]. > The {{Staff}} JPA entity generated using the Forge Hibernate Tools plugin, contains a {{byte[]}} property in the form of a {{picture}}. The property is rendered as a {{h:inputText}} widget in the create/edit screens and as a {{h:outputText}} widget in the view screen. This results in errors like the following being reported during operations in such screens: {{Conversion Error setting value '' for 'null Converter'.}} > Since a default converter cannot be applied, mostly due to the possibility of changing semantics of such properties across applications, it would be better to > * either omit such properties for functional scaffolds, > * or generate converters for every such type. > * or use more appropriate widgets (like a file upload widget) that can operate on such data types. > Also see the TicketMonster model, where a {{long[][]}} property is present in the {{SectionAllocation}} entity. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1020) Create a documentation plan and outline for Forge 2

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1020?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1020: -------------------------------------- Fix Version/s: 2.x Future > Create a documentation plan and outline for Forge 2 > --------------------------------------------------- > > Key: FORGE-1020 > URL: https://issues.jboss.org/browse/FORGE-1020 > Project: Forge > Issue Type: Sub-task > Components: Documentation > Affects Versions: 2.0.0.Alpha6 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Similar to the following: > https://docs.google.com/document/d/17B03_n1OpsdEcqnmha0ch13xjz1pikiEagLgk... -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013