September 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1187) UIInput<Boolean>.getValue() should not return null

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1187?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1187: ----------------------------------- Description: It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances. The default being false, unless of course it was specified in the UIInput definition. (was: It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances. The default being false, unless of course it was specified by in the UIInput definition.) > UIInput<Boolean>.getValue() should not return null > -------------------------------------------------- > > Key: FORGE-1187 > URL: https://issues.jboss.org/browse/FORGE-1187 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Reporter: Vineet Reynolds > Priority: Minor > Fix For: 2.x Future > > > It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances. The default being false, unless of course it was specified in the UIInput definition. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1187) UIInput<Boolean>.getValue() should not return null

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1187?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1187: ----------------------------------- Description: It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances. The default being false, unless of course it was specified by in the UIInput definition. (was: It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances.) > UIInput<Boolean>.getValue() should not return null > -------------------------------------------------- > > Key: FORGE-1187 > URL: https://issues.jboss.org/browse/FORGE-1187 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Reporter: Vineet Reynolds > Priority: Minor > Fix For: 2.x Future > > > It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances. The default being false, unless of course it was specified by in the UIInput definition. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1187) UIInput<Boolean>.getValue() should not return null

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1187: -------------------------------------- Summary: UIInput<Boolean>.getValue() should not return null Key: FORGE-1187 URL: https://issues.jboss.org/browse/FORGE-1187 Project: Forge Issue Type: Feature Request Components: UI - API Reporter: Vineet Reynolds Priority: Minor Fix For: 2.x Future It would be ideal to return a binary value, instead of having this as a tri-state variable leading to addon developers adding in null checks. Perhaps it would be better to automatically set the defaultValue of UIInput<Boolean> instances. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1186) Provide a test API for testing UICommands

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1186: -------------------------------------- Summary: Provide a test API for testing UICommands Key: FORGE-1186 URL: https://issues.jboss.org/browse/FORGE-1186 Project: Forge Issue Type: Feature Request Components: Test Harness Reporter: Vineet Reynolds Fix For: 2.x Future Similar to the WizardTester API that tests UIWizards, we'll need one for UICommands. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1102) Support detection/registration/installation of undeclared dependent facets

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1102?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1102. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Alpha12 (was: 2.x Future) Resolution: Done Done. Breaks Facets API. > Support detection/registration/installation of undeclared dependent facets > -------------------------------------------------------------------------- > > Key: FORGE-1102 > URL: https://issues.jboss.org/browse/FORGE-1102 > Project: Forge > Issue Type: Feature Request > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha12 > > > Based on FORGE-1101, facets that are not declared via {{@RequiresFacet}} may not be visible via {{Project.hasFacet()}} at the right time since the {{ProjectFactory}}'s registry may not process these facets in the right order. It would be a good idea to hint the {{ProjectFactory}} that a particular Facet may have to be registered. > To explain further, the {{RestFacet}} does not declare any dependencies on the {{RestWebXmlFacet}} and the {{RestApplicationFacet}}. These facets are therefore not always detected via the {{project.hasFacet()}} invocations. > Declaring them as facets via a {{@RequiresOnlyOneFacet}} annotation could be one solution to ensure that only one facet within a group should be sufficient to satisfy the desired constraints on a Faceted type. Likewise, we could also add support for optional facets that are may be installed if possible, via a {{@OptionalFacets}} annotation. > This would probably be better supported in 2.x instead of 1.x. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1185) Create XML parser addon

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1185: -------------------------------------- Summary: Create XML parser addon Key: FORGE-1185 URL: https://issues.jboss.org/browse/FORGE-1185 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.0.0.Alpha11 Reporter: George Gastaldi Fix For: 2.x Future Should use forge xml-parser -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1173) Port the JSF commands

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1173?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1173: -------------------------------------- Assignee: George Gastaldi > Port the JSF commands > --------------------- > > Key: FORGE-1173 > URL: https://issues.jboss.org/browse/FORGE-1173 > Project: Forge > Issue Type: Sub-task > Components: Builtin Plugins > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > Commands in Forge 1: > * faces setup > * faces project-stage > * faces <default_command> > * faces new-view -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1148) Support multi-level UIWizard flows.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1148?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1148. ------------------------------------- Resolution: Done > Support multi-level UIWizard flows. > ----------------------------------- > > Key: FORGE-1148 > URL: https://issues.jboss.org/browse/FORGE-1148 > Project: Forge > Issue Type: Feature Request > Components: UI - API, UI - Eclipse, UI - Shell > Affects Versions: 2.0.0.Alpha11 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Labels: difficult > Fix For: 2.0.0.Alpha12 > > Attachments: Screen Shot 2013-08-30 at 3.02.14 PM.png > > > Say for instance I want to create a new entity, but persistence is not set up. I should have the choice to set up persistence, say, via a checkbox. > but once persistence is set up, then I should be directed to add a new field, for instance. So the flow is this: > 1. New Entity > 2. Persistence Setup (Container Selection, Provider Selection) > 3. New Field > This means that persistence setup executes in a sub-flow that must return to the next designated step of the original flow when complete. > {code}return Results.navigate(PersistenceSetup.class, NewField.class){code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1148) Support multi-level UIWizard flows.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1148?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1148: -------------------------------------- Issue Type: Feature Request (was: Bug) > Support multi-level UIWizard flows. > ----------------------------------- > > Key: FORGE-1148 > URL: https://issues.jboss.org/browse/FORGE-1148 > Project: Forge > Issue Type: Feature Request > Components: UI - API, UI - Eclipse, UI - Shell > Affects Versions: 2.0.0.Alpha11 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Labels: difficult > Fix For: 2.0.0.Alpha12 > > Attachments: Screen Shot 2013-08-30 at 3.02.14 PM.png > > > Say for instance I want to create a new entity, but persistence is not set up. I should have the choice to set up persistence, say, via a checkbox. > but once persistence is set up, then I should be directed to add a new field, for instance. So the flow is this: > 1. New Entity > 2. Persistence Setup (Container Selection, Provider Selection) > 3. New Field > This means that persistence setup executes in a sub-flow that must return to the next designated step of the original flow when complete. > {code}return Results.navigate(PersistenceSetup.class, NewField.class){code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1148) Support multi-level UIWizard flows.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1148?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-1148: --------------------------------------- > Support multi-level UIWizard flows. > ----------------------------------- > > Key: FORGE-1148 > URL: https://issues.jboss.org/browse/FORGE-1148 > Project: Forge > Issue Type: Bug > Components: UI - API, UI - Eclipse, UI - Shell > Affects Versions: 2.0.0.Alpha11 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Labels: difficult > Fix For: 2.0.0.Alpha12 > > Attachments: Screen Shot 2013-08-30 at 3.02.14 PM.png > > > Say for instance I want to create a new entity, but persistence is not set up. I should have the choice to set up persistence, say, via a checkbox. > but once persistence is set up, then I should be directed to add a new field, for instance. So the flow is this: > 1. New Entity > 2. Persistence Setup (Container Selection, Provider Selection) > 3. New Field > This means that persistence setup executes in a sub-flow that must return to the next designated step of the original flow when complete. > {code}return Results.navigate(PersistenceSetup.class, NewField.class){code} -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2013