March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1599) Introduce a cache addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1599?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1599: ---------------------------------------- Perhaps Infinispan related code may be introduced through an SPI. > Introduce a cache addon > ----------------------- > > Key: FORGE-1599 > URL: https://issues.jboss.org/browse/FORGE-1599 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: George Gastaldi > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > This would allow other addons to cache state. It should allow individual configurations of each cache. > There should also have a CacheFactory, to allow creation of caches on-demand. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1599) Introduce a cache addon

by Adam Wyłuda (JIRA)

[ https://issues.jboss.org/browse/FORGE-1599?page=com.atlassian.jira.plugin... ] Adam Wyłuda commented on FORGE-1599: ------------------------------------ The simplest way to make this addon is to create empty addon with JCache (JSR-107) as compile dependency in API and infinispan-cdi dependency in impl. That would require no code except tests. But it might be also worth considering to create our own wrapper instead of using JCache API, as it doesn't allow using custom Infinispan options. Here are all cache options from JCache: http://javadoc4.caucho.com/javax/cache/CacheBuilder.html > Introduce a cache addon > ----------------------- > > Key: FORGE-1599 > URL: https://issues.jboss.org/browse/FORGE-1599 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: George Gastaldi > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > This would allow other addons to cache state. It should allow individual configurations of each cache. > There should also have a CacheFactory, to allow creation of caches on-demand. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1625) Prevent UIWizards from being merged into dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1625?page=com.atlassian.jira.plugin... ] George Gastaldi edited comment on FORGE-1625 at 3/3/14 1:33 PM: ---------------------------------------------------------------- Shoud an exception be thrown when an UIWizard is added? was (Author: gastaldi): Shoud an exception be thrown when a UIWizard is added? > Prevent UIWizards from being merged into dialogs > ------------------------------------------------ > > Key: FORGE-1625 > URL: https://issues.jboss.org/browse/FORGE-1625 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.1.1.Final > Reporter: Vineet Reynolds > > When I add multiple UICommand and UIWizard instances to create a single dialog page, like so: > {noformat} > NavigationResultBuilder builder = NavigationResultBuilder.create(); > builder.add(getMetadata(uiContext), setupFlow); > return builder.build(); > {noformat} > the wizard pages are also added to the dialog page. This results in erroneous behavior since only the first page of the wizard is added and displayed. The second and subsequent pages of a wizard are omitted (even from execution). > Since it is obvious that the next page in a wizard cannot be determined statically, and should determined at runtime, we must prevent wizards from being merged into a single page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1625) Prevent UIWizards from being merged into dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1625?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1625: ----------------------------------- Priority: Minor (was: Major) > Prevent UIWizards from being merged into dialogs > ------------------------------------------------ > > Key: FORGE-1625 > URL: https://issues.jboss.org/browse/FORGE-1625 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.1.1.Final > Reporter: Vineet Reynolds > Priority: Minor > > When I add multiple UICommand and UIWizard instances to create a single dialog page, like so: > {noformat} > NavigationResultBuilder builder = NavigationResultBuilder.create(); > builder.add(getMetadata(uiContext), setupFlow); > return builder.build(); > {noformat} > the wizard pages are also added to the dialog page. This results in erroneous behavior since only the first page of the wizard is added and displayed. The second and subsequent pages of a wizard are omitted (even from execution). > Since it is obvious that the next page in a wizard cannot be determined statically, and should determined at runtime, we must prevent wizards from being merged into a single page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1625) Prevent UIWizards from being merged into dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1625?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1625: ---------------------------------------- Shoud an exception be thrown when a UIWizard is added? > Prevent UIWizards from being merged into dialogs > ------------------------------------------------ > > Key: FORGE-1625 > URL: https://issues.jboss.org/browse/FORGE-1625 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.1.1.Final > Reporter: Vineet Reynolds > > When I add multiple UICommand and UIWizard instances to create a single dialog page, like so: > {noformat} > NavigationResultBuilder builder = NavigationResultBuilder.create(); > builder.add(getMetadata(uiContext), setupFlow); > return builder.build(); > {noformat} > the wizard pages are also added to the dialog page. This results in erroneous behavior since only the first page of the wizard is added and displayed. The second and subsequent pages of a wizard are omitted (even from execution). > Since it is obvious that the next page in a wizard cannot be determined statically, and should determined at runtime, we must prevent wizards from being merged into a single page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1625) Prevent UIWizards from being merged into dialogs

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1625: -------------------------------------- Summary: Prevent UIWizards from being merged into dialogs Key: FORGE-1625 URL: https://issues.jboss.org/browse/FORGE-1625 Project: Forge Issue Type: Feature Request Components: UI - API Affects Versions: 2.1.1.Final Reporter: Vineet Reynolds When I add multiple UICommand and UIWizard instances to create a single dialog page, like so: {noformat} NavigationResultBuilder builder = NavigationResultBuilder.create(); builder.add(getMetadata(uiContext), setupFlow); return builder.build(); {noformat} the wizard pages are also added to the dialog page. This results in erroneous behavior since only the first page of the wizard is added and displayed. The second and subsequent pages of a wizard are omitted (even from execution). Since it is obvious that the next page in a wizard cannot be determined statically, and should determined at runtime, we must prevent wizards from being merged into a single page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1624) Create JPASetupWizard interface so JPA setup can be invoked from other plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1624?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1624. ---------------------------------- Assignee: Shane Bryzak Fix Version/s: 2.1.2.Final Resolution: Done > Create JPASetupWizard interface so JPA setup can be invoked from other plugins > ------------------------------------------------------------------------------ > > Key: FORGE-1624 > URL: https://issues.jboss.org/browse/FORGE-1624 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Affects Versions: 2.1.1.Final > Reporter: Shane Bryzak > Assignee: Shane Bryzak > Fix For: 2.1.2.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1624) Create JPASetupWizard interface so JPA setup can be invoked from other plugins

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/FORGE-1624?page=com.atlassian.jira.plugin... ] Shane Bryzak updated FORGE-1624: -------------------------------- Git Pull Request: https://github.com/forge/core/pull/393 Pull request sent. > Create JPASetupWizard interface so JPA setup can be invoked from other plugins > ------------------------------------------------------------------------------ > > Key: FORGE-1624 > URL: https://issues.jboss.org/browse/FORGE-1624 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Affects Versions: 2.1.1.Final > Reporter: Shane Bryzak > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1624) Create JPASetupWizard interface so JPA setup can be invoked from other plugins

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/FORGE-1624?page=com.atlassian.jira.plugin... ] Shane Bryzak updated FORGE-1624: -------------------------------- Affects Version/s: 2.1.1.Final Component/s: Java EE > Create JPASetupWizard interface so JPA setup can be invoked from other plugins > ------------------------------------------------------------------------------ > > Key: FORGE-1624 > URL: https://issues.jboss.org/browse/FORGE-1624 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Affects Versions: 2.1.1.Final > Reporter: Shane Bryzak > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1432: ------------------------------------------- Okay. Looks like there are still bugs. I'll take a look tomorrow :) Sorry! > run command is missing (and with it, scripting) > ----------------------------------------------- > > Key: FORGE-1432 > URL: https://issues.jboss.org/browse/FORGE-1432 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.1.0.Final > > > I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 : > {code} > @/* ====================================== */; > @/* == From Java EE 6 to 7 Dependencies == */; > @/* ====================================== */; > project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ; > project remove-dependency javax.validation:validation-api ; > project remove-dependency org.hibernate:hibernate-validator ; > project remove-dependency javax.enterprise:cdi-api ; > project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ; > project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ; > project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ; > project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ; > project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ; > project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ; > project add-dependency javax:javaee-api:7.0:provided ; > project add-dependency org.primefaces:primefaces:4.0 ; > project add-repository primefaces-repo http://repository.primefaces.org ; > {code} > I have other scripts like that. The good this is, without leaving the console, I can write : > {code} > [Forge]$ run script1.fsh > [Forge]$ run script2.fsh > [Forge]$ run script3.fsh > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014