February 2014 - 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 closed FORGE-368. --------------------------------- Closing this issue as duplicated from FORGE-1342 > 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: 2.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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-933) Expose the ForgePropertyStyle methods as an API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-933?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-933. --------------------------------- Fix Version/s: (was: 1.x Future) Resolution: Duplicate Issue Implemented in FORGE-1342 > Expose the ForgePropertyStyle methods as an API > ----------------------------------------------- > > Key: FORGE-933 > URL: https://issues.jboss.org/browse/FORGE-933 > Project: Forge > Issue Type: Sub-task > Components: Parsers / File Manipulation > Reporter: Alceu Medeiros > > As mentioned in IRC channel with development team, it would be nice if we have the ForgePropertyStyle methods as an API, to retrieve getter/setter methods from Fields, among other project higher-level properties. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1591) Not possible to exit shell using ctrl-d

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1591?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1591. ---------------------------------- Assignee: Ståle Pedersen Resolution: Done Thanks. Closing it > Not possible to exit shell using ctrl-d > --------------------------------------- > > Key: FORGE-1591 > URL: https://issues.jboss.org/browse/FORGE-1591 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Ståle Pedersen > Assignee: Ståle Pedersen > Fix For: 2.0.1.Final > > > Currently the InterruptHandler do not trigger forge to quit when ignoreeof threshold is triggered. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1591) Not possible to exit shell using ctrl-d

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1591?page=com.atlassian.jira.plugin... ] Ståle Pedersen updated FORGE-1591: ---------------------------------- Fix Version/s: 2.0.1.Final (was: 2.x Future) > Not possible to exit shell using ctrl-d > --------------------------------------- > > Key: FORGE-1591 > URL: https://issues.jboss.org/browse/FORGE-1591 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Ståle Pedersen > Fix For: 2.0.1.Final > > > Currently the InterruptHandler do not trigger forge to quit when ignoreeof threshold is triggered. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1591) Not possible to exit shell using ctrl-d

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1591?page=com.atlassian.jira.plugin... ] Ståle Pedersen commented on FORGE-1591: --------------------------------------- yup, it is. > Not possible to exit shell using ctrl-d > --------------------------------------- > > Key: FORGE-1591 > URL: https://issues.jboss.org/browse/FORGE-1591 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Ståle Pedersen > Fix For: 2.0.1.Final > > > Currently the InterruptHandler do not trigger forge to quit when ignoreeof threshold is triggered. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1591) Not possible to exit shell using ctrl-d

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1591?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1591: ---------------------------------------- I think this is already implemented? > Not possible to exit shell using ctrl-d > --------------------------------------- > > Key: FORGE-1591 > URL: https://issues.jboss.org/browse/FORGE-1591 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Ståle Pedersen > Fix For: 2.x Future > > > Currently the InterruptHandler do not trigger forge to quit when ignoreeof threshold is triggered. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1591) Not possible to exit shell using ctrl-d

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1591?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1591: -------------------------------------- Fix Version/s: 2.x Future > Not possible to exit shell using ctrl-d > --------------------------------------- > > Key: FORGE-1591 > URL: https://issues.jboss.org/browse/FORGE-1591 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Ståle Pedersen > Fix For: 2.x Future > > > Currently the InterruptHandler do not trigger forge to quit when ignoreeof threshold is triggered. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1593) Being able to create our own JSF artifacts

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1593?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1593: ------------------------------------------ Check the sub-tasks and let me know if you need more indeepth example > Being able to create our own JSF artifacts > ------------------------------------------ > > Key: FORGE-1593 > URL: https://issues.jboss.org/browse/FORGE-1593 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1595) Being able to create an empty JSF backing bean

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1595: ---------------------------------------- Summary: Being able to create an empty JSF backing bean Key: FORGE-1595 URL: https://issues.jboss.org/browse/FORGE-1595 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Priority: Minor Fix For: 2.x Future At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such : {code} faces-new-bean --named MyBean {code} This will create a {{MyBean}}, of scope request, under the {{view}} package. You could also give a different sub-package with : {code} faces-new-page --named MyBean --targetPackage view.admin {code} This will create the page under {{view/admin/MyBean.java}}. {code} @Named @RequestScoped public class MyBean { } {code} Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes) {code} faces-new-bean --named MyBean --scoped Conversation {code} This would generate the following code {code} @Named @ConversationScoped public class MyBean implements Serializable { @Inject private Conversation conversation; public String begin() { conversation.begin(); } public String end() { conversation.end(); } } {code} PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1594) Being able to create an empty JSF page

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1594: ---------------------------------------- Summary: Being able to create an empty JSF page Key: FORGE-1594 URL: https://issues.jboss.org/browse/FORGE-1594 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Priority: Minor Fix For: 2.x Future At the moment the only way to generate JSF pages is with scaffolding. When you create an application, you realize that these scaffolded pages are not enough and that you need to create new ones. To save time and help the developer in creating new pages, it would be good to have a command such : {code} faces-new-page --named mypage {code} This will create a mypage.xhtml on the root of the webapp directory. You could also give a different directory with : {code} faces-new-page --named mypage --targetDirectory admin {code} This will create the page under webapp/admin/mypage.xhtml. {code} <?xml version='1.0' encoding='UTF-8' ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://xmlns.jcp.org/jsf/html" xmlns:f="http://xmlns.jcp.org/jsf/core" xmlns:ui="http://xmlns.jcp.org/jsf/facelets" template="/resources/scaffold/pageTemplate.xhtml"> <ui:param name="pageTitle" value="mypage"/> <ui:define name="header"> mypage </ui:define> <ui:define name="subheader"> mypage </ui:define> <ui:define name="footer"/> <ui:define name="main"> </ui:define> </ui:composition> {code} The name of the page {{mypage}} is used for the title, header, subheader. But we could customize this using optional attributes for title, header, subheader : {code} faces-new-page --named mypage --targetDirectory admin --title Administration Page --header Admin Header --subheader Admin Sub Header {code} It would just create a minimum JSF page such as : {code} <?xml version='1.0' encoding='UTF-8' ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://xmlns.jcp.org/jsf/html" xmlns:f="http://xmlns.jcp.org/jsf/core" xmlns:ui="http://xmlns.jcp.org/jsf/facelets" template="/resources/scaffold/pageTemplate.xhtml"> <ui:param name="pageTitle" value="Administration Page"/> <ui:define name="header"> Admin Header </ui:define> <ui:define name="subheader"> Admin Sub Header </ui:define> <ui:define name="footer"/> <ui:define name="main"> </ui:define> </ui:composition> {code} PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014