August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1083) Faces scaffold is activated even though it was not setup

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1083?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1083. ---------------------------------- Assignee: Vineet Reynolds Fix Version/s: 1.3.4.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/b265a05fa73579958125c83f2357d8102958... The fix was to verify whether the static files were available. This results in a warning being displayed that the Faces scaffold was not installed cleanly, since the scaffold plugins fire an InstallFacets event before the facet has been truly installed. This would be rectified in FORGE-1098 when the setup procedure will be revised. > Faces scaffold is activated even though it was not setup > -------------------------------------------------------- > > Key: FORGE-1083 > URL: https://issues.jboss.org/browse/FORGE-1083 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > On opening the TicketMonster sources and executing {{project list-facets}}, the Faces scaffolding facet is shown as installed. This is even though {{scaffold setup}} was not executed previously, and also despite the lack of artifacts required by the Faces scaffold. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1098) Scaffold setup command does not setup the chosen scaffold

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1098: -------------------------------------- Summary: Scaffold setup command does not setup the chosen scaffold Key: FORGE-1098 URL: https://issues.jboss.org/browse/FORGE-1098 Project: Forge Issue Type: Bug Components: Scaffold Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Priority: Blocker On running the {{scaffold setup}} or {{scaffold-x setup}} commands, the default Faces scaffolding provider is chosen even though a different provider was to be installed. As an example, instead of setting up the AngularJS provider the Faces provider is installed: {noformat} [ticket-monster] demo $ scaffold-x setup --scaffoldType angularjs ***INFO*** Using currently installed scaffold [faces] ? [/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.html] File exists, overwrite? [Y/n] Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/favicon.ico Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/scaffold/paginator.xhtml Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/scaffold/pageTemplate.xhtml Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.html Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.xhtml Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/error.xhtml Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/add.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/bootstrap.css Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/false.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/favicon.ico Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/forge-logo.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/forge-style.css Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/remove.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/search.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/true.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/jboss-community.png Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/WEB-INF/web.xml {noformat} -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1097) Forge Java parser fails to distinguish between several fields in a FieldDeclaration

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1097?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1097. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 1.3.4.Final Resolution: Done > Forge Java parser fails to distinguish between several fields in a FieldDeclaration > ----------------------------------------------------------------------------------- > > Key: FORGE-1097 > URL: https://issues.jboss.org/browse/FORGE-1097 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Priority: Critical > Fix For: 1.3.4.Final > > > Consider the following test: > {code:java} > @Test > public void testFieldTypesByteExtraDimensionDeclarationTest() > { > final JavaClass javaClass = JavaParser.create(JavaClass.class); > final Field<JavaClass> field = javaClass.addField("public byte content1[], content2;"); > Assert.assertEquals("content1", field.getName()); > Assert.assertEquals("byte[]", field.getQualifiedType()); > Assert.assertEquals("byte[]", field.getType()); > Assert.assertTrue(field.getTypeInspector().isArray()); > } > {code} > The above shown behavior is obviously incorrect since the second 'field' named content2 is 'lost' and so is information about it's type. > The underlying issue is that of the parser treating the FieldDeclaration as that belonging to a single field, whereas there may be several VariableDeclarationFragments within the same FieldDeclaration. Ideally, this should be solved by introducing a new type like {{Variable}} to identify individual variables in the declaration, or to change the semantic of {{Field}} to refer to the individual variables. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1083) Faces scaffold is activated even though it was not setup

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1083?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1083: ----------------------------------- Description: On opening the TicketMonster sources and executing {{project list-facets}}, the Faces scaffolding facet is shown as installed. This is even though {{scaffold setup}} was not executed previously, and also despite the lack of artifacts required by the Faces scaffold. (was: On opening the TicketMonster sources and executing {{project list-facets}}, the Faces scaffolding facet is shown as installed. This is even though {{scaffold setup}] was not executed previously, and also despite the lack of artifacts required by the Faces scaffold.) > Faces scaffold is activated even though it was not setup > -------------------------------------------------------- > > Key: FORGE-1083 > URL: https://issues.jboss.org/browse/FORGE-1083 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > > On opening the TicketMonster sources and executing {{project list-facets}}, the Faces scaffolding facet is shown as installed. This is even though {{scaffold setup}} was not executed previously, and also despite the lack of artifacts required by the Faces scaffold. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-873) Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-873. --------------------------------- > Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e" > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-873 > URL: https://issues.jboss.org/browse/FORGE-873 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.3.Final > Environment: JBoss 7.1.1 final , Hibernate 4.2.0.final, > Reporter: claudio perrotta > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > For a table with a foreign key the UI permits to select the possible values, but this values are listed in a dropdown menu in a form like "org.forgetest.model.Entity@5f9ba38e" (would be preferable that the string present be relative to the PK referenced) > Anyway, after setting this field and submitting the form, the data are inserted in the table correctly but when i want to modify the record, the UI doesn't show the setted value for the foreign key and i must set it again before saving. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1085) Support ordering of elements in collections in responses for GET collection reqeusts

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1085?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1085. ---------------------------------- Fix Version/s: 1.3.4.Final Resolution: Done > Support ordering of elements in collections in responses for GET collection reqeusts > ------------------------------------------------------------------------------------ > > Key: FORGE-1085 > URL: https://issues.jboss.org/browse/FORGE-1085 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > The {{listAll}} method in the generated REST resources lacks an ORDER BY clause. Due to the absence of such a clause, results are unordered. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1081) REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1081?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1081. ---------------------------------- Fix Version/s: 1.3.4.Final Resolution: Done > REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class > -------------------------------------------------------------------------------------------------------- > > Key: FORGE-1081 > URL: https://issues.jboss.org/browse/FORGE-1081 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > When REST is setup in a project and activated through the {{@ApplicationPath}} annotated class, it would be preferable to generate all the REST resources in the same package instead of using the computed package from the project's group Id. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1081) REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1081?page=com.atlassian.jira.plugin... ] Vineet Reynolds reopened FORGE-1081: ------------------------------------ > REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class > -------------------------------------------------------------------------------------------------------- > > Key: FORGE-1081 > URL: https://issues.jboss.org/browse/FORGE-1081 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > When REST is setup in a project and activated through the {{@ApplicationPath}} annotated class, it would be preferable to generate all the REST resources in the same package instead of using the computed package from the project's group Id. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1085) Support ordering of elements in collections in responses for GET collection reqeusts

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1085?page=com.atlassian.jira.plugin... ] Vineet Reynolds reopened FORGE-1085: ------------------------------------ > Support ordering of elements in collections in responses for GET collection reqeusts > ------------------------------------------------------------------------------------ > > Key: FORGE-1085 > URL: https://issues.jboss.org/browse/FORGE-1085 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The {{listAll}} method in the generated REST resources lacks an ORDER BY clause. Due to the absence of such a clause, results are unordered. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1097) Forge Java parser fails to distinguish between several fields in a FieldDeclaration

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1097: -------------------------------------- Summary: Forge Java parser fails to distinguish between several fields in a FieldDeclaration Key: FORGE-1097 URL: https://issues.jboss.org/browse/FORGE-1097 Project: Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Priority: Critical Consider the following test: {code:java} @Test public void testFieldTypesByteExtraDimensionDeclarationTest() { final JavaClass javaClass = JavaParser.create(JavaClass.class); final Field<JavaClass> field = javaClass.addField("public byte content1[], content2;"); Assert.assertEquals("content1", field.getName()); Assert.assertEquals("byte[]", field.getQualifiedType()); Assert.assertEquals("byte[]", field.getType()); Assert.assertTrue(field.getTypeInspector().isArray()); } {code} The above shown behavior is obviously incorrect since the second 'field' named content2 is 'lost' and so is information about it's type. The underlying issue is that of the parser treating the FieldDeclaration as that belonging to a single field, whereas there may be several VariableDeclarationFragments within the same FieldDeclaration. Ideally, this should be solved by introducing a new type like {{Variable}} to identify individual variables in the declaration, or to change the semantic of {{Field}} to refer to the individual variables. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013