May 2013 - forge-issues - Jboss List Archives

[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 claudio perrotta (JIRA)

[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ] claudio perrotta commented on FORGE-873: ---------------------------------------- To change the string "org.forgetest.model.Entity@5f9ba38e" i change in xhtml files (create, view, search) this line <f:selectItems value="#{EntityBean.all}"/> in <f:selectItems value="#{EntityBean.all}" var="entity" itemValue="#{entity}" itemLabel="#{entity.id}"/> where "#{entity} is the private attribute in the bean relative to the entity class and #{entity.id} is the label that you want to show in dropdown menu i hope it helps > 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 > > 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

12 years, 11 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 claudio perrotta (JIRA)

[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ] claudio perrotta updated FORGE-873: ----------------------------------- Summary: Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e" (was: Scaffold don't shows the correct referenced entities in edit views, while in details views show something like "org.forgetest.model.Entity@5f9ba38e") > 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 > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-440: ---------------------------------- Priority: Major (was: Critical) > A pom.xml which contains comments loses all of them after Forge operates on it. > ------------------------------------------------------------------------------- > > Key: FORGE-440 > URL: https://issues.jboss.org/browse/FORGE-440 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.0.6.Final > Environment: HEAD > Reporter: Pete Muir > Fix For: 2.0.0.Alpha4 > > > Also looses formatting, but this is less of an issue. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-604: --------------------------------------- Hi Christopher, Forge 1.2.4.Final now supports EAR packaging as described in FORGE-864. Could you check if that is sufficient to close this issue ? Best Regards, George Gastaldi > Add support for Java EE 6 Full Profile > -------------------------------------- > > Key: FORGE-604 > URL: https://issues.jboss.org/browse/FORGE-604 > Project: Forge > Issue Type: Task > Components: Java EE APIs > Affects Versions: 1.0.5.Final > Environment: All > Reporter: Christopher Volk > Fix For: 1.2.4.Final > > > Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging. > The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort. > I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile. > This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-698) Forge must try to box identifiers when they are primitives

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-698?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-698. --------------------------------- Assignee: Vineet Reynolds Fix Version/s: 1.2.4.Final Resolution: Done Closing this issue. This should have been fixed in the recent fixes made for FORGE-572. This upstream commit https://github.com/forge/core/commit/dd0ab7908d8e20c2a3e44c48181053bae30c... should have addressed this specific issue. > Forge must try to box identifiers when they are primitives > ---------------------------------------------------------- > > Key: FORGE-698 > URL: https://issues.jboss.org/browse/FORGE-698 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.1.1.Final > Reporter: Marius Bogoevici > Assignee: Vineet Reynolds > Fix For: 1.2.4.Final > > > With TicketMonster (https://github.com/jboss-jdf/ticket-monster, tag 2.0.1.Final), when running the admin_layer.fsh script (without applying the patches), the class org.jboss.jdf.examples.view.SectionAllocationBean will contain the following uncompilable code > {code} > return ejbProxy.findById(long.valueOf(value)); > {code} > (note the use of lowercase l in long) > This is caused by the id field in the entity class being primitive rather than object. While this can be worked around easily (using a class is better than the primitive anyway), this still remains a bug. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-875: ------------------------------------- Assignee: Koen Aers (was: George Gastaldi) > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Bug > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Assignee: Koen Aers > Priority: Critical > Labels: forge > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-875: ---------------------------------- Priority: Critical (was: Blocker) > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Bug > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Assignee: George Gastaldi > Priority: Critical > Labels: forge > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-875: --------------------------------------- This looks like a race condition issue in the Forge/JBT integration. When walking through the code under a debugger attached to the Forge instance in JBT, this is no longer reproducible - the beans.xml file is never deleted after it is created the first time. Restarting the Eclipse workspace and running the script in Forge without an attached debugger, almost always reproduces the issue. I can't be definite about this, but it does seem that the file is lost when Eclipse updates the facets of the created project. The workaround of running {{beans setup}} before {{scaffold setup}} in the script prevents this specific instance of the bug from occurring, but there could be others. > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Bug > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Assignee: George Gastaldi > Priority: Blocker > Labels: forge > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-885) Support Bean Validation 1.1 method constraints in plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-885?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-885: --------------------------------------- More info: http://docs.jboss.org/hibernate/validator/5.0/reference/en-US/html_single... > Support Bean Validation 1.1 method constraints in plugins > --------------------------------------------------------- > > Key: FORGE-885 > URL: https://issues.jboss.org/browse/FORGE-885 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Reporter: George Gastaldi > Fix For: Future > > > It would be nice if we could add support for BV 1.1 in a plugin method, avoiding the need to manually validate pre-conditions. This should happen after normal @Option validation, as there is an {{@Option(required=true)}} for example. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-885) Support Bean Validation 1.1 method constraints in plugins

by George Gastaldi (JIRA)

George Gastaldi created FORGE-885: ------------------------------------- Summary: Support Bean Validation 1.1 method constraints in plugins Key: FORGE-885 URL: https://issues.jboss.org/browse/FORGE-885 Project: Forge Issue Type: Enhancement Components: Plugin API Reporter: George Gastaldi Fix For: Future It would be nice if we could add support for BV 1.1 in a plugin method, avoiding the need to manually validate pre-conditions. This should happen after normal @Option validation, as there is an {{@Option(required=true)}} for example. -- 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, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2013