May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1670) JPA Setup Command should allow explicitly overwriting existing persistence units

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1670?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1670: ------------------------------------------- So I just looked into this - I don't believe you need to remove any persistence units (which you could do by removing all units and re-adding all but the unit you wish to remove). Overwrite should simply modify an existing PU, which is supported just by getting the PU and setting new data into it, then re-saving. ~Lincoln > JPA Setup Command should allow explicitly overwriting existing persistence units > --------------------------------------------------------------------------------- > > Key: FORGE-1670 > URL: https://issues.jboss.org/browse/FORGE-1670 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE > Affects Versions: 2.1.1.Final > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > Labels: Starter > Fix For: 2.x Future > > > JPA Setup should have an "Overwrite" check-box that is enabled only when a name conflict is detected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

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

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1848: -------------------------------------- Same behavior in 1.3.0.Beta3-v20140528-0948-B630 > IDE loose 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.6.0.Final > > > 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)

9 years, 11 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: ------------------------------------------ Correct. Just re-use the functionality without introducing another step. > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1717) Comments in script file

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1717?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1717: ----------------------------------------- Assignee: Lincoln Baxter III > Comments in script file > ----------------------- > > Key: FORGE-1717 > URL: https://issues.jboss.org/browse/FORGE-1717 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > A script file can be loaded in forge console and run as: > run script.forge > It would be nice to support comments there. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1717) Comments in script file

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1717?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1717. ------------------------------------- Fix Version/s: 2.6.0.Final Resolution: Done > Comments in script file > ----------------------- > > Key: FORGE-1717 > URL: https://issues.jboss.org/browse/FORGE-1717 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > A script file can be loaded in forge console and run as: > run script.forge > It would be nice to support comments there. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1716) Specify package, in addition to class name, for generating JSF scaffolds

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1716?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1716. ------------------------------------- Fix Version/s: 2.6.0.Final Resolution: Done > Specify package, in addition to class name, for generating JSF scaffolds > ------------------------------------------------------------------------ > > Key: FORGE-1716 > URL: https://issues.jboss.org/browse/FORGE-1716 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > The following command need a specific class name: > scaffold-generate --targets org.forge.samples.javaee.entities.Author > There should be an option to specify a package such as: > scaffold-generate --targets org.forge.samples.javaee.entities.* -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1716) Specify package, in addition to class name, for generating JSF scaffolds

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1716?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1716: ----------------------------------------- Assignee: Lincoln Baxter III > Specify package, in addition to class name, for generating JSF scaffolds > ------------------------------------------------------------------------ > > Key: FORGE-1716 > URL: https://issues.jboss.org/browse/FORGE-1716 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > The following command need a specific class name: > scaffold-generate --targets org.forge.samples.javaee.entities.Author > There should be an option to specify a package such as: > scaffold-generate --targets org.forge.samples.javaee.entities.* -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

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

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] Matej Briskar edited comment on FORGE-1855 at 5/29/14 6:55 AM: --------------------------------------------------------------- However, the singleton instance itself needs to be saved somewhere. What about changing the {{interface org.jboss.forge.furnace.addons.Addon}} and adding there methods {{getSingletonInstances(), add/createSingletonInstance()}} ? was (Author: mbriskar): However, the singleton instance itself needs to be saved somewhere. What about changing the {{interface org.jboss.forge.furnace.addons.Addon}} and adding there a method {{getSingletonInstances()}} ? > 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)

9 years, 11 months

1
0
0 / 0

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

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] Matej Briskar edited comment on FORGE-1855 at 5/29/14 6:46 AM: --------------------------------------------------------------- However, the singleton instance itself needs to be saved somewhere. What about changing the {{interface org.jboss.forge.furnace.addons.Addon}} and adding there a method {{getSingletonInstances()}} ? was (Author: mbriskar): However, the singleton instance itself needs to be saved somewhere. What about changing the `interface org.jboss.forge.furnace.addons.Addon` and adding there a method `getSingletonInstances()` ? > 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)

9 years, 11 months

1
0
0 / 0

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

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] Matej Briskar commented on FORGE-1855: -------------------------------------- However, the singleton instance itself needs to be saved somewhere. What about changing the `interface org.jboss.forge.furnace.addons.Addon` and adding there a method `getSingletonInstances()` ? > 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)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014