January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1454) maven-remove-dependency command is missing

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1454: ---------------------------------------- Summary: maven-remove-dependency command is missing Key: FORGE-1454 URL: https://issues.jboss.org/browse/FORGE-1454 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 remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ; {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-1453) Cannot scaffold JSF pages using a * target

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1453: ---------------------------------------- Summary: 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 Fix For: 2.0.0.CR1 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1452) web.xml is Servlet 3.0 instead of 3.1

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1452: ---------------------------------------- Summary: web.xml is Servlet 3.0 instead of 3.1 Key: FORGE-1452 URL: https://issues.jboss.org/browse/FORGE-1452 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves Fix For: 2.x Future When creating entities, adding constraints, scaffolding REST and JSF, we end up with Java EE 7 deployment descriptors (e.g. {{beans.xml}} is in 1.1, {{faces-config.xml}} is in 2.2.....) except for the {{web.xml}} that is still in 3.0 instead of 3.1 -- 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-1422) REST addon should support generation of exception mappers for validation errors

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1422: ---------------------------------------- [~epbernard], [~ron_sigal], thanks for your comments. I think this feature is exactly what would help here, with of course client-side logic to parse the JSON and display errors in the UI. The reason why the generated REST resources dont use RESTEasy is because the generator is designed to emit code with only Java EE 6/7 APIs. All of the commands in the Java EE addon (of which the REST command is one) are designed this way (to use only the standards). I'd say that based on your comments, it would be beneficial to create a RESTEasy addon in Forge that wouldn't be constrained by this limitation. The other alternative is to perform contextual code generation based on the presence of a JBoss BOM, but we haven't come anywhere close to realizing this. And if we do this the lazy way (by hoisting it into the Java EE addon) it might bloat the addon, and also result in people demanding support for other JAX-RS stacks. > REST addon should support generation of exception mappers for validation errors > ------------------------------------------------------------------------------- > > Key: FORGE-1422 > URL: https://issues.jboss.org/browse/FORGE-1422 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Currently a HTTP 500 response is generated for validation errors encountered during processing of POST/PUT requests that create or update JPA entities. The 500 response contains a stacktrace that cannot be parsed by clients to evaluate what failed. > We should generate exception mappers that can map Bean validation errors to help generate parseable responses (for the REST clients). -- 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-1451) Cannot scaffold REST endpoints using a * target

by Antonio Goncalves (JIRA)

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

1
0
0 / 0

[JBoss JIRA] (FORGE-1422) REST addon should support generation of exception mappers for validation errors

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ] Ron Sigal commented on FORGE-1422: ---------------------------------- The reporting format of constraint violations in Resteasy is described here: http://docs.jboss.org/resteasy/docs/3.0.6.Final/userguide/html/Validation.... The report, which can be transmitted in XML, JSON, and text format, contains four fields per violation: # type of violated constraint # path to violating element # error message # description of value in error For example: {noformat} [FIELD] [s] [size must be between 2 and 4] [a] [PROPERTY] [t] [size must be between 3 and 5] [z] [CLASS] [] [Concatenation of s and t must have length > 5] [org.jboss.resteasy.validation.TestResource@68467a6f] [PARAMETER] [test.<cross-parameter>] [Parameters must total <= 7] [[5, 7]] [RETURN_VALUE] [g.<return value>] [size must be between 2 and 4] [abcde] {noformat} > REST addon should support generation of exception mappers for validation errors > ------------------------------------------------------------------------------- > > Key: FORGE-1422 > URL: https://issues.jboss.org/browse/FORGE-1422 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Currently a HTTP 500 response is generated for validation errors encountered during processing of POST/PUT requests that create or update JPA entities. The 500 response contains a stacktrace that cannot be parsed by clients to evaluate what failed. > We should generate exception mappers that can map Bean validation errors to help generate parseable responses (for the REST clients). -- 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-1450) Cannot create an enum attribute on an Entity

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1450: ---------------------------------------- Summary: Cannot create an enum attribute on an Entity Key: FORGE-1450 URL: https://issues.jboss.org/browse/FORGE-1450 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 {{Language}} enum (with {{java-new-enum}}) and then I want my entity {{Book}} to have an attribute of type {{Language}}. In Forge 1.x I would do : {code} field custom --named language --type org.javaone.javaee7.model.Language.java ; {code} There is no such {{custom}} attribute in Forge 2.x and the following doesn't work : {code} jpa-new-field --named language --typeName org.javaone.javaee7.model.Language.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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1254) calling setStatic(true) on a static method add keyword "static" twice

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1254?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1254. ---------------------------------- Resolution: Done > calling setStatic(true) on a static method add keyword "static" twice > --------------------------------------------------------------------- > > Key: FORGE-1254 > URL: https://issues.jboss.org/browse/FORGE-1254 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.4.1.Final > Reporter: Michael Schwartz > Assignee: Salem Elrahal > Priority: Minor > Fix For: 1.4.4.Final, 2.0.0.CR1 > > > Testclass: > {code:java} > class Tester() { > static void testit() { > } > } > {code} > Forge: > {code:java} > Method<?> method = entityclass.getMethod("testit"); > method.setStatic(true); > // save the class > {code} > yields to: > {code} > static static void testit() {} > {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-1449) Copy/pasting several line in the Forge shell hangs

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1449?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1449: ------------------------------------- Fix Version/s: 2.x Future > Copy/pasting several line in the Forge shell hangs > -------------------------------------------------- > > Key: FORGE-1449 > URL: https://issues.jboss.org/browse/FORGE-1449 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I have a few commands in a text file : > {code} > jpa-new-entity --named Book ; > jpa-new-field --named isbn ; > jpa-new-field --named title ; > jpa-new-field --named author ; > jpa-new-field --named description --length 2000 ; > {code} > When I copy paste these 5 lines in the Forge shell I get : > {code} > [Book.java]$ jpa-new-field --named isbn ; > ***SUCCESS*** Field isbn created > [Book.java]$ > {code} > The first two lines have been executed and then the shell hangs. CTRL+C doesn't work, I can't type anything (e.g. exit) so I need to kill the process -- 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-1449) Copy/pasting several line in the Forge shell hangs

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1449: ---------------------------------------- Summary: Copy/pasting several line in the Forge shell hangs Key: FORGE-1449 URL: https://issues.jboss.org/browse/FORGE-1449 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR1 Reporter: Antonio Goncalves I have a few commands in a text file : {code} jpa-new-entity --named Book ; jpa-new-field --named isbn ; jpa-new-field --named title ; jpa-new-field --named author ; jpa-new-field --named description --length 2000 ; {code} When I copy paste these 5 lines in the Forge shell I get : {code} [Book.java]$ jpa-new-field --named isbn ; ***SUCCESS*** Field isbn created [Book.java]$ {code} The first two lines have been executed and then the shell hangs. CTRL+C doesn't work, I can't type anything (e.g. exit) so I need to kill the process -- 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