November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-833) java new-field improvements

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-833?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-833: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > java new-field improvements > --------------------------- > > Key: FORGE-833 > URL: https://issues.jboss.org/browse/FORGE-833 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Labels: starter > Fix For: 2.x Future > > > It should be possible to add getters and setters when a new field is created using the following command: > {code} > java new-field --named partType --type ~.model.PartType --accessType PRIVATE --asJavaBean > {code} > Where: > - named: The field name > - type: the field type > - accessModifier: The access modifier of this field: (PUBLIC,PRIVATE,PROTECTED,PACKAGE) > - asJavaBean: generate getters and setters -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-911) Scaffolding from a Join table with more than two primary key columns is not supported

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-911?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-911: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Scaffolding from a Join table with more than two primary key columns is not supported > ------------------------------------------------------------------------------------- > > Key: FORGE-911 > URL: https://issues.jboss.org/browse/FORGE-911 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final, 1.3.0.Final > Environment: Linux 3.8 - Firefox - MySQL 5.5 - PostgreSQl 9.1 > Reporter: Hanine Hanynowsky > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > Using JForge (latest version); one will have a hibernate error complaining about the M2M join table (linking two objects) having more than 2 key columns. > Naturally, if you join a table with one key column with a another table with a composite primary key (two columns key), in order to get a Many to Many relationship, you'll end up with a join table that has three key columns. > > When Forge finished scaffolding no error is displayed. You get the error when deploying to the container (JBoss as 7.1.1 for example). And the app is not deployed (rolled back). > > Is this a bug? A feature request? > > It seems to me that with the EmbeddedId bug, this one is also serious stuff!! -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-823) The REST plugin should generate resources for entities with non-basic Id types

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-823?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-823: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > The REST plugin should generate resources for entities with non-basic Id types > ------------------------------------------------------------------------------ > > Key: FORGE-823 > URL: https://issues.jboss.org/browse/FORGE-823 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Only JPA entities having Ids of type - Boolean, Byte, Double, Float, Integer, Long, Short and String, are eligible to have resources generated. Non-basic types like Embedded Ids cannot have resources generated. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-691) scaffolding does not support entities using a manytomany relationship with a join table

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-691?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-691: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > scaffolding does not support entities using a manytomany relationship with a join table > --------------------------------------------------------------------------------------- > > Key: FORGE-691 > URL: https://issues.jboss.org/browse/FORGE-691 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Reporter: Kevin Hooke > Fix For: 2.x Future > > > using field with a relationship type of manytomany does not give the option to generate the relationship using a join table. If you map this relationship by hand with JPA annotations using oneToMany from either side to an association entity, Forge scaffolding does not know how to generate view pages to handle creation of the relationship. It currently attempts to populate a list to allow the user to select an instance of the association class, which doesn't make any sense. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-152) Plugin to secure application

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-152?page=com.atlassian.jira.... ] Lincoln Baxter III moved FORGE-821 to FORGEPLUGINS-152: ------------------------------------------------------- Project: Forge Plugins (was: Forge) Key: FORGEPLUGINS-152 (was: FORGE-821) Affects Version/s: (was: 1.2.2.Final) Component/s: (was: Java EE APIs) (was: Builtin Plugins) Fix Version/s: (was: 2.x Future) > Plugin to secure application > ---------------------------- > > Key: FORGEPLUGINS-152 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-152 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: George Gastaldi > Labels: starter > > The plugin should primarily: > - Add a <security-constraint> entry to the web.xml file. > - Introduce a SecurityFacet for interoperability with other plugins > - The ScaffoldPlugin could create entries for the login and login-error pages if the SecurityFacet is enabled in the current project -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-882) The entity plugin should support addition of newly created entities to a persistence unit

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-882?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-882: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > The entity plugin should support addition of newly created entities to a persistence unit > ----------------------------------------------------------------------------------------- > > Key: FORGE-882 > URL: https://issues.jboss.org/browse/FORGE-882 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > The entity plugin just creates a new JPA entity, but it does not offer to add the newly created entity to a persistence unit. There is an underlying assumption that the PU includes unlisted classes, whereas the opposite could be true. > It is therefore desired that the entity plugin should either prompt the user to add the new entity to a PU (if there are multiple PUs), or should perhaps add the entity to an existing PU if it is the only one in the project configured to exclude unlisted classes. > Note that these are suggestions and the feature could be implemented in a suitable way to allow entities to be added to PUs. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-899) Add support to generate REST resources that issue HTTP cache headers

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-899?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-899: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Add support to generate REST resources that issue HTTP cache headers > -------------------------------------------------------------------- > > Key: FORGE-899 > URL: https://issues.jboss.org/browse/FORGE-899 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > This is more or less an issue that affects HTML5 scaffolding that depends on the generated REST resources. > Browsers like IE8/9/10 etc. aggressively cache responses unless instructed to not do so, ensuring that clients (like the scaffolded apps) do not issue additional requests beyond the first one, until the cache is cleared, or until the REST resources are modified. > We should therefore allow (possibly as an option) the generation of code within the REST resources that issue HTTP Cache-Control headers. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-812) Create Hamcrest Matchers for use in the Forge Test Harness

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-812?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-812: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Create Hamcrest Matchers for use in the Forge Test Harness > ---------------------------------------------------------- > > Key: FORGE-812 > URL: https://issues.jboss.org/browse/FORGE-812 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > We could use specialized Hamcrest matchers for use in the test harness. For example, comparing expected and actual file contents of the generated scaffold could benefit from a matcher that can pinpoint mismatches, instead of relying on String comparisons. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-368) Return list of properties based on higher-level understanding

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-368?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-368: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Return list of properties based on higher-level understanding > ------------------------------------------------------------- > > Key: FORGE-368 > URL: https://issues.jboss.org/browse/FORGE-368 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Richard Kennard > Fix For: 2.x Future > > > Hi guys, > As I understand it, Forge has an understanding of your project that transcends Java's own understanding. So for example if I say... > field string --named foo > ...Forge knows I'm creating a property, and it creates getters and setters for that property. But later if I do... > org.jboss.forge.parser.java.JavaClass.getMethods() > ...then I get back just normal methods. I'll have to check their signature for 'get' or 'set' to see if they're properties. Equally if I do... > org.jboss.forge.parser.java.JavaClass.getFields() > ...I get back just normal fields. I don't know if these are property fields (and if so, what their corresponding getter/setter methods are) or whether they're just internal fields (and should be ignored). > Is there a recommended way to 'get back out' the list of properties for a class? Something that tells me a) the field; b) the getter; c) the setter? > If it helps, for now I am using a rough implementation at: https://github.com/kennardconsulting/forge/blob/master/scaffold-metawidge... -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-125) Field/Entity plugins should warn when using potential SQL tokens an entity names or field names

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-125?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-125: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Field/Entity plugins should warn when using potential SQL tokens an entity names or field names > ----------------------------------------------------------------------------------------------- > > Key: FORGE-125 > URL: https://issues.jboss.org/browse/FORGE-125 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > It's currently possible to easily create an entity or field that will break JPA because of usage of SQL reserved words. > E.g: "order" or "limit" -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013