February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1549) Add unitName to @PersistenceContext

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1549?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1549: ----------------------------------- Labels: Starter (was: ) > Add unitName to @PersistenceContext > ----------------------------------- > > Key: FORGE-1549 > URL: https://issues.jboss.org/browse/FORGE-1549 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Labels: Starter > Fix For: 2.x Future > > > The scaffolding generates this kind of code in terms of persistence context (e.g. below is for JSF) : > {code} > @PersistenceContext(type = PersistenceContextType.EXTENDED) > {code} > Because it doesn't have any {{unitName}} it takes the default one, if there is only one persistence unit. It would be better to explicitelly add the {{unitName}} so the code still deploys if there are several persistence unit. As per [FORGE-1513], the persistence unit name is the project name with -{{persistence-unit}} : > {code} > @PersistenceContext(unitName = "myproject-persistence-unit", type = PersistenceContextType.EXTENDED) > {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1549) Add unitName to @PersistenceContext

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1549: ---------------------------------------- Summary: Add unitName to @PersistenceContext Key: FORGE-1549 URL: https://issues.jboss.org/browse/FORGE-1549 Project: Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future The scaffolding generates this kind of code in terms of persistence context (e.g. below is for JSF) : {code} @PersistenceContext(type = PersistenceContextType.EXTENDED) {code} Because it doesn't have any {{unitName}} it takes the default one, if there is only one persistence unit. It would be better to explicitelly add the {{unitName}} so the code still deploys if there are several persistence unit. As per [FORGE-1513], the persistence unit name is the project name with -{{persistence-unit}} : {code} @PersistenceContext(unitName = "myproject-persistence-unit", type = PersistenceContextType.EXTENDED) {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1548) Updated the Forge 2.0 plugin and now JBDS won't start

by Robb Greathouse (JIRA)

Robb Greathouse created FORGE-1548: -------------------------------------- Summary: Updated the Forge 2.0 plugin and now JBDS won't start Key: FORGE-1548 URL: https://issues.jboss.org/browse/FORGE-1548 Project: Forge Issue Type: Bug Components: UI - Eclipse Affects Versions: 2.0.0.Final, 2.0.0.CR2 Environment: JBDS 7.1 Macbook Pro Maverick OS. Reporter: Robb Greathouse After checking for updates on JBDS I approved the update of the Forge 2 plugin. JBDS asked to to be restarted. Upon restarting it gave a progress window announcing Forge 2 starting. After 10 minutes it had not started. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1547) Adding debug information on JSF pages

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1547?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1547: ----------------------------------- Labels: starter (was: ) > Adding debug information on JSF pages > ------------------------------------- > > Key: FORGE-1547 > URL: https://issues.jboss.org/browse/FORGE-1547 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Labels: starter > Fix For: 2.x Future > > > JSF pages are hard to debug, so adding a {{ui:debug}} in the main template. The idea (as explained on http://stackoverflow.com/questions/4049531/uidebug-tag-not-working-in-fac...) is to add a {{ui:debug}} and some config in web.xml so only the debugging shows up in development. > So in the {{pageTemplate.xhtml}} we would add : > {code} > <h:body> > <ui:debug rendered="#{initParam['javax.faces.FACELETS_DEVELOPMENT']}"/> > <div class="navbar navbar-fixed-top"> > {code} > And in the {{web.xml}} : > {code} > <context-param> > <param-name>javax.faces.FACELETS_DEVELOPMENT</param-name> > <param-value>true</param-value> > </context-param> > {code} > Then, once in any page, you just need to press CTRL+ SHIFT + D -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1546) Generate inputTextarea instead of inputText

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1546?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1546: ----------------------------------- Labels: starter (was: ) > Generate inputTextarea instead of inputText > ------------------------------------------- > > Key: FORGE-1546 > URL: https://issues.jboss.org/browse/FORGE-1546 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Labels: starter > Fix For: 2.x Future > > > In the JSF scaffolding, when an entity has a length greater than, let's say, 500, an inputTextarea should be generated instead of an inputText > {code} > jpa-new-field --named bio --length 800 > {code} > Should generate : > {code} > <h:inputTextarea id="authorBeanAuthorBio" maxLength="800" value="#{authorBean.author.bio}"/> > {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1547) Adding debug information on JSF pages

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1547: ---------------------------------------- Summary: Adding debug information on JSF pages Key: FORGE-1547 URL: https://issues.jboss.org/browse/FORGE-1547 Project: Forge Issue Type: Enhancement Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future JSF pages are hard to debug, so adding a {{ui:debug}} in the main template. The idea (as explained on http://stackoverflow.com/questions/4049531/uidebug-tag-not-working-in-fac...) is to add a {{ui:debug}} and some config in web.xml so only the debugging shows up in development. So in the {{pageTemplate.xhtml}} we would add : {code} <h:body> <ui:debug rendered="#{initParam['javax.faces.FACELETS_DEVELOPMENT']}"/> <div class="navbar navbar-fixed-top"> {code} And in the {{web.xml}} : {code} <context-param> <param-name>javax.faces.FACELETS_DEVELOPMENT</param-name> <param-value>true</param-value> </context-param> {code} Then, once in any page, you just need to press CTRL+ SHIFT + D -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1546) Generate inputTextarea instead of inputText

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1546: ---------------------------------------- Summary: Generate inputTextarea instead of inputText Key: FORGE-1546 URL: https://issues.jboss.org/browse/FORGE-1546 Project: Forge Issue Type: Enhancement Components: Scaffold Affects Versions: 2.0.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future In the JSF scaffolding, when an entity has a length greater than, let's say, 500, an inputTextarea should be generated instead of an inputText {code} jpa-new-field --named bio --length 800 {code} Should generate : {code} <h:inputTextarea id="authorBeanAuthorBio" maxLength="800" value="#{authorBean.author.bio}"/> {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1128) Migrate GIT tools (plugins) as a Forge 2.x Addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1128?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1128. ---------------------------------- Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > Migrate GIT tools (plugins) as a Forge 2.x Addon > ------------------------------------------------ > > Key: FORGE-1128 > URL: https://issues.jboss.org/browse/FORGE-1128 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha10 > Reporter: George Gastaldi > Assignee: Ivan St. Ivanov > Labels: Starter > Fix For: 2.0.0.Final > > > Migrate the git-tools and git-tools-tests modules to an addon -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014