August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1087) DependencyFacet.removeProperty should be moved to MetadataFacet

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1087: -------------------------------------- Summary: DependencyFacet.removeProperty should be moved to MetadataFacet Key: FORGE-1087 URL: https://issues.jboss.org/browse/FORGE-1087 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 2.0.0.Alpha9 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Alpha10 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1086) JavaParser fails to identify types of ArrayType in field types

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1086?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1086: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/java-parser/pull/7 > JavaParser fails to identify types of ArrayType in field types > -------------------------------------------------------------- > > Key: FORGE-1086 > URL: https://issues.jboss.org/browse/FORGE-1086 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Similar to FORGE-1026, {{org.jboss.forge.parser.java.Field.getQualifiedType()}} converts array types into simple types resulting in loss of information about the field type. > This is due to Arrays being stripped away when org.jboss.forge.parser.java.impl.AbstractJavaSource.resolveType(String) is invoked. The type returned by AbstractJavaSource omits any information about the ArrayType in the provided argument, and this is not accounted for when returning the qualified type. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1086) JavaParser fails to identify types of ArrayType in field types

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1086?page=com.atlassian.jira.plugin... ] Vineet Reynolds reassigned FORGE-1086: -------------------------------------- Assignee: Vineet Reynolds > JavaParser fails to identify types of ArrayType in field types > -------------------------------------------------------------- > > Key: FORGE-1086 > URL: https://issues.jboss.org/browse/FORGE-1086 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Similar to FORGE-1026, {{org.jboss.forge.parser.java.Field.getQualifiedType()}} converts array types into simple types resulting in loss of information about the field type. > This is due to Arrays being stripped away when org.jboss.forge.parser.java.impl.AbstractJavaSource.resolveType(String) is invoked. The type returned by AbstractJavaSource omits any information about the ArrayType in the provided argument, and this is not accounted for when returning the qualified type. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1086) JavaParser fails to identify types of ArrayType in field types

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1086: -------------------------------------- Summary: JavaParser fails to identify types of ArrayType in field types Key: FORGE-1086 URL: https://issues.jboss.org/browse/FORGE-1086 Project: Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Similar to FORGE-1026, {{org.jboss.forge.parser.java.Field.getQualifiedType()}} converts array types into simple types resulting in loss of information about the field type. This is due to Arrays being stripped away when org.jboss.forge.parser.java.impl.AbstractJavaSource.resolveType(String) is invoked. The type returned by AbstractJavaSource omits any information about the ArrayType in the provided argument, and this is not accounted for when returning the qualified type. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1034) Upgrade forge-maven-plugin to use furnace-manager

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1034?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on FORGE-1034: -------------------------------------------- Its really not nice that we would have to move to Maven 3.1 in a bug fix release :/ > Upgrade forge-maven-plugin to use furnace-manager > ------------------------------------------------- > > Key: FORGE-1034 > URL: https://issues.jboss.org/browse/FORGE-1034 > Project: Forge > Issue Type: Component Upgrade > Components: Maven Plugin > Affects Versions: 2.0.0.Alpha6 > Reporter: George Gastaldi > Assignee: George Gastaldi > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1060) REST plugin should support creation of DTOs for the underlying JPA entities of REST resources

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1060?page=com.atlassian.jira.plugin... ] Work on FORGE-1060 started by Vineet Reynolds. > REST plugin should support creation of DTOs for the underlying JPA entities of REST resources > --------------------------------------------------------------------------------------------- > > Key: FORGE-1060 > URL: https://issues.jboss.org/browse/FORGE-1060 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Using JPA entities directly in the REST resources is obviously not proving to be of much help: > * It leads to problems when working with cyclic dependencies, as seen in FORGE-606. Using {{@JsonIdentityInfo}} to resolve this has lead to further problems on the client side due to the lack of support in JavaScript clients to handle JSON object references out of the box. > * It requires the entire object graph to be eagerly fetched and made available during the serialization process. During deserialization, JPA merges could result in incorrect behavior since merges of object graphs depend on whether the collection was previously fetched or not. Merges are not expected to occur by spec, unless the collection was fetched. See [HHH-4135|https://hibernate.atlassian.net/browse/HHH-4135] and [HHH-5187|https://hibernate.atlassian.net/browse/HHH-5187] for some details on Hibernate, with differing behavior in EclipseLink. > * It requires manipulation of the relational associations across entities to modify the resource representations, thus lacking separation of concerns. > * It provides no control over the depth of the object graph to be serialized. Annotations like {{@JsonIgnore}} are required to be placed on JPA entities which does not aid in separation of concerns. Custom serializers/deserializers offer little benefit concerning standards since they requires compilation against specific versions of the JSON libraries like Jackson for every container that is to be supported. > Therefore it is proposed to have the REST plugin create DTOs for representing the state of the JPA entities in the REST resources. -- 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, 11 months

1
0
0 / 0

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

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-125: -------------------------------------------- Summary: 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1085) Support ordering of elements in collections in responses for GET collection reqeusts

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1085?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1085. ---------------------------------- Assignee: Vineet Reynolds Resolution: Done Pushed upstream: https://github.com/forge/core/commit/744d7dd354b2d184cd38550facc243678f7f... > Support ordering of elements in collections in responses for GET collection reqeusts > ------------------------------------------------------------------------------------ > > Key: FORGE-1085 > URL: https://issues.jboss.org/browse/FORGE-1085 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The {{listAll}} method in the generated REST resources lacks an ORDER BY clause. Due to the absence of such a clause, results are unordered. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1085) Support ordering of elements in collections in responses for GET collection reqeusts

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1085: -------------------------------------- Summary: Support ordering of elements in collections in responses for GET collection reqeusts Key: FORGE-1085 URL: https://issues.jboss.org/browse/FORGE-1085 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds The {{listAll}} method in the generated REST resources lacks an ORDER BY clause. Due to the absence of such a clause, results are unordered. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1084) REST resources generated by the REST plugin contains duplicate values in resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1084?page=com.atlassian.jira.plugin... ] Vineet Reynolds reopened FORGE-1084: ------------------------------------ > REST resources generated by the REST plugin contains duplicate values in resource representations > ------------------------------------------------------------------------------------------------- > > Key: FORGE-1084 > URL: https://issues.jboss.org/browse/FORGE-1084 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The JPQL queries generated by the REST plugin should use the DISTINCT keyword to ensure that duplicate values are eliminated from the query result. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013