January 2014 - forge-issues - Jboss List Archives

[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: ------------------------------------- Affects Version/s: 2.0.0.CR1 (was: 2.0.0.Beta4) > 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 > 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, 3 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 commented on FORGE-1399: ------------------------------------------ In the latest SNAPSHOT I get a similar exception : {code} [Book.java]$ jpa-new-field --named authors --entity com.pluralsight.persistence.module07.model.Author --relationshipType One-to-Many ***ERROR*** org.xadisk.filesystem.exceptions.InsufficientPermissionOnFileException: Permission of type [READ_FILE] is needed over the file/directory with path [/Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/String.java] for the i/o operation to succeed. {code} It still wants to create a {{String}} class, wonder why > 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.Beta4 > Reporter: Antonio Goncalves > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1485) Rename --target for faces-new-validator-method command

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1485: ---------------------------------------- Summary: Rename --target for faces-new-validator-method command Key: FORGE-1485 URL: https://issues.jboss.org/browse/FORGE-1485 Project: Forge Issue Type: Sub-task Components: UI - Shell Reporter: Antonio Goncalves Fix For: 2.x Future The {{faces-new-validator-method}} has a {{--target}} parameter but without TAB completion, we don't know what this actually targets. When we hit TAB we get : {code} [Language.java]$ faces-new-validator-method --target Author.java Item.java Language.java Publisher.java {code} Most of the {{target}} parameters are suffixed to be more explicit : {code} entities-from-tables --targetPackage faces-new-converter --targetPackage project-new --targetLocation {code} So I would rename it {{targetClass}} : {code} faces-new-validator-method --targetClass {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1484) --packageName should be renamed --targetPackage

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1484: ---------------------------------------- Summary: --packageName should be renamed --targetPackage Key: FORGE-1484 URL: https://issues.jboss.org/browse/FORGE-1484 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future The {{java}} commands have a {{--packageName}} parameter and should be renamed in {{--targetPackage}} : {code} java-new-annotation --packageName java-new-class --packageName java-new-enum --packageName java-new-interface --packageName {code} Most of the other commands use {{target}} : {code} entities-from-tables --targetPackage faces-new-converter --targetPackage faces-new-validator --targetPackage addon-new-command --targetPackage {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1483) Rename entities-from-tables comment

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1483: ---------------------------------------- Summary: Rename entities-from-tables comment Key: FORGE-1483 URL: https://issues.jboss.org/browse/FORGE-1483 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future The command {{entities-from-tables}} is related to jpa and should be called something like : {code} jpa-generate-from-tables jpa-scaffold-from-tables {code} We talked about the difference between generate and scaffold in the ML. Lincoln defines scaffolding for the UI, so in this case {{generate}} is more appropriate. -- 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-1482) Being able to turn off verbose output

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1482: ---------------------------------------- Summary: Being able to turn off verbose output Key: FORGE-1482 URL: https://issues.jboss.org/browse/FORGE-1482 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future In [FORGE-1439] the verbose output has been implemented using the command : {code} transaction-track-changes {code} But once it's on, there is no way to turn it off. You can add a parameter to it {code} transaction-track-changes --verbose true transaction-track-changes --verbose false {code} I would have use the {{export}} for this matter {code} export VERBOSE_OUTPUT= true export VERBOSE_OUTPUT= false {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1481) Code completion missing for --packageName on java-new-enum

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1481: ---------------------------------------- Summary: Code completion missing for --packageName on java-new-enum Key: FORGE-1481 URL: https://issues.jboss.org/browse/FORGE-1481 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future TAB code completion is missing for {{--packageName}} : {code} java-new-enum --named Language --packageName TAB {code} When pressing TAB, nothing happens. I would expect to have code completion with existing packages. -- 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-1480) Mulitple --value parameters for Min constraint

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1480: ---------------------------------------- Summary: Mulitple --value parameters for Min constraint Key: FORGE-1480 URL: https://issues.jboss.org/browse/FORGE-1480 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future When you create a {{Min}} constraint (it's ok for {{Max}}), you can add as many {{--value}} attributes you want. You should only have *one* {{--value}} : {code} [Item.java]$ constraint-add --onProperty description --constraint Min -- --message --onAccessor --value --payload --groups [Item.java]$ constraint-add --onProperty description --constraint Min --value -- --message --value --payload --groups [Item.java]$ constraint-add --onProperty description --constraint Min --value -- --message --value --payload --groups [Item.java]$ constraint-add --onProperty description --constraint Min --value 12 --value 13 -- --message --payload --groups [Item.java]$ constraint-add --onProperty description --constraint Min --value 12 --value 13 -- {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1479: ---------------------------------------- Summary: 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.CR1 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1478) Being able to have inheritance in JPA

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1478: ---------------------------------------- Summary: Being able to have inheritance in JPA Key: FORGE-1478 URL: https://issues.jboss.org/browse/FORGE-1478 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future JPA inheritance is really needed. It would be good to have an option to create an entity that inherits either from a java class, an entity or a mapped superclass. Something like : {code} jpa-new-entity --named Customer --extends Person {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, 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