June 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1855) Simple Container should support singleton services

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1855: ----------------------------------- Labels: (was: starter) > Simple Container should support singleton services > -------------------------------------------------- > > Key: FORGE-1855 > URL: https://issues.jboss.org/browse/FORGE-1855 > Project: Forge > Issue Type: Feature Request > Components: Furnace Simple > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. > I propose a {{public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1804) Generated code is not properly indented

by Rafael Pestano (JIRA)

[ https://issues.jboss.org/browse/FORGE-1804?page=com.atlassian.jira.plugin... ] Rafael Pestano commented on FORGE-1804: --------------------------------------- Hi guys, attached my win7 output. > Generated code is not properly indented > --------------------------------------- > > Key: FORGE-1804 > URL: https://issues.jboss.org/browse/FORGE-1804 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > Attachments: win7.png > > > *The affected version is 2.5.1-SNAPSHOT*. I noticed a regression in 2.5.1-SNAPSHOT. > I create an Entity and an EJB : > {code} > [temp]$ project-new --named proj251 > [proj251]$ jpa-new-entity --named MyEntity > [MyEntity.java]$ ejb-new-bean --named MyService > {code} > If I run this script in 2.5.0 the generated code is well indented. Here for the entity : > {code} > import java.lang.Override; > @Entity > public class MyEntity implements Serializable > {code} > And for the EJB : > {code} > import java.io.Serializable; > @Stateless > @LocalBean > public class MyService implements Serializable > {code} > But when I do that with 2.5.1-SNAPSHOT, the class annotation is not right : > {code} > import java.lang.Override;@Entity > public class MyEntity implements Serializable { > {code} > And > {code} > import java.io.Serializable;@Stateless > @LocalBean > public class MyService implements Serializable { > {code} > I haven't tried with all the other artifacts, I'm wondering if it's on all the generated code or not -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1804) Generated code is not properly indented

by Rafael Pestano (JIRA)

[ https://issues.jboss.org/browse/FORGE-1804?page=com.atlassian.jira.plugin... ] Rafael Pestano updated FORGE-1804: ---------------------------------- Attachment: win7.png > Generated code is not properly indented > --------------------------------------- > > Key: FORGE-1804 > URL: https://issues.jboss.org/browse/FORGE-1804 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > Attachments: win7.png > > > *The affected version is 2.5.1-SNAPSHOT*. I noticed a regression in 2.5.1-SNAPSHOT. > I create an Entity and an EJB : > {code} > [temp]$ project-new --named proj251 > [proj251]$ jpa-new-entity --named MyEntity > [MyEntity.java]$ ejb-new-bean --named MyService > {code} > If I run this script in 2.5.0 the generated code is well indented. Here for the entity : > {code} > import java.lang.Override; > @Entity > public class MyEntity implements Serializable > {code} > And for the EJB : > {code} > import java.io.Serializable; > @Stateless > @LocalBean > public class MyService implements Serializable > {code} > But when I do that with 2.5.1-SNAPSHOT, the class annotation is not right : > {code} > import java.lang.Override;@Entity > public class MyEntity implements Serializable { > {code} > And > {code} > import java.io.Serializable;@Stateless > @LocalBean > public class MyService implements Serializable { > {code} > I haven't tried with all the other artifacts, I'm wondering if it's on all the generated code or not -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-885) Support Bean Validation 1.1 method constraints in plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-885?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-885: ------------------------------------- Assignee: George Gastaldi > Support Bean Validation 1.1 method constraints in plugins > --------------------------------------------------------- > > Key: FORGE-885 > URL: https://issues.jboss.org/browse/FORGE-885 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > > It would be nice if we could add support for BV 1.1 in a plugin method, avoiding the need to manually validate pre-conditions. This should happen after normal @Option validation, as there is an {{@Option(required=true)}} for example. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-885) Support Bean Validation 1.1 method constraints in plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-885?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-885: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/468 > Support Bean Validation 1.1 method constraints in plugins > --------------------------------------------------------- > > Key: FORGE-885 > URL: https://issues.jboss.org/browse/FORGE-885 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > > It would be nice if we could add support for BV 1.1 in a plugin method, avoiding the need to manually validate pre-conditions. This should happen after normal @Option validation, as there is an {{@Option(required=true)}} for example. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-451) Warn a user if generating relationship CRUD screens and HashCode/Equals are missing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-451?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-451: ------------------------------------------ Matej, is this issue complete? > Warn a user if generating relationship CRUD screens and HashCode/Equals are missing > ----------------------------------------------------------------------------------- > > Key: FORGE-451 > URL: https://issues.jboss.org/browse/FORGE-451 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: Pete Muir > Assignee: Matej Briskar > Labels: Starter > Fix For: 2.x Future > > > It's necessary to provide these on the entities in order for drop downs to work. If not provided, there should be a WARN message. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1855) Simple Container should support singleton services

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1855: ----------------------------------- Labels: starter (was: ) > Simple Container should support singleton services > -------------------------------------------------- > > Key: FORGE-1855 > URL: https://issues.jboss.org/browse/FORGE-1855 > Project: Forge > Issue Type: Feature Request > Components: Furnace Simple > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Labels: starter > Fix For: 2.x Future > > > In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. > I propose a {{public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loses defaultValue on dependent field update

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1848: ----------------------------------- Fix Version/s: 2.x Future (was: 2.6.0.Final) > IDE loses defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1860) Writing files with content

by Robert Balent (JIRA)

[ https://issues.jboss.org/browse/FORGE-1860?page=com.atlassian.jira.plugin... ] Robert Balent commented on FORGE-1860: -------------------------------------- Any other improvements which could be made in this issue? to "touch file --content xyz" is probably not good idea because touch is intended only to modify file timestamp. But "echo xyz > file" should by now fully working. > Writing files with content > -------------------------- > > Key: FORGE-1860 > URL: https://issues.jboss.org/browse/FORGE-1860 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Assignee: Robert Balent > Fix For: 2.x Future > > > I see myself adding files here and there on my projects (JBoss cli commands, shell scripts, SQL scripts...) and I use the touch command in Forge extensively. But how could I add content to these files ? I mostly write Forge scripts, so I would love to do something like that in my script : > {code} > # Creates a project > project-new --named test > # Adds a few extra files and directories > mkdir src/main/script ; > touch src/main/resources/insert.sql ; // This creates an empty file > touch src/main/script/wildfly-show.cli --content (((( // This adds content to the file > version > # #################### > # # System Properties > # #################### > /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties) > # #################### > # # Datasource > # #################### > /subsystem=datasources/data-source=ApplicationBlancheH2DS:read-resource > )))) > {code} > And this command would just create a file with the previous content in it. As you can see, this can be tricky : when to end the content of a file (something similar to <![CDATA[]]>) > George mentioned on the mailing list : > ??I think piping to a file would be more intuitive and it should work now:?? > {code} > echo Hi > a.txt > {code} > The problem with this, is I can't make it work the way I want. In fact, each time I do a {{echo text > file.txt}}, the {{file.txt}} is created in the directory below, not the current one. As I can't create a file in another directory. > {code} > [Devoxx]$ ls > [Devoxx]$ project-new --named testecho > ***SUCCESS*** Project named 'testecho' has been created. > [testecho]$ ls > pom.xml src > [testecho]$ echo Text to add to this new file > newfile.txt > [testecho]$ ls > pom.xml src > [testecho]$ cd .. > [Devoxx]$ ls > newfile.txt testecho > [Devoxx]$ > [testecho]$ echo One test again > ./file.txt > [testecho]$ ls > pom.xml src > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1860) Writing files with content

by Robert Balent (JIRA)

[ https://issues.jboss.org/browse/FORGE-1860?page=com.atlassian.jira.plugin... ] Robert Balent commented on FORGE-1860: -------------------------------------- ">" , ">>" and other operators were not writing to files in the actual working directory. This is now resolved in Aesh 0.56-SNAPSHOT. > Writing files with content > -------------------------- > > Key: FORGE-1860 > URL: https://issues.jboss.org/browse/FORGE-1860 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I see myself adding files here and there on my projects (JBoss cli commands, shell scripts, SQL scripts...) and I use the touch command in Forge extensively. But how could I add content to these files ? I mostly write Forge scripts, so I would love to do something like that in my script : > {code} > # Creates a project > project-new --named test > # Adds a few extra files and directories > mkdir src/main/script ; > touch src/main/resources/insert.sql ; // This creates an empty file > touch src/main/script/wildfly-show.cli --content (((( // This adds content to the file > version > # #################### > # # System Properties > # #################### > /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties) > # #################### > # # Datasource > # #################### > /subsystem=datasources/data-source=ApplicationBlancheH2DS:read-resource > )))) > {code} > And this command would just create a file with the previous content in it. As you can see, this can be tricky : when to end the content of a file (something similar to <![CDATA[]]>) > George mentioned on the mailing list : > ??I think piping to a file would be more intuitive and it should work now:?? > {code} > echo Hi > a.txt > {code} > The problem with this, is I can't make it work the way I want. In fact, each time I do a {{echo text > file.txt}}, the {{file.txt}} is created in the directory below, not the current one. As I can't create a file in another directory. > {code} > [Devoxx]$ ls > [Devoxx]$ project-new --named testecho > ***SUCCESS*** Project named 'testecho' has been created. > [testecho]$ ls > pom.xml src > [testecho]$ echo Text to add to this new file > newfile.txt > [testecho]$ ls > pom.xml src > [testecho]$ cd .. > [Devoxx]$ ls > newfile.txt testecho > [Devoxx]$ > [testecho]$ echo One test again > ./file.txt > [testecho]$ ls > pom.xml src > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014