April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-109) Create a plugin based on Adam Bien's Real World Java EE patterns

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-109: -------------------------------------------- Summary: Create a plugin based on Adam Bien's Real World Java EE patterns Key: FORGEPLUGINS-109 URL: https://issues.jboss.org/browse/FORGEPLUGINS-109 Project: Forge Plugins Issue Type: Feature Request Reporter: Vineet Reynolds The description is kind of obvious. But we need to implement a curated set of patterns, so that we can tie these down to @Options and @Commands in the Forge plugin. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project

by George Gastaldi (JIRA)

George Gastaldi created FORGE-840: ------------------------------------- Summary: Provide a dependency information repository for the current project Key: FORGE-840 URL: https://issues.jboss.org/browse/FORGE-840 Project: Forge Issue Type: Feature Request Components: Usability Affects Versions: 2.0.0.Alpha1, 1.2.2.Final Reporter: George Gastaldi Fix For: 1.2.3.Final, 2.0.0.Alpha2 It would be nice if Forge could provide a query-able mechanism for a project such as it would be possible to retrieve information like: - All available @Entity mapped classes; - Classes that implement a specific interface; - Is a specific class present in the configured pom.xml? That would enrich user experience and also allow the writing of smarter plugins. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-840?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-840: ---------------------------------- Description: It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like: - All available @Entity mapped classes; - Classes that implement a specific interface; - Is a specific class present in the configured pom.xml? That would enrich user experience and also allow the writing of smarter plugins. was: It would be nice if Forge could provide a query-able mechanism for a project such as it would be possible to retrieve information like: - All available @Entity mapped classes; - Classes that implement a specific interface; - Is a specific class present in the configured pom.xml? That would enrich user experience and also allow the writing of smarter plugins. > Provide a dependency information repository for the current project > ------------------------------------------------------------------- > > Key: FORGE-840 > URL: https://issues.jboss.org/browse/FORGE-840 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 1.2.2.Final, 2.0.0.Alpha1 > Reporter: George Gastaldi > Fix For: 1.2.3.Final, 2.0.0.Alpha2 > > > It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like: > - All available @Entity mapped classes; > - Classes that implement a specific interface; > - Is a specific class present in the configured pom.xml? > That would enrich user experience and also allow the writing of smarter plugins. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-39) Create a plugin to ease usage of GoF Design Patterns

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-39?page=com.atlassian.jira.p... ] George Gastaldi updated FORGEPLUGINS-39: ---------------------------------------- Labels: gsoc (was: ) > Create a plugin to ease usage of GoF Design Patterns > ---------------------------------------------------- > > Key: FORGEPLUGINS-39 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-39 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: George Gastaldi > Labels: gsoc > > It would be nice to have a plugin to transform your code to use GoF patterns. > The plugin could ask for the classes involved on any of these patterns or create one -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-839) Upgrade to ShrinkWrap Resolver 2.0.0-beta-2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-839?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-839. --------------------------------- Assignee: George Gastaldi Resolution: Done > Upgrade to ShrinkWrap Resolver 2.0.0-beta-2 > ------------------------------------------- > > Key: FORGE-839 > URL: https://issues.jboss.org/browse/FORGE-839 > Project: Forge > Issue Type: Library Upgrade > Components: Maven Integration > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.0.0.Alpha2 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-108) Create a JodaTime Plugin

by George Gastaldi (JIRA)

George Gastaldi created FORGEPLUGINS-108: -------------------------------------------- Summary: Create a JodaTime Plugin Key: FORGEPLUGINS-108 URL: https://issues.jboss.org/browse/FORGEPLUGINS-108 Project: Forge Plugins Issue Type: Feature Request Reporter: George Gastaldi It would be nice to have a plugin that supports JodaTime and/or JSR310 specific annotations. The field plugin could be extended to allow mapping of temporal fields using Joda/JSR310 classes and specific user types when the JPA provider is Hibernate. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-839) Upgrade to ShrinkWrap Resolver 2.0.0-beta-2

by George Gastaldi (JIRA)

George Gastaldi created FORGE-839: ------------------------------------- Summary: Upgrade to ShrinkWrap Resolver 2.0.0-beta-2 Key: FORGE-839 URL: https://issues.jboss.org/browse/FORGE-839 Project: Forge Issue Type: Library Upgrade Components: Maven Integration Affects Versions: 2.0.0.Alpha1 Reporter: George Gastaldi Priority: Minor Fix For: 2.0.0.Alpha2 -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-837) RestPlugin supports only whole numbers as resource identifiers

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-837?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-837: ---------------------------------- Component/s: Java EE APIs > RestPlugin supports only whole numbers as resource identifiers > -------------------------------------------------------------- > > Key: FORGE-837 > URL: https://issues.jboss.org/browse/FORGE-837 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Reporter: Vineet Reynolds > > The RestPlugin contains the following {{@Path}} annotation: > {code} > @Path("/{id:[0-9][0-9]*}") > {code} > irrespective of the type of the JPA Entity @Id field. > Even among the basic @Id types deemed supported by the Rest plugin, having any of the decimal types like {{float}} and {{double}}, or {{String}}, as the type of the @Id field in the JPA entity would result in generation of an incorrect REST resource. > The regex should preferably be context-sensitive and contain a different regex for different @Id types, or be omitted altogether. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-838) RestPlugin should support the right semantics for entities with non auto-generated Ids

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-838?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-838: ---------------------------------- Component/s: Java EE APIs > RestPlugin should support the right semantics for entities with non auto-generated Ids > -------------------------------------------------------------------------------------- > > Key: FORGE-838 > URL: https://issues.jboss.org/browse/FORGE-838 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > > Currently, the generated REST resources contain a {{@POST}} method for creating new entities and a {{@PUT}} method for updating an existing entity. > This set of semantics is appropriate for auto-generated Ids where the Ids would be created by the server, and cannot be specified by the client. > However, for JPA entities that do not contain a {{@GeneratedValue}} annotation, these semantics may not be unsuitable. It would be preferable to use only a {{@PUT}} method that is used to create and update the entities. This is primarily because the client gets to decide the resource/entity identifier, and hence, also the location of the resource. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-838) RestPlugin should support the right semantics for entities with non auto-generated Ids

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-838: ------------------------------------- Summary: RestPlugin should support the right semantics for entities with non auto-generated Ids Key: FORGE-838 URL: https://issues.jboss.org/browse/FORGE-838 Project: Forge Issue Type: Feature Request Reporter: Vineet Reynolds Currently, the generated REST resources contain a {{@POST}} method for creating new entities and a {{@PUT}} method for updating an existing entity. This set of semantics is appropriate for auto-generated Ids where the Ids would be created by the server, and cannot be specified by the client. However, for JPA entities that do not contain a {{@GeneratedValue}} annotation, these semantics may not be unsuitable. It would be preferable to use only a {{@PUT}} method that is used to create and update the entities. This is primarily because the client gets to decide the resource/entity identifier, and hence, also the location of the resource. -- 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

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013