July 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1916) Add versioning and exception handling to JAX-RS scaffolding

by Erik Jan de Wit (JIRA)

[ https://issues.jboss.org/browse/FORGE-1916?page=com.atlassian.jira.plugin... ] Erik Jan de Wit updated FORGE-1916: ----------------------------------- Assignee: George Gastaldi (was: Erik Jan de Wit) > Add versioning and exception handling to JAX-RS scaffolding > ----------------------------------------------------------- > > Key: FORGE-1916 > URL: https://issues.jboss.org/browse/FORGE-1916 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > Eric to provide the changes to the JAX-RS endpoint code to allow for entity versioning and dealing with update conflicts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1916) Add versioning and exception handling to JAX-RS scaffolding

by Erik Jan de Wit (JIRA)

[ https://issues.jboss.org/browse/FORGE-1916?page=com.atlassian.jira.plugin... ] Erik Jan de Wit updated FORGE-1916: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/481 > Add versioning and exception handling to JAX-RS scaffolding > ----------------------------------------------------------- > > Key: FORGE-1916 > URL: https://issues.jboss.org/browse/FORGE-1916 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > Assignee: Erik Jan de Wit > Priority: Critical > Fix For: 2.x Future > > > Eric to provide the changes to the JAX-RS endpoint code to allow for entity versioning and dealing with update conflicts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-166) Adding Ionic to AngularJS Scaffold

by Sebastien Blanc (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-166?page=com.atlassian.jira.... ] Sebastien Blanc commented on FORGEPLUGINS-166: ---------------------------------------------- Since an Ionic project will be in 95% of the cases a Cordova project what about to scaffold into an new hybrid mobile project (created on the fly) ? I would really love this feature. > Adding Ionic to AngularJS Scaffold > ---------------------------------- > > Key: FORGEPLUGINS-166 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-166 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: AngularJS Scaffold > Reporter: Burr Sutter > Assignee: Vineet Reynolds > Priority: Critical > > Leverage the Ionic UI widgets/controls for the AngularJS scaffold output. We will be adding an Ionic Palette in JBoss Tools as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1900) JSON should be the default content type when generating JAXRS Endpoints

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1900?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1900. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done > JSON should be the default content type when generating JAXRS Endpoints > ----------------------------------------------------------------------- > > Key: FORGE-1900 > URL: https://issues.jboss.org/browse/FORGE-1900 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1622: ------------------------------------ > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.7.0.Final > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1622: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done Merged. > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.7.0.Final > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1880) Being able to add @Named to an EJBs... or any annotation anywhere

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1880?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1880. ---------------------------------- Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done Merged, thanks! > Being able to add @Named to an EJBs... or any annotation anywhere > ----------------------------------------------------------------- > > Key: FORGE-1880 > URL: https://issues.jboss.org/browse/FORGE-1880 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Assignee: Robert Balent > Fix For: 2.7.0.Final > > > When I create an EJB with Forge with the following command : > {code} > ejb-new-bean --named MyService > {code} > I get the following : > {code} > @Stateless > @LocalBean > public class MyService implements Serializable > {code} > In some cases, I would need to add an extra {{@Named}} annotation. Several ways to do it. On the EJB command itself, we could add a parameter : > {code} > ejb-new-bean --named MyService --addNamed > {code} > But I think it would be good to have something more generic that could be used anywhere. We could use the same logic as constraint-add (that adds any kind of constraint on any Entity) and have something like > {code} > cdi-add-qualifier --qualifier Named --target org.app.service.MyService > // or on a property, which could be useful > cdi-add-qualifier --qualifier Named --onProperty myProp > cdi-add-qualifier --qualifier Named --onMethod myMethod > {code} > Or something even more generic would be to use the Java command > {code} > java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService > java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onProperty myProp > java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onMethod myMethod > java-add-annotation --annotation javax.inject.Named --onProperty myProp > java-add-annotation --annotation javax.inject.Named --onMethod myMethod > {code} > _Comments on the mailing list by Ivan_ > _I think that java-add-annotation is a good command that we should have. But still it would be better to have also something more explicit for creating named beans and setting stereotypes. So, I think that the three levels of abstraction that Antonio described may be implemented. Well, at the end they will reuse one and the same code for adding annotation, so no repeating ourselves will occur._ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1398) Being able to create embeddables

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1398?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1398. ---------------------------------- Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done Merged, thanks! > Being able to create embeddables > -------------------------------- > > Key: FORGE-1398 > URL: https://issues.jboss.org/browse/FORGE-1398 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Matej Briskar > Fix For: 2.7.0.Final > > > As per [FORGE-797] it would be good to have a new command to create an embeddable : > {code} > jpa-new-embeddable --named Address ; > jpa-new-field --named street1 --length 50 ; > jpa-new-field --named street2 ; > jpa-new-field --named city --length 50 ; > jpa-new-field --named state ; > {code} > Then, how do we embed it into a entity ? We could have a new {{--relationshipType}} : > {code} > jpa-new-entity --named Customer ; > jpa-new-field --named address --entity org.agoncal.application.petstore.model.Address --relationshipType Embedded ; > {code} > Except {{Address}} is not an entity. So having {{--entity}} pointing to an embeddable looks strange -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1917) ClasspathWorkspaceResolver no longer works for impl projects

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1917: -------------------------------------- Summary: ClasspathWorkspaceResolver no longer works for impl projects Key: FORGE-1917 URL: https://issues.jboss.org/browse/FORGE-1917 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Tools - Maven Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future In split projects (api/impl/addon), the tests no longer detect the changes in the workspace. This is caused because the classpath for the impl classes is no longer available for tests (impl was made <optional> by default) . This requires the user to manually install the api/impl projects before running the tests, which can be cumbersome -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2014