October 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2279) Renaming parameters so their either use camel case or dash

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2279?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2279. ---------------------------------- Fix Version/s: 3.0.0.Alpha1 (was: 3.x Future) Assignee: George Gastaldi Resolution: Done > Renaming parameters so their either use camel case or dash > ---------------------------------------------------------- > > Key: FORGE-2279 > URL: https://issues.jboss.org/browse/FORGE-2279 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > One discussion that came once on #IRC was "shall we use camel case on the command parameters, or shall we be more 'unixy' and use a dash syntax". At the moment, most of the parameters have the following syntax : > {code} > --targetPackage > --targetLocation > --columnName > {code} > But a few parameters don't use camel case but the dash syntax : > {code} > --not-nullable > --not-insertable > --not-updatable > {code} > We should choose one syntax and stick to it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2077) Batch mode should process keyboard input

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2077?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2077. ---------------------------------- Release Notes Text: Batch mode and script execution should run by themselves Resolution: Won't Fix > Batch mode should process keyboard input > ---------------------------------------- > > Key: FORGE-2077 > URL: https://issues.jboss.org/browse/FORGE-2077 > Project: Forge > Issue Type: Bug > Reporter: Ondrej Zizka > Fix For: 2.x Future > > > STR: > 1) Download Windup 2 > 2) Run bin/windup.sh -e "man windup-migrate-app" > Now you're stuck :) > Forge should process keyboard input somehow. Maybe just for some actions? Or, user should have an option whether to read from stdin or keyboard? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2499) Upgrade minimum version to JDK 1.8

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2499?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2499. ---------------------------------- Resolution: Done > Upgrade minimum version to JDK 1.8 > ---------------------------------- > > Key: FORGE-2499 > URL: https://issues.jboss.org/browse/FORGE-2499 > Project: Forge > Issue Type: Feature Request > Components: Forge Build > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > Forge sources should target JDK 8+ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2499) Upgrade minimum version to JDK 1.8

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2499: -------------------------------------- Summary: Upgrade minimum version to JDK 1.8 Key: FORGE-2499 URL: https://issues.jboss.org/browse/FORGE-2499 Project: Forge Issue Type: Feature Request Components: Forge Build Affects Versions: 2.19.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.0.0.Alpha1 Forge sources should target JDK 8+ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2470) List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx University (by mid-November 2015)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2470?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2470: ----------------------------------- Summary: List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx University (by mid-November 2015) (was: List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx Univeristy (by mid-November 2015)) > List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx University (by mid-November 2015) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2470 > URL: https://issues.jboss.org/browse/FORGE-2470 > Project: Forge > Issue Type: Task > Components: Brainstorming > Affects Versions: 2.19.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Here are a few JIRAs that would get to be implemented so it makes the talk smoother : > * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not > * [ROASTER-51] - Add interface or abstract class should implement inherited methods > * [FORGE-2466] - Cannot use '~' in most of the command parameters > * [FORGE-1580] - Having more flexible templating to integrate JSF pages better > * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute > * [FORGE-1808] - Being able to have inheritance in CDI > * [FORGE-1594] - Being able to create a new JSF View > * [FORGE-2081] - Being able to add a new CDI event producer to an existing class > * [FORGE-2079] - Being able to add a new CDI producer field > * [FORGE-2225] - Being able to add a new CDI producer method to an existing class > * [FORGE-2468] - Being able to add methods to an existing JSF backing bean > * [FORGE-2318] - Being able to setup a logger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-83) JavaClass.getMethod retrieves the first method with no parameters

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-83?page=com.atlassian.jira.plugin... ] George Gastaldi closed ROASTER-83. ---------------------------------- Resolution: Done > JavaClass.getMethod retrieves the first method with no parameters > ----------------------------------------------------------------- > > Key: ROASTER-83 > URL: https://issues.jboss.org/browse/ROASTER-83 > Project: Roaster > Issue Type: Feature Request > Components: JDT > Affects Versions: 2.17.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.17.1.Final > > > When you try to get a method with parameters, you instead get the first method with no parameters if it exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-83) JavaClass.getMethod retrieves the first method with no parameters

by George Gastaldi (JIRA)

George Gastaldi created ROASTER-83: -------------------------------------- Summary: JavaClass.getMethod retrieves the first method with no parameters Key: ROASTER-83 URL: https://issues.jboss.org/browse/ROASTER-83 Project: Roaster Issue Type: Feature Request Components: JDT Affects Versions: 2.17.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.17.1.Final When you try to get a method with parameters, you instead get the first method with no parameters if it exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2490) Handling of unique constraint exceptions

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2490?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2490: ---------------------------------------- How can we solve this issue? Can you provide a pull-request with the necessary fix? Thanks > Handling of unique constraint exceptions > ---------------------------------------- > > Key: FORGE-2490 > URL: https://issues.jboss.org/browse/FORGE-2490 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.19.2.Final > Environment: Faces 2.2, Hibernate, Oracle 11g, WildFly 8.2 > Reporter: Aitor Fdez-Ceballos Jiménez > Fix For: 2.x Future > > > If you scaffold an Entity in which you have an unique constraint (i.e: java-add-annotation --onProperty testField --annotation Column(unique=true)) the generated code isn't able to handle the exception when you violate the unique, unlike other restrictions, and redirects the user to the general error page, losing the inserted data. > Reading about this my conclusion is that JPA doesn't manage this and delegates to the database. Anyway, It would be great if the generated Forge beans could handle the restriction just like with the others and show a validation error instead of redirecting to the error page. > I have tried with two different approaches to manage this: > 1) Flush after the persist/merge in the bean so we can catch the SQLIntegrityConstraintViolationException in the update method and then add a proper message. > 2) Launch a previous select query to the database to see if the value is already in the database (not very efficient / smart) > Following the option 1 we faced another problem and we have finally extended ours beans from a "general bean" in which we have an interceptor method with @AroundInvoke annotation to handle errors from the database. This appear to be necessary sometimes when we get an EJBTransactionRolledbackException (i.e when you are editing [not creating] an object, because the exception is launched in CMTTxInterceptor so we cannot catch it in the update method) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2430) Migrate projects addon to simple container

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2430?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2430. ---------------------------------- Fix Version/s: 2.20.0.Final (was: 2.x Future) Resolution: Done > Migrate projects addon to simple container > ------------------------------------------ > > Key: FORGE-2430 > URL: https://issues.jboss.org/browse/FORGE-2430 > Project: Forge > Issue Type: Sub-task > Components: Projects > Affects Versions: 2.17.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.20.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2436) InputComponentInjectionEnricher is bound to CDI API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2436?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2436. ---------------------------------- Fix Version/s: 2.20.0.Final (was: 2.x Future) Resolution: Done > InputComponentInjectionEnricher is bound to CDI API > --------------------------------------------------- > > Key: FORGE-2436 > URL: https://issues.jboss.org/browse/FORGE-2436 > Project: Forge > Issue Type: Enhancement > Components: UI - API > Affects Versions: 2.17.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > InputComponentInjectionEnricher presents a method that takes a {{javax.enterprise.inject.spi.InjectionPoint}} as a parameter. > That doesn't allow addons that depend on another container (eg. simple) to implement it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2015