January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1422) REST addon should support generation of exception mappers for validation errors

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1422: -------------------------------------- Fix Version/s: 2.x Future > REST addon should support generation of exception mappers for validation errors > ------------------------------------------------------------------------------- > > Key: FORGE-1422 > URL: https://issues.jboss.org/browse/FORGE-1422 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > Currently a HTTP 500 response is generated for validation errors encountered during processing of POST/PUT requests that create or update JPA entities. The 500 response contains a stacktrace that cannot be parsed by clients to evaluate what failed. > We should generate exception mappers that can map Bean validation errors to help generate parseable responses (for the REST clients). -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1361) Control REST resource generation to allow entities to be sent in response to POST request

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1361?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1361: -------------------------------------- Fix Version/s: 2.x Future > Control REST resource generation to allow entities to be sent in response to POST request > ----------------------------------------------------------------------------------------- > > Key: FORGE-1361 > URL: https://issues.jboss.org/browse/FORGE-1361 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 1.4.3.Final, 2.0.0.Beta3 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > The generated REST resources always issue a HTTP 201 Response with a Location header in response to a HTTP POST. Some clients expect the response to contain an entity representation of the newly created resource. Therefore, we should allow users to control whether they want the entity to feature in the response. > This would require: > * the method be annotated with @Produces with the mediatype being the chosen resource representation. > * the entity() method be invoked to populate the entity in the response. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1419) Review the addon structure for scaffold and scaffold-faces

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1419?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1419: -------------------------------------- Fix Version/s: 2.x Future > Review the addon structure for scaffold and scaffold-faces > ---------------------------------------------------------- > > Key: FORGE-1419 > URL: https://issues.jboss.org/browse/FORGE-1419 > Project: Forge > Issue Type: Task > Components: Scaffold > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > Currently there is some form of interdependency between the scaffold addon and the scaffold-faces addon. The scaffold-faces addon depends on the APIs and SPIs provided by the scaffold addon, while the scaffold-addon embeds the scaffold-faces addon. This was done so that the faces addon that supplies JSF scaffolding is available OOTB, without requiring an additional addon to be installed. > We need to simplify this, since this is confusing for maintenance. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1419) Review the addon structure for scaffold and scaffold-faces

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1419?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1419: ------------------------------------------- The scaffold-faces addon should consume API/SPI from scaffold addon. The scaffold addon should consume API/SPI services that it has defined, but are provided by the scaffold-faces (or other) addon(s). > Review the addon structure for scaffold and scaffold-faces > ---------------------------------------------------------- > > Key: FORGE-1419 > URL: https://issues.jboss.org/browse/FORGE-1419 > Project: Forge > Issue Type: Task > Components: Scaffold > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > Currently there is some form of interdependency between the scaffold addon and the scaffold-faces addon. The scaffold-faces addon depends on the APIs and SPIs provided by the scaffold addon, while the scaffold-addon embeds the scaffold-faces addon. This was done so that the faces addon that supplies JSF scaffolding is available OOTB, without requiring an additional addon to be installed. > We need to simplify this, since this is confusing for maintenance. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1406) Support customization of Forge generated artifacts in Faces scaffolding

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1406?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1406: -------------------------------------- Fix Version/s: 2.x Future > Support customization of Forge generated artifacts in Faces scaffolding > ----------------------------------------------------------------------- > > Key: FORGE-1406 > URL: https://issues.jboss.org/browse/FORGE-1406 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Currently, the customization of the generated scaffold is limited to the Faces template used for the page. Aspects of the generated scaffold like the managed beans, the CSS files etc. cannot be customized during generation; they have to modified after generation. > This feature request is to track the ability to customize any necessary aspects of the generated scaffold. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1415) Target Unreachable, 'entityName' returned null after Bean Validation failure

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1415?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1415: -------------------------------------- Fix Version/s: 2.x Future > Target Unreachable, 'entityName' returned null after Bean Validation failure > ---------------------------------------------------------------------------- > > Key: FORGE-1415 > URL: https://issues.jboss.org/browse/FORGE-1415 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.3.Final > Environment: JBossAS7.1 > Reporter: Esteve Aviles > Fix For: 2.x Future > > > Hi, > When you want to persist a new entity through create.xhtml page and the information produces a server side error then the error is show and when you fix it and try to summit again an Exception occurs: > {noformat} > /view/operacio/inventariMobilePos/create.xhtml @50,58 value="#{inventariMobilePosBean.inventariMobilePos.codiTmb}": Target Unreachable, 'inventariMobilePos' returned null > {noformat} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1402) Angularjs plugin does not create supporting beans

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1402?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1402: -------------------------------------- Fix Version/s: 2.x Future > Angularjs plugin does not create supporting beans > -------------------------------------------------- > > Key: FORGE-1402 > URL: https://issues.jboss.org/browse/FORGE-1402 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 1.4.1.Final > Environment: Mac Maverick with JBDS 7.1 > Reporter: Robb Greathouse > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > When using the Angularjs plugin it creates the html pages; but does not create the backing beans to support the functionality of the page. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1381) Being able to clear parts of the generated code (or all the project)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1381?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1381. ------------------------------------- Resolution: Won't Fix This is what the resource transaction API is for. {code} transaction-start // do some commands jpa-setup jpa-new-entity // OOPS did it wrong transaction-rollback {code} Energy should be spent making this transaction API as robust and comprehensive as possible. > Being able to clear parts of the generated code (or all the project) > -------------------------------------------------------------------- > > Key: FORGE-1381 > URL: https://issues.jboss.org/browse/FORGE-1381 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Beta3 > Reporter: Antonio Goncalves > > When prototyping using a Forge script, sometimes I would like to have a command that would delete parts of a project (or everything) from dependencies in the {{pom.xml}} to source code. Something like : > {code} > jpa-clear # deletes the code of the entities and the JPA dependencies > jsf-clear # deletes the backing bean and pages > ... > project-clear # deletes everything (source code, and pom dependencies) leaving empty directories and artifactId and groupId > {code} > And then I would be able to start again from scratch without leaving the CLI. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1423) REST resources generated by the REST plugin do not abstract java.sql.* types

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1423?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1423: -------------------------------------- Fix Version/s: 2.x Future > REST resources generated by the REST plugin do not abstract java.sql.* types > ---------------------------------------------------------------------------- > > Key: FORGE-1423 > URL: https://issues.jboss.org/browse/FORGE-1423 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.4.3.Final, 2.0.0.Beta4 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > When Date/Time temporal types are serialized or deserialized by the generated REST resources, the underlying {{java.sql.Date/java.sql.Time}} values in JPA entities (and also DTOs) are referenced directly by Jackson. > This leads to several problems: > * The serialized time values lack any timezone info leading to date/time shifting issues when they're deserialized back. > * By default, Jackson deserializes properties in JSON objects to {{java.util.Date}} instances only for a subset of ISO8601 formats. Partial time values are not a supported format and thus time values submitted by clients cannot be parsed. > For more info see: http://wiki.fasterxml.com/JacksonFAQDateHandling -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1403) Pressing TAB twice while completing should print a description of the current option being completed

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1403?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1403: -------------------------------------- Fix Version/s: 2.x Future > Pressing TAB twice while completing should print a description of the current option being completed > ---------------------------------------------------------------------------------------------------- > > Key: FORGE-1403 > URL: https://issues.jboss.org/browse/FORGE-1403 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Forge 1 is very good about helping the user figure out what various command options are for. Forge 2 lacks this helpful information, and it would be useful to display. -- 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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014