June 2014 - forge-issues - Jboss List Archives

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-837?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-837: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > RestPlugin supports only whole numbers as resource identifiers > -------------------------------------------------------------- > > Key: FORGE-837 > URL: https://issues.jboss.org/browse/FORGE-837 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-984) Create base class for Bean classes generated by scaffold from-entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-984?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-984: ---------------------------------- Priority: Trivial (was: Major) > Create base class for Bean classes generated by scaffold from-entity > -------------------------------------------------------------------- > > Key: FORGE-984 > URL: https://issues.jboss.org/browse/FORGE-984 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: George Gastaldi > Priority: Trivial > Fix For: 2.x Future > > > In order to promote code reuse, we should generate an abstract Bean class and make all Beans generated by the scaffold extend this abstract class. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-984) Create base class for Bean classes generated by scaffold from-entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-984?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-984: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Create base class for Bean classes generated by scaffold from-entity > -------------------------------------------------------------------- > > Key: FORGE-984 > URL: https://issues.jboss.org/browse/FORGE-984 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > In order to promote code reuse, we should generate an abstract Bean class and make all Beans generated by the scaffold extend this abstract class. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-165) AngularJS search screen does not use the same input type as the detail

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-165?page=com.atlassian.jira.... ] George Gastaldi moved FORGE-906 to FORGEPLUGINS-165: ---------------------------------------------------- Project: Forge Plugins (was: Forge) Key: FORGEPLUGINS-165 (was: FORGE-906) Affects Version/s: (was: 1.3.0.Final) Component/s: AngularJS Scaffold (was: Scaffold) Fix Version/s: (was: 1.x Future) > AngularJS search screen does not use the same input type as the detail > ----------------------------------------------------------------------- > > Key: FORGEPLUGINS-165 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-165 > Project: Forge Plugins/Addons > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: AngularJS Scaffold > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Labels: angularjs > > Date fields are represented as text fields in the search screen. I tried to just change it to date but the search feature didn't work. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1031) Synchronize repository.yaml model with Forge's plugin installation model

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1031?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1031. ---------------------------------- Fix Version/s: (was: 1.x Future) Resolution: Out of Date Fixed in the Forge 2 distribution system > Synchronize repository.yaml model with Forge's plugin installation model > ------------------------------------------------------------------------ > > Key: FORGE-1031 > URL: https://issues.jboss.org/browse/FORGE-1031 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 1.3.3.Final > Reporter: Lennart Jörelid > Priority: Minor > > The repository.yaml file holds a Maven GAV to each Forge Plugin. > However, Forge's resolution only retrieves the latest/HEAD revision of a particular Git Branch, ignoring the Maven GAV given in the repository.yaml. > Thus, one *must* release SNAPSHOT plugin versions in order to be able to bugfix Forge plugins. This is quite contrary to a normal Maven release, where SNAPSHOT versions are not permitted (for example by the release plugin). > So ... > # Forge only uses HEAD of a branch to find a plugin source code revision > # Repository.yaml indicates that a particular Maven GAV for a project should be used for the plugin > # During resolution, Forge ignores the Maven GAV in repository.yaml > # Maven releases are normally not permitted to contain SNAPSHOTs, but the two facts above *requires* Forge plugins to be Maven SNAPSHOTs. > It seems that two different (and not particularly coherent) models are used to define Forge's resolution here. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-904) Document the Scaffold-X plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-904?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-904. --------------------------------- Fix Version/s: (was: 1.x Future) Resolution: Out of Date No longer used in Forge 2.x > Document the Scaffold-X plugin > ------------------------------ > > Key: FORGE-904 > URL: https://issues.jboss.org/browse/FORGE-904 > Project: Forge > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The Forge Scaffold-X API and plugin released in 1.3.0 should be documented in the Forge documentation site. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1228) increase conversation timeout to 30 minutes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1228?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1228: ----------------------------------- Fix Version/s: (was: 1.x Future) > increase conversation timeout to 30 minutes > ------------------------------------------- > > Key: FORGE-1228 > URL: https://issues.jboss.org/browse/FORGE-1228 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 1.4.1.Final > Reporter: Gerry Matte > Priority: Minor > Fix For: 2.x Future > > > The scaffold generated entity DAO beans contain two conversation.begin() commands [in the create() and retrieve() methods] > After each conversation.begin() please insert: > this.conversation.setTimeout(1800000); > which will extend the conversation timeout from the default ten minutes to thirty minutes (same as the session timeout) > For me, complex data entry screens often have their conversation expire during the period that a user composes and keys their data. Very frustrating ! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1067) Adopt WebJars as encapsulation for Bootstrap and JQuery resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1067?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1067: ----------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Adopt WebJars as encapsulation for Bootstrap and JQuery resources > ----------------------------------------------------------------- > > Key: FORGE-1067 > URL: https://issues.jboss.org/browse/FORGE-1067 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment JBoss Forge copies the {{bootstrap.css}} into the resources directory. It would be nice to use WebJar [1] to package Bootstrap (and JQuery) into the war file. > For this to happen you just need to add the following Maven dependencies to the {{pom.xml}} : > {code} > <dependency> > <groupId>org.webjars</groupId> > <artifactId>bootstrap</artifactId> > <version>2.3.2</version> > </dependency> > <dependency> > <groupId>org.webjars</groupId> > <artifactId>jquery</artifactId> > <version>2.0.3</version> > </dependency> > {code} > Then, change the {{pageTemplate.xhtml}} so it looks like this : > {code} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title> > <link rel="icon" href="#{resource['favicon.ico']}"/> > <h:outputStylesheet library="webjars/bootstrap/2.3.2/css" name="bootstrap.min.css"/> > <h:outputStylesheet name="forge-style.css"/> > </h:head> > <h:body> > ... > ... > ... >  >  > <h:outputScript name="webjars/jquery/2.0.3/jquery.min.js"/> > <h:outputScript library="webjars/bootstrap/2.3.2/js" name="bootstrap.min.js"/> > </h:body> > </html> > {code} > And of course, get rid of the {{bootstrap.css}} file ;o) > [1] http://www.webjars.org/ > [1] http://www.jamesward.com/2012/10/31/webjars-officially-launched > See also : https://issues.jboss.org/browse/RF-12584 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1164) `project remove-managed-dependency` does not remove managed dependency

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1164. ---------------------------------- Fix Version/s: (was: 1.x Future) Resolution: Out of Date Fixed in Forge 2.x > `project remove-managed-dependency` does not remove managed dependency > ---------------------------------------------------------------------- > > Key: FORGE-1164 > URL: https://issues.jboss.org/browse/FORGE-1164 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > > I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies : > {code} > $ project list-managed-dependencies > org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import > org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided > javax : javaee-api : 7.0 : jar : provided > {code} > If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist : > {code} > $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0 > Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project... > {code} > I even tried adding version, scope and so on, but it doesn't work : > {code} > $ project remove-managed-dependency > ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import > Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project... > {code} > PS : same occur in Forge 1.3.3-Final -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-524) Scaffolding an entity with enum uses a <f:selectItem> for each enum value

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-524?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-524: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Scaffolding an entity with enum uses a <f:selectItem> for each enum value > ------------------------------------------------------------------------- > > Key: FORGE-524 > URL: https://issues.jboss.org/browse/FORGE-524 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > When scaffolding an entity with a enumeration as an attribute (displaying it as a selectOneMenu), the enum values are placed directly inside the XHTML. > This is a bad thing, since when you modify the enumeration you MUST change the XHTML also. The scaffolding should use <f:selectItems> instead -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014