June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-368) Return list of properties based on higher-level understanding

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-368?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-368: ---------------------------------- Fix Version/s: 1.x Future (was: 2.0.0.Alpha5) > Return list of properties based on higher-level understanding > ------------------------------------------------------------- > > Key: FORGE-368 > URL: https://issues.jboss.org/browse/FORGE-368 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Richard Kennard > Fix For: 1.x Future > > > Hi guys, > As I understand it, Forge has an understanding of your project that transcends Java's own understanding. So for example if I say... > field string --named foo > ...Forge knows I'm creating a property, and it creates getters and setters for that property. But later if I do... > org.jboss.forge.parser.java.JavaClass.getMethods() > ...then I get back just normal methods. I'll have to check their signature for 'get' or 'set' to see if they're properties. Equally if I do... > org.jboss.forge.parser.java.JavaClass.getFields() > ...I get back just normal fields. I don't know if these are property fields (and if so, what their corresponding getter/setter methods are) or whether they're just internal fields (and should be ignored). > Is there a recommended way to 'get back out' the list of properties for a class? Something that tells me a) the field; b) the getter; c) the setter? > If it helps, for now I am using a rough implementation at: https://github.com/kennardconsulting/forge/blob/master/scaffold-metawidge... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-286) Forge needs a de-centralized plugin distribution and repository system

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-286?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-286: ---------------------------------- Fix Version/s: 1.x Future (was: 1.0.0.Beta1) > Forge needs a de-centralized plugin distribution and repository system > ---------------------------------------------------------------------- > > Key: FORGE-286 > URL: https://issues.jboss.org/browse/FORGE-286 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Plugin API > Affects Versions: 1.0.0.Alpha1 > Environment: All > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Priority: Critical > Labels: Maven > Fix For: 1.x Future > > > There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven. > Features Forge would need to provide: > 1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity > ------------------------------------------------------------------------------------------ > $ forge plugin-find prettyfaces > Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts. > * http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1] > * http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0 > $ forge plugin-install prettyfaces --version 3.1.0 > ***SUCCESS*** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes. > $ forge plugin-list > Listing installed plugins: > * prettyfaces [3.1.0] > * forge-scaffold [1.0.0.Alpha1] > * forge-javaee6 [1.0.0.Alpha1] > * home-control [1.0.0.Alpha1] > $ forge plugin-remove prettyfaces > Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y > ***SUCCESS*** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes. > ------------------------------------------------------------------------------------------ > 2) Plugin repository management (add/remove/edit/list current plugin repository targets.) > ------------------------------------------------------------------------------------------ > $ forge repo-list > Currently using the following plugin repositories: > * 1. https://repository.jboss.org/nexus/content/groups/public/ > * 2. http://ocpsoft.com/repository > * 3. http://example.com/forge/plugin-repository > $ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen > $ forge repo-add http://javaee.org/forge/repository/ > $ forge repo-list > Currently using the following plugin repositories: > * 1. https://repository.jboss.org/nexus/content/groups/public/ > * 2. http://ocpsoft.com/repository > * 3. http://example.com/forge/plugin-repository > * 4. http://jboss.org/forge/repository/ > * 5. http://javaee.org/forge/repository/ > $ forge repo-del 5 > ***SUCCESS*** removed repository [http://javaee.org/forge/repository/]. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove {plugin-id}] > ------------------------------------------------------------------------------------------ > 3) Auto-update functionality > Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins. > 4) A meta-data system of identifying compatible versions of plugins w/running version of forge. > Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-893) UIInput<?> should support setValidator(UIIInputValidator) getValidator() for input-level-validation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-893?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-893: ---------------------------------- Fix Version/s: 2.x Future > UIInput<?> should support setValidator(UIIInputValidator) getValidator() for input-level-validation > --------------------------------------------------------------------------------------------------- > > Key: FORGE-893 > URL: https://issues.jboss.org/browse/FORGE-893 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse, UI - IntelliJ IDEA, UI - Shell > Affects Versions: 2.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Currently Forge 2 UI API supports command-level validation, but we don't support field-level validation, which would be useful for dev simplification/ease of use. > This may or may not be able to live on the base InputComponent interface, but more likely it will need to be customized for each of UISelectOne, UISelectMany, UIInput, and UIInputMany types. > {code} > public interface InputComponent<IMPLTYPE, VALUETYPE> extends Faceted<HintsFacet> > { > Validator<VALUETYPE> getValidator(); > IMPLTYPE setValidator(Validator<VALUETYPE>); > } > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-932) Add support for UICompleter in the UI API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-932?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-932: ---------------------------------- Fix Version/s: 2.x Future > Add support for UICompleter in the UI API > ----------------------------------------- > > Key: FORGE-932 > URL: https://issues.jboss.org/browse/FORGE-932 > Project: Forge > Issue Type: Enhancement > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha4 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > > UICompleter is defined in the UI API however it is not used anywhere -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-910) In View Beans, Search predicate for boolean fields is not supported

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-910?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-910: ---------------------------------- Fix Version/s: 1.x Future (was: 2.0.0.Beta2) > In View Beans, Search predicate for boolean fields is not supported > ------------------------------------------------------------------- > > Key: FORGE-910 > URL: https://issues.jboss.org/browse/FORGE-910 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final > Environment: Linux 3.8, Firefox. > Reporter: Hanine Hanynowsky > Priority: Minor > Fix For: 1.x Future > > > In View Beans, Search predicate for boolean fields is not supported. > > Jboss Forge generates the View Bean with search support using JPA criteria expressions for fields of type String and Entity objects but it does not for boolean fields. > Is this not supported? A bug? A feature request? Or simply that it's not possible to use boolean fields with JPA predicate isLike & equ -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-697) For Faces scaffold selectOneMenu not working with LAZY properties

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-697?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-697: ---------------------------------- Fix Version/s: 1.x Future (was: 2.x Future) > For Faces scaffold selectOneMenu not working with LAZY properties > ----------------------------------------------------------------- > > Key: FORGE-697 > URL: https://issues.jboss.org/browse/FORGE-697 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.1.1.Final > Environment: JBoss 7.1.1, forge 1.1.1 > Reporter: Esteve Aviles > Priority: Minor > Labels: jpa2 > Fix For: 1.x Future > > > When using JSF scaffold we get the following generated code for @ManyToOne relation: > <h:selectOneMenu converter="#{clubBean.converter}" id="clubFacilityBeanClubFacilityClub" value="#{clubFacilityBean.clubFacility.club}"> > <f:selectItem/> > <f:selectItems value="#{clubBean.all}"/> > </h:selectOneMenu> > When we annotate the property LAZY @ManyToOne(fetch=FetchType.LAZY) the selectOneMenu is not selected with the current value in the create.xhtml file. > Is there any way to solve this situation? > Thanks in advance. > Regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-697) For Faces scaffold selectOneMenu not working with LAZY properties

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-697?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-697: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Beta2) > For Faces scaffold selectOneMenu not working with LAZY properties > ----------------------------------------------------------------- > > Key: FORGE-697 > URL: https://issues.jboss.org/browse/FORGE-697 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.1.1.Final > Environment: JBoss 7.1.1, forge 1.1.1 > Reporter: Esteve Aviles > Priority: Minor > Labels: jpa2 > Fix For: 2.x Future > > > When using JSF scaffold we get the following generated code for @ManyToOne relation: > <h:selectOneMenu converter="#{clubBean.converter}" id="clubFacilityBeanClubFacilityClub" value="#{clubFacilityBean.clubFacility.club}"> > <f:selectItem/> > <f:selectItems value="#{clubBean.all}"/> > </h:selectOneMenu> > When we annotate the property LAZY @ManyToOne(fetch=FetchType.LAZY) the selectOneMenu is not selected with the current value in the create.xhtml file. > Is there any way to solve this situation? > Thanks in advance. > Regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-697) For Faces scaffold selectOneMenu not working with LAZY properties

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-697?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-697: ---------------------------------- Fix Version/s: 2.0.0.Beta2 > For Faces scaffold selectOneMenu not working with LAZY properties > ----------------------------------------------------------------- > > Key: FORGE-697 > URL: https://issues.jboss.org/browse/FORGE-697 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.1.1.Final > Environment: JBoss 7.1.1, forge 1.1.1 > Reporter: Esteve Aviles > Priority: Minor > Labels: jpa2 > Fix For: 2.0.0.Beta2 > > > When using JSF scaffold we get the following generated code for @ManyToOne relation: > <h:selectOneMenu converter="#{clubBean.converter}" id="clubFacilityBeanClubFacilityClub" value="#{clubFacilityBean.clubFacility.club}"> > <f:selectItem/> > <f:selectItems value="#{clubBean.all}"/> > </h:selectOneMenu> > When we annotate the property LAZY @ManyToOne(fetch=FetchType.LAZY) the selectOneMenu is not selected with the current value in the create.xhtml file. > Is there any way to solve this situation? > Thanks in advance. > Regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-910) In View Beans, Search predicate for boolean fields is not supported

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-910?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-910: ---------------------------------- Fix Version/s: 2.0.0.Beta2 > In View Beans, Search predicate for boolean fields is not supported > ------------------------------------------------------------------- > > Key: FORGE-910 > URL: https://issues.jboss.org/browse/FORGE-910 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final > Environment: Linux 3.8, Firefox. > Reporter: Hanine Hanynowsky > Priority: Minor > Fix For: 2.0.0.Beta2 > > > In View Beans, Search predicate for boolean fields is not supported. > > Jboss Forge generates the View Bean with search support using JPA criteria expressions for fields of type String and Entity objects but it does not for boolean fields. > Is this not supported? A bug? A feature request? Or simply that it's not possible to use boolean fields with JPA predicate isLike & equ -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-35) add-constraint is missing NotEmpty

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-35?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-35: --------------------------------- Fix Version/s: (was: Future) > add-constraint is missing NotEmpty > ---------------------------------- > > Key: FORGE-35 > URL: https://issues.jboss.org/browse/FORGE-35 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.6.Final > Reporter: Pete Muir > Assignee: George Gastaldi > Labels: Starter > -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013