January 2014 - forge-issues - Jboss List Archives

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1399?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1399: ---------------------------------------- The command was not supposed to appear and it was fixed in FORGE-1508 > 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.CR2 > 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-1508) CommandFactory should not return UIWIzardStep implementations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1508?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1508. ---------------------------------- Resolution: Done > CommandFactory should not return UIWIzardStep implementations > ------------------------------------------------------------- > > Key: FORGE-1508 > URL: https://issues.jboss.org/browse/FORGE-1508 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.0.0.CR2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > UIWizardStep are not used for direct invocation, hence should not be returned from CommandFactory.getCommands() -- 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-1508) CommandFactory should not return UIWIzardStep implementations

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1508: -------------------------------------- Summary: CommandFactory should not return UIWIzardStep implementations Key: FORGE-1508 URL: https://issues.jboss.org/browse/FORGE-1508 Project: Forge Issue Type: Bug Components: UI - API Affects Versions: 2.0.0.CR2 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Final UIWizardStep are not used for direct invocation, hence should not be returned from CommandFactory.getCommands() -- 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-1479) Explicitly setup in Bean Validation, not in JPA

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1479: ------------------------------------------ Same problem happens with rest. I can run {{rest-endpoint-from-entity}} without {{rest-setup}}. I think either you allow {{jpa-}} commands only if {{jpa-setup}} is executed (and same for rest, soap, constraint...) or you run the {{setup}} on behalf. At the moment, either you are allowed to execute {{setup}} or not, and it works or not. > Explicitly setup in Bean Validation, not in JPA > ----------------------------------------------- > > Key: FORGE-1479 > URL: https://issues.jboss.org/browse/FORGE-1479 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) : > {code} > ***SUCCESS*** Project named 'test' has been created. > [test]$ jpa-new-entity --named Author > [Author.java]$ jpa-new-field --named firstname --length 50 > ***SUCCESS*** Field firstname created > {code} > This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation : > {code} > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-setup > [Author.java]$ constraint-setup > ***SUCCESS*** Bean Validation is installed. > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-add constraint-setup > [Author.java]$ constraint-add --constraint NotNull --onProperty firstname > ***SUCCESS*** Constraint NotNull successfully configured > {code} > if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following : > {code} > servlet-setup > ejb-setup > soap-setup > cdi-setup > jms-setup > rest-setup > jpa-setup > faces-setup > jstl-setup > jta-setup > constraint-setup > {code} > Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}" > That would save some bugs (developers forgetting to setup things), less typing and shorter scripts. -- 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-1453) Cannot scaffold JSF pages using a * target

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1453?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1453: ------------------------------------- Affects Version/s: 2.0.0.CR2 (was: 2.0.0.CR1) > Cannot scaffold JSF pages using a * target > ------------------------------------------ > > Key: FORGE-1453 > URL: https://issues.jboss.org/browse/FORGE-1453 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > When I want to generate JSF pages for each of my entities, I can write the following in Forge 1.x : > {code} > scaffold from-entity ~.model.* ; > {code} > In Forge 2.CR1 I cannot use the '*' and need to specify each entity : > {code} > [TalkEndpoint.java]$ scaffold-generate --targets ~.model.* > Targets must be specified. > [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.* > Targets must be specified. > [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk > ***SUCCESS*** Scaffold was generated successfully. > [TalkEndpoint.java]$ > {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-1453) Cannot scaffold JSF pages using a * target

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1453?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1453: ------------------------------------- Parent Issue: FORGE-1505 (was: FORGE-1387) > Cannot scaffold JSF pages using a * target > ------------------------------------------ > > Key: FORGE-1453 > URL: https://issues.jboss.org/browse/FORGE-1453 > 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 > > > When I want to generate JSF pages for each of my entities, I can write the following in Forge 1.x : > {code} > scaffold from-entity ~.model.* ; > {code} > In Forge 2.CR1 I cannot use the '*' and need to specify each entity : > {code} > [TalkEndpoint.java]$ scaffold-generate --targets ~.model.* > Targets must be specified. > [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.* > Targets must be specified. > [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk > ***SUCCESS*** Scaffold was generated successfully. > [TalkEndpoint.java]$ > {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-1451) Cannot scaffold REST endpoints using a * target

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1451?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1451: ------------------------------------- Parent Issue: FORGE-1505 (was: FORGE-1387) > Cannot scaffold REST endpoints using a * target > ----------------------------------------------- > > Key: FORGE-1451 > URL: https://issues.jboss.org/browse/FORGE-1451 > 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 > > > When I want to generate REST enpoints for each of my entities, I can write the following in Forge 1.x : > {code} > rest endpoint-from-entity ~.model.* ; > {code} > In Forge 2.CR1 I cannot use the '*' and need to specify each entity : > {code} > [Book.java]$ rest-endpoint-from-entity --targets ~.model.* > Targets must be specified. > [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.* > Targets must be specified. > [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk > ***SUCCESS*** Endpoint created > ***SUCCESS*** EJB has been 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-1451) Cannot scaffold REST endpoints using a * target

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1451?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1451: ------------------------------------- Affects Version/s: 2.0.0.CR2 (was: 2.0.0.CR1) > Cannot scaffold REST endpoints using a * target > ----------------------------------------------- > > Key: FORGE-1451 > URL: https://issues.jboss.org/browse/FORGE-1451 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > When I want to generate REST enpoints for each of my entities, I can write the following in Forge 1.x : > {code} > rest endpoint-from-entity ~.model.* ; > {code} > In Forge 2.CR1 I cannot use the '*' and need to specify each entity : > {code} > [Book.java]$ rest-endpoint-from-entity --targets ~.model.* > Targets must be specified. > [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.* > Targets must be specified. > [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk > ***SUCCESS*** Endpoint created > ***SUCCESS*** EJB has been 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-1432) run command is missing (and with it, scripting)

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1432: ------------------------------------- Affects Version/s: 2.0.0.CR2 (was: 2.0.0.Beta4) > 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.0.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, 2 months

1
0
0 / 0

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

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1432: ------------------------------------- Parent Issue: FORGE-1505 (was: FORGE-1433) > 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.Beta4 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.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, 2 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