January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1456) project-add/remove-repository command is missing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1456?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1456: -------------------------------------- Assignee: George Gastaldi > project-add/remove-repository command is missing > ------------------------------------------------ > > Key: FORGE-1456 > URL: https://issues.jboss.org/browse/FORGE-1456 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.x Future > > > This command is similar to the following on in Forge 1.x > {code} > project add-repository primefaces-repo http://repository.primefaces.org > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1499) Rename endpoint to resource in the context of REST commands

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1499: -------------------------------------- Summary: Rename endpoint to resource in the context of REST commands Key: FORGE-1499 URL: https://issues.jboss.org/browse/FORGE-1499 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 2.0.0.CR1 Reporter: Vineet Reynolds Assignee: Vineet Reynolds The word "endpoint" is a remnant of SOAP and makes less sense in REST discussions. We should instead reword it as "resource". -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1399) Cannot create a relationship between two entities

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1399?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1399: ------------------------------------- Priority: Critical (was: Major) > Cannot create a relationship between two entities > ------------------------------------------------- > > Key: FORGE-1399 > URL: https://issues.jboss.org/browse/FORGE-1399 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > I've created a {{Country}} entity and then a {{Customer}}. When I create a relationship between both, I have an error : > {code} > [Customer.java]$ jpa-new-field --named country --entity org.agoncal.application.petstore.model.Country --relationshipType Many-to-One > ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed. > [Customer.java]$ jpa-setup > ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed. > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1456) project-add/remove-repository command is missing

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1456?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1456: ------------------------------------- Summary: project-add/remove-repository command is missing (was: project-add-repository command is missing) > project-add/remove-repository command is missing > ------------------------------------------------ > > Key: FORGE-1456 > URL: https://issues.jboss.org/browse/FORGE-1456 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > This command is similar to the following on in Forge 1.x > {code} > project add-repository primefaces-repo http://repository.primefaces.org > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1498. ------------------------------------- Resolution: Won't Fix I don't think that we should implement this. If ordering is required, it should be enforced by the interface of the Service being requested. This isn't something that we should try to do in Furnace. Re-open if you really disagree :) > Allow ordering in the lookup of services in AddonRegistry > --------------------------------------------------------- > > Key: FORGE-1498 > URL: https://issues.jboss.org/browse/FORGE-1498 > Project: Forge > Issue Type: Enhancement > Components: Brainstorming, Furnace (Container) > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > Some services may require to be executed before others. It would be nice if the container could order these services while an iteraction of an {{Imported}} object happens. This ordering may happen based on an annotation or an interface. > Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the {{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to exist before other UIContextListeners are fired. > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1498: ---------------------------------------- Perhaps we could assume that Comparable instances could be automatically ordered in the Imported.iterator(). Then it could be up to the implementation to decide which strategy to use for ordering. WDYT? ----- Mensagem original ----- De: "Lincoln Baxter III (JIRA)" <issues(a)jboss.org> Para: forge-issues(a)lists.jboss.org Enviadas: Domingo, 26 de janeiro de 2014 16:59:29 Assunto: [forge-issues] [JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry [ https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1498: ------------------------------------------- Ah, so you're saying that you want the listeners to be ordered? Do we ever need to execute them in order? If so, we should add a priority() method and/or make them Comparable/Provide a comparator. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -- 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 _______________________________________________ forge-issues mailing list forge-issues(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-issues > Allow ordering in the lookup of services in AddonRegistry > --------------------------------------------------------- > > Key: FORGE-1498 > URL: https://issues.jboss.org/browse/FORGE-1498 > Project: Forge > Issue Type: Enhancement > Components: Brainstorming, Furnace (Container) > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > Some services may require to be executed before others. It would be nice if the container could order these services while an iteraction of an {{Imported}} object happens. This ordering may happen based on an annotation or an interface. > Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the {{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to exist before other UIContextListeners are fired. > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1498: ------------------------------------------- Ah, so you're saying that you want the listeners to be ordered? Do we ever need to execute them in order? If so, we should add a priority() method and/or make them Comparable/Provide a comparator. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." > Allow ordering in the lookup of services in AddonRegistry > --------------------------------------------------------- > > Key: FORGE-1498 > URL: https://issues.jboss.org/browse/FORGE-1498 > Project: Forge > Issue Type: Enhancement > Components: Brainstorming, Furnace (Container) > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > Some services may require to be executed before others. It would be nice if the container could order these services while an iteraction of an {{Imported}} object happens. This ordering may happen based on an annotation or an interface. > Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the {{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to exist before other UIContextListeners are fired. > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1498: -------------------------------------- Summary: Allow ordering in the lookup of services in AddonRegistry Key: FORGE-1498 URL: https://issues.jboss.org/browse/FORGE-1498 Project: Forge Issue Type: Enhancement Components: Brainstorming, Furnace (Container) Affects Versions: 2.0.0.CR1 Reporter: George Gastaldi Fix For: 2.x Future Some services may require to be executed before others. It would be nice if the container could order these services while an iteraction of an {{Imported}} object happens. This ordering may happen based on an annotation or an interface. Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the {{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to exist before other UIContextListeners are fired. -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1498: ---------------------------------------- The issue is regarding the order specified by the iterator returned in Imported.iterator(). In some scenarios, like the one described in the issue, the consumer is unaware of how to order the returned services. > Allow ordering in the lookup of services in AddonRegistry > --------------------------------------------------------- > > Key: FORGE-1498 > URL: https://issues.jboss.org/browse/FORGE-1498 > Project: Forge > Issue Type: Enhancement > Components: Brainstorming, Furnace (Container) > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > Some services may require to be executed before others. It would be nice if the container could order these services while an iteraction of an {{Imported}} object happens. This ordering may happen based on an annotation or an interface. > Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the {{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to exist before other UIContextListeners are fired. > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1498) Allow ordering in the lookup of services in AddonRegistry

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1498: ------------------------------------------- Not sure I really follow this issue. What is the problem? Service lookups just return objects, so activation order could be handled by the consumer. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." > Allow ordering in the lookup of services in AddonRegistry > --------------------------------------------------------- > > Key: FORGE-1498 > URL: https://issues.jboss.org/browse/FORGE-1498 > Project: Forge > Issue Type: Enhancement > Components: Brainstorming, Furnace (Container) > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > Some services may require to be executed before others. It would be nice if the container could order these services while an iteraction of an {{Imported}} object happens. This ordering may happen based on an annotation or an interface. > Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the {{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to exist before other UIContextListeners are fired. > -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014