January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-159) Support Temporal fields of type date and time in the AngularJS scaffolding

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-159?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-159. ------------------------------------------ Resolution: Done Pushed: https://github.com/forge/angularjs-scaffoldx-plugin/commit/3ea3e917b58c6c... This adds two new directives for handling HTML5 date and time input that is not yet supported in all browsers. > Support Temporal fields of type date and time in the AngularJS scaffolding > -------------------------------------------------------------------------- > > Key: FORGEPLUGINS-159 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-159 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The generated AngularJS scaffold treats datetime fields as text fields. It would be preferable to the HTML5 input['datetime'] support, but given that most browsers do not support it yet, we should attempt to support it via Modernizr based detection and a fallback to an input validation driven widget. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-160) Have scaffolding put labels etc in i18n property files

by Jose Miguel Loor (JIRA)

[ https://issues.jboss.org/browse/FORGE-160?page=com.atlassian.jira.plugin.... ] Jose Miguel Loor reassigned FORGE-160: -------------------------------------- Assignee: Jose Miguel Loor > Have scaffolding put labels etc in i18n property files > ------------------------------------------------------ > > Key: FORGE-160 > URL: https://issues.jboss.org/browse/FORGE-160 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.0.0.Alpha4 > Reporter: Ronald van Kuijk > Assignee: Jose Miguel Loor > Priority: Optional > Labels: scaffold > Fix For: 2.x Future > > > To support easy i18n, the labels for e.g. colums or input fields should be put in files. > Decide on: > - label conventions > - use of jsf i18n or seam i18n > - ... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-158) Upgrade jQuery to 2.x

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-158?page=com.atlassian.jira.... ] Vineet Reynolds reopened FORGEPLUGINS-158: ------------------------------------------ Reopening this, since it is meant to be done in the WFK 2.6 timeframe. > Upgrade jQuery to 2.x > --------------------- > > Key: FORGEPLUGINS-158 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-158 > Project: Forge Plugins > Issue Type: Task > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us. > To allow the generated scaffold to be of use in Cordova apps, we'll upgrade to jQuery 2.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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1414) CommandExecutionListeners are not called when native Aesh Commands are run

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1414?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1414. ---------------------------------- Resolution: Done > CommandExecutionListeners are not called when native Aesh Commands are run > -------------------------------------------------------------------------- > > Key: FORGE-1414 > URL: https://issues.jboss.org/browse/FORGE-1414 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > -- 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, 3 months

1
0
0 / 0

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

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1422: ---------------------------------------- We'll need to bring in exception mapping support like the one in Jersey: https://jersey.java.net/documentation/latest/bean-validation.html#d0e11775 Unfortunately, that is not standardized. For JBoss EAP based REST resources, we may wish to do something similar in RESTEasy, to serialize BV errors into HTTP responses. > 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 > > 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, 3 months

1
0
0 / 0

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

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ] Burr Sutter commented on FORGE-1422: ------------------------------------ the current 500 results: http://screencast.com/t/O7fzSXfYR2q3 Unfortunately Firebug Lite (in CordovaSim) would not let me copy & paste the text, so I took a screenshot > 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 > > 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, 3 months

1
0
0 / 0

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

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ] Burr Sutter commented on FORGE-1422: ------------------------------------ memberPipe.save(newContactAsJSON, { success: function(data) { console.log("success"); $("#inputName").val(""); $("#inputPhone").val(""); $("#inputEmail").val(""); $.mobile.changePage("#page-1"); app.refreshRESTContacts(); }, error: function(error) { console.log("status: " + error.status); // if error.status == 400 // bean validation errors // need a nice string to display in my errorDialog console.log("responseText: " + error.responseText); $.mobile.changePage("#errorDialog"); } }); // memberPipe.save > 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 > > 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, 3 months

1
0
0 / 0

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

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1422: -------------------------------------- Summary: 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 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1421) Move back to ShrinkWrap Descriptors

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1421: -------------------------------------- Summary: Move back to ShrinkWrap Descriptors Key: FORGE-1421 URL: https://issues.jboss.org/browse/FORGE-1421 Project: Forge Issue Type: Task Components: Parsers / File Manipulation Affects Versions: 2.0.0.Beta4 Reporter: George Gastaldi Fix For: 2.x Future After SHRINKDESC-151 is resolved, we can switch back to ShrinkWrap Descriptors. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1420) Create a UICommand to create test classes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1420?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1420. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > Create a UICommand to create test classes > ----------------------------------------- > > Key: FORGE-1420 > URL: https://issues.jboss.org/browse/FORGE-1420 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins, Test Harness > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > There should be two commands: > - should be able to setup test dependencies; > - should be able to create a test class and configure the Furnace Arquillian provider -- 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, 3 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