February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1576) Generating a transactional layer

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1576?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1576: ------------------------------------- Summary: Generating a transactional layer (was: Adding a transactional layer) > Generating a transactional layer > -------------------------------- > > Key: FORGE-1576 > URL: https://issues.jboss.org/browse/FORGE-1576 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > On my [blog I explain a few architectural styles|http://antoniogoncalves.org/2013/10/29/several-architectural-style...] that can be used in Java EE. JBoss Forge generates REST endoints and JSB backing bean that, both, use a {{EntityManager}} to access the database. > It would be good to have another type of architecture, one with an EJB transactional layer, and both JSF beans and REST endpoints accessing this EJB tier. -- 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-1578) Create command rest-generate-endpoints-from-services

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1578: ---------------------------------------- Summary: Create command rest-generate-endpoints-from-services Key: FORGE-1578 URL: https://issues.jboss.org/browse/FORGE-1578 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future This command would create REST enpoints from a transactional EJB tier. Instead of accessing an {{EntityManager}} (like the {{rest-generate-endpoints-from-entities}} command), the generated REST endpoints would delegate CRUD operations to the EJB tier -- 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-1577) Create command ejb-generate-services-from-entities

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1577: ---------------------------------------- Summary: Create command ejb-generate-services-from-entities Key: FORGE-1577 URL: https://issues.jboss.org/browse/FORGE-1577 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future This command would create an EJB tier from entities. Like today with REST enpoints or JSF beans, this EJB tier would give CRUD operations for each entities -- 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-1576) Adding a transactional layer

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1576: ---------------------------------------- Summary: Adding a transactional layer Key: FORGE-1576 URL: https://issues.jboss.org/browse/FORGE-1576 Project: Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future On my [blog I explain a few architectural styles|http://antoniogoncalves.org/2013/10/29/several-architectural-style...] that can be used in Java EE. JBoss Forge generates REST endoints and JSB backing bean that, both, use a {{EntityManager}} to access the database. It would be good to have another type of architecture, one with an EJB transactional layer, and both JSF beans and REST endpoints accessing this EJB tier. -- 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-1201) getSearchPredicates should use case insensitive search

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1201?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1201: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/383 > getSearchPredicates should use case insensitive search > ------------------------------------------------------ > > Key: FORGE-1201 > URL: https://issues.jboss.org/browse/FORGE-1201 > Project: Forge > Issue Type: Feature Request > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > Hi, > When you do JSF scaffolding, the generated code for research is as follow : > {code} > private Predicate[] getSearchPredicates(Root<Talk> root) { > CriteriaBuilder builder = this.entityManager.getCriteriaBuilder(); > List<Predicate> predicatesList = new ArrayList<>(); > String title = this.example.getTitle(); > if (title != null && !"".equals(title)) { > predicatesList.add(builder.like(root.<String>get("title"), '%' + title + '%')); > } > {code} > The problem with that is the search is case sensitive and searching for "java" or "Java" doesn't bring the same results. It would be more natural to have case insensitive search as follow : > {code} > private Predicate[] getSearchPredicates(Root<Talk> root) { > CriteriaBuilder builder = this.entityManager.getCriteriaBuilder(); > List<Predicate> predicatesList = new ArrayList<>(); > String title = this.example.getTitle(); > if (title != null && !"".equals(title)) { > predicatesList.add(builder.like(builder.lower(root.<String>get("title")), "%" + title.toLowerCase() + "%")); > } > {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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1201) getSearchPredicates should use case insensitive search

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1201?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-1201: ---------------------------------------- Assignee: Antonio Goncalves > getSearchPredicates should use case insensitive search > ------------------------------------------------------ > > Key: FORGE-1201 > URL: https://issues.jboss.org/browse/FORGE-1201 > Project: Forge > Issue Type: Feature Request > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > Hi, > When you do JSF scaffolding, the generated code for research is as follow : > {code} > private Predicate[] getSearchPredicates(Root<Talk> root) { > CriteriaBuilder builder = this.entityManager.getCriteriaBuilder(); > List<Predicate> predicatesList = new ArrayList<>(); > String title = this.example.getTitle(); > if (title != null && !"".equals(title)) { > predicatesList.add(builder.like(root.<String>get("title"), '%' + title + '%')); > } > {code} > The problem with that is the search is case sensitive and searching for "java" or "Java" doesn't bring the same results. It would be more natural to have case insensitive search as follow : > {code} > private Predicate[] getSearchPredicates(Root<Talk> root) { > CriteriaBuilder builder = this.entityManager.getCriteriaBuilder(); > List<Predicate> predicatesList = new ArrayList<>(); > String title = this.example.getTitle(); > if (title != null && !"".equals(title)) { > predicatesList.add(builder.like(builder.lower(root.<String>get("title")), "%" + title.toLowerCase() + "%")); > } > {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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1575) Map Entities and Columns From the Forge Command Line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1575?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1575: ----------------------------------- Fix Version/s: 2.x Future Since Forge 1.x is feature-frozen, this feature should be implemented in Forge 2 > Map Entities and Columns From the Forge Command Line > ---------------------------------------------------- > > Key: FORGE-1575 > URL: https://issues.jboss.org/browse/FORGE-1575 > Project: Forge > Issue Type: Feature Request > Components: Forge Scripting Language > Affects Versions: 1.4.4.Final > Reporter: Larry Wilson > Fix For: 2.x Future > > > As an end user, I would like to be able to create a table or column mapping with the Forge command line. > Our company has standards for the data model that are different than those for the Java layer. > For example, the standard name for the Java POJO TimeZone.java which is mapped to the table named TIME_ZONE. > Ideally, Forge would support: > entity --named TimeZone --tableName TIME_ZONE; > field string --named activeFlag --columnName ACTIVE_FLAG; > This would lend keeping a project as a prototype much longer before stepping away from Forge and manually making these changes. -- 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-1575) Map Entities and Columns From the Forge Command Line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1575?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1575: ----------------------------------- Labels: Starter (was: ) > Map Entities and Columns From the Forge Command Line > ---------------------------------------------------- > > Key: FORGE-1575 > URL: https://issues.jboss.org/browse/FORGE-1575 > Project: Forge > Issue Type: Feature Request > Components: Forge Scripting Language > Affects Versions: 1.4.4.Final > Reporter: Larry Wilson > Labels: Starter > Fix For: 2.x Future > > > As an end user, I would like to be able to create a table or column mapping with the Forge command line. > Our company has standards for the data model that are different than those for the Java layer. > For example, the standard name for the Java POJO TimeZone.java which is mapped to the table named TIME_ZONE. > Ideally, Forge would support: > entity --named TimeZone --tableName TIME_ZONE; > field string --named activeFlag --columnName ACTIVE_FLAG; > This would lend keeping a project as a prototype much longer before stepping away from Forge and manually making these changes. -- 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-1575) Map Entities and Columns From the Forge Command Line

by Larry Wilson (JIRA)

Larry Wilson created FORGE-1575: ----------------------------------- Summary: Map Entities and Columns From the Forge Command Line Key: FORGE-1575 URL: https://issues.jboss.org/browse/FORGE-1575 Project: Forge Issue Type: Feature Request Components: Forge Scripting Language Affects Versions: 1.4.4.Final Reporter: Larry Wilson As an end user, I would like to be able to create a table or column mapping with the Forge command line. Our company has standards for the data model that are different than those for the Java layer. For example, the standard name for the Java POJO TimeZone.java which is mapped to the table named TIME_ZONE. Ideally, Forge would support: entity --named TimeZone --tableName TIME_ZONE; field string --named activeFlag --columnName ACTIVE_FLAG; This would lend keeping a project as a prototype much longer before stepping away from Forge and manually making these changes. -- 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-1479) Explicitly setup in Bean Validation, not in JPA

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1479: -------------------------------------- Assignee: George Gastaldi > Explicitly setup in Bean Validation, not in JPA > ----------------------------------------------- > > Key: FORGE-1479 > URL: https://issues.jboss.org/browse/FORGE-1479 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.x Future > > > Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) : > {code} > ***SUCCESS*** Project named 'test' has been created. > [test]$ jpa-new-entity --named Author > [Author.java]$ jpa-new-field --named firstname --length 50 > ***SUCCESS*** Field firstname created > {code} > This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation : > {code} > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-setup > [Author.java]$ constraint-setup > ***SUCCESS*** Bean Validation is installed. > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-add constraint-setup > [Author.java]$ constraint-add --constraint NotNull --onProperty firstname > ***SUCCESS*** Constraint NotNull successfully configured > {code} > if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following : > {code} > servlet-setup > ejb-setup > soap-setup > cdi-setup > jms-setup > rest-setup > jpa-setup > faces-setup > jstl-setup > jta-setup > constraint-setup > {code} > Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}" > That would save some bugs (developers forgetting to setup things), less typing and shorter scripts. -- 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