August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds updated FORGEPLUGINS-126: ----------------------------------------- Priority: Critical (was: Major) > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-128) AngularJS scaffold facet is deactivated on exit from the project context

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-128?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-128. ------------------------------------------ Resolution: Partially Completed Partially completed. Pushed to topic branch: https://github.com/forge/angularjs-scaffoldx-plugin/tree/FORGEPLUGINS-128 This will need to be completed by updating the Forge API version used, after Forge 1.4.0 is released. > AngularJS scaffold facet is deactivated on exit from the project context > ------------------------------------------------------------------------ > > Key: FORGEPLUGINS-128 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-128 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > After incorporating the fix for FORGEPLUGINS-124, the following behavior is observed. Exiting from the project context either by changing the directory or by restarting Forge, the AngularJS facet installed in the project is lost and the scaffolding needs to be setup once again. > This is due to the project-scoped configuration not being activated before invocation of {{Facet.isInstalled()}}. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-128) AngularJS scaffold facet is deactivated on exit from the project context

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-128?page=com.atlassian.jira.... ] Work on FORGEPLUGINS-128 started by Vineet Reynolds. > AngularJS scaffold facet is deactivated on exit from the project context > ------------------------------------------------------------------------ > > Key: FORGEPLUGINS-128 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-128 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > After incorporating the fix for FORGEPLUGINS-124, the following behavior is observed. Exiting from the project context either by changing the directory or by restarting Forge, the AngularJS facet installed in the project is lost and the scaffolding needs to be setup once again. > This is due to the project-scoped configuration not being activated before invocation of {{Facet.isInstalled()}}. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-125) Support Temporal fields of type datetime in the AngularJS scaffolding

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-125?page=com.atlassian.jira.... ] Vineet Reynolds commented on FORGEPLUGINS-125: ---------------------------------------------- Fixed up display issues involving temporal types in the search results in this commit: https://github.com/forge/angularjs-scaffoldx-plugin/commit/d724cbd9191cc2... The datetime widget support is still not done. > Support Temporal fields of type datetime in the AngularJS scaffolding > --------------------------------------------------------------------- > > Key: FORGEPLUGINS-125 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-125 > 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 polyfills. > This: https://github.com/jonstipe/datetime-polyfill looks like a polyfill that we could consider, but we would need to write an AngularJS directive. > The same applies to this Bootstrap based datetime picker: http://www.malot.fr/bootstrap-datetimepicker/index.php -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-125) Support Temporal fields of type datetime in the AngularJS scaffolding

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-125?page=com.atlassian.jira.... ] Work on FORGEPLUGINS-125 started by Vineet Reynolds. > Support Temporal fields of type datetime in the AngularJS scaffolding > --------------------------------------------------------------------- > > Key: FORGEPLUGINS-125 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-125 > 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 polyfills. > This: https://github.com/jonstipe/datetime-polyfill looks like a polyfill that we could consider, but we would need to write an AngularJS directive. > The same applies to this Bootstrap based datetime picker: http://www.malot.fr/bootstrap-datetimepicker/index.php -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1104) REST plugin stores the path of the Activator class instead of the classname in the project config

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1104?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1104. ---------------------------------- Assignee: Vineet Reynolds Fix Version/s: 1.4.0.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/f3cc7f554c68e9ecbbe1a727569924ee595f... > REST plugin stores the path of the Activator class instead of the classname in the project config > ------------------------------------------------------------------------------------------------- > > Key: FORGE-1104 > URL: https://issues.jboss.org/browse/FORGE-1104 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: 1.4.0.Final > > > The fully qualified path aka location of the file containing the {{@ApplicationPath}} annotation is stored in the project configuration by the REST plugin. It should instead store just the simple class name since this class name is appended with the stored package name to determine whether the facet should be activated or not. > There are no issues encountered except that the ApplicationPath class is scanned for every time the project is opened since the class will eventually be found, but once found the incorrect entry is stored. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1103) Upgrade the REST plugin to use the ConfigurationFactory API

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1103?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1103. ---------------------------------- Resolution: Done Pushed upstream: https://github.com/forge/core/commit/747291844a585c664bcbe4fce03218561f5c... > Upgrade the REST plugin to use the ConfigurationFactory API > ----------------------------------------------------------- > > Key: FORGE-1103 > URL: https://issues.jboss.org/browse/FORGE-1103 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.4.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.4.0.Final > > > Given that FORGE-1100 is fixed, the REST plugin and it's facets should use the newer ConfigurationFactory API. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1101) REST facet should be activated when either RestWebXmlFacet or RestApplicationFacet is active

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1101?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1101. ---------------------------------- Assignee: Vineet Reynolds Fix Version/s: 1.4.0.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/ba7b9a5d8c133eaaee44d80b93395bfef90f... > REST facet should be activated when either RestWebXmlFacet or RestApplicationFacet is active > -------------------------------------------------------------------------------------------- > > Key: FORGE-1101 > URL: https://issues.jboss.org/browse/FORGE-1101 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.4.0.Final > > > The Rest facet should not require both of these to be activated. Either should be sufficient. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1104) REST plugin stores the path of the Activator class instead of the classname in the project config

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1104: -------------------------------------- Summary: REST plugin stores the path of the Activator class instead of the classname in the project config Key: FORGE-1104 URL: https://issues.jboss.org/browse/FORGE-1104 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Priority: Minor The fully qualified path aka location of the file containing the {{@ApplicationPath}} annotation is stored in the project configuration by the REST plugin. It should instead store just the simple class name since this class name is appended with the stored package name to determine whether the facet should be activated or not. There are no issues encountered except that the ApplicationPath class is scanned for every time the project is opened since the class will eventually be found, but once found the incorrect entry is stored. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1103) Upgrade the REST plugin to use the ConfigurationFactory API

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1103: -------------------------------------- Summary: Upgrade the REST plugin to use the ConfigurationFactory API Key: FORGE-1103 URL: https://issues.jboss.org/browse/FORGE-1103 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.4.0.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds Fix For: 1.4.0.Final Given that FORGE-1100 is fixed, the REST plugin and it's facets should use the newer ConfigurationFactory API. -- 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, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013