[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 commented on FORGE-1547:
----------------------------------------
I agree, good idea
> 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
> Assignee: 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, 7 months
[JBoss JIRA] (FORGE-1547) Adding debug information on JSF pages
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1547?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1547:
------------------------------------------
Looks like the following code is better because it uses Staging
{code}
<ui:debug rendered="#{facesContext.application.projectStage == 'Development'}" />
{code}
> 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
> Assignee: 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, 7 months
[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 edited comment on FORGE-1547 at 2/17/14 3:34 PM:
-----------------------------------------------------------------
{{javax.faces.PROJECT_STAGE}} should be used instead, as there is already a command that sets the project stage:
{code}
faces-project-stage --stage Development
{code}
was (Author: gastaldi):
{{javax.faces.PROJECT_STAGE}} should be used instead
> 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
> Assignee: 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, 7 months
[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 commented on FORGE-1547:
----------------------------------------
{{javax.faces.PROJECT_STAGE}} should be used instead
> 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
> Assignee: 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, 7 months
[JBoss JIRA] (FORGE-1575) Map Entities and Columns From the Forge Command Line
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1575?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1575.
----------------------------------
Fix Version/s: 2.0.1.Final
(was: 2.x Future)
Resolution: Done
> Map Entities and Columns From the Forge Command Line
> ----------------------------------------------------
>
> Key: FORGE-1575
> URL: https://issues.jboss.org/browse/FORGE-1575
> Project: Forge
> Issue Type: Feature Request
> Components: Forge Scripting Language
> Affects Versions: 1.4.4.Final
> Reporter: Larry Wilson
> Assignee: George Gastaldi
> Labels: Starter
> Fix For: 2.0.1.Final
>
>
> As an end user, I would like to be able to create a table or column mapping with the Forge command line.
> Our company has standards for the data model that are different than those for the Java layer.
> For example, the standard name for the Java POJO TimeZone.java which is mapped to the table named TIME_ZONE.
> Ideally, Forge would support:
> entity --named TimeZone --tableName TIME_ZONE;
> field string --named activeFlag --columnName ACTIVE_FLAG;
> This would lend keeping a project as a prototype much longer before stepping away from Forge and manually making these changes.
--
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, 7 months
[JBoss JIRA] (FORGE-1547) Adding debug information on JSF pages
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1547?page=com.atlassian.jira.plugin... ]
Antonio Goncalves reassigned FORGE-1547:
----------------------------------------
Assignee: Antonio Goncalves
> 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
> Assignee: 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, 7 months
[JBoss JIRA] (FORGE-1575) Map Entities and Columns From the Forge Command Line
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1575?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1575:
--------------------------------------
Assignee: George Gastaldi
> Map Entities and Columns From the Forge Command Line
> ----------------------------------------------------
>
> Key: FORGE-1575
> URL: https://issues.jboss.org/browse/FORGE-1575
> Project: Forge
> Issue Type: Feature Request
> Components: Forge Scripting Language
> Affects Versions: 1.4.4.Final
> Reporter: Larry Wilson
> Assignee: George Gastaldi
> Labels: Starter
> Fix For: 2.x Future
>
>
> As an end user, I would like to be able to create a table or column mapping with the Forge command line.
> Our company has standards for the data model that are different than those for the Java layer.
> For example, the standard name for the Java POJO TimeZone.java which is mapped to the table named TIME_ZONE.
> Ideally, Forge would support:
> entity --named TimeZone --tableName TIME_ZONE;
> field string --named activeFlag --columnName ACTIVE_FLAG;
> This would lend keeping a project as a prototype much longer before stepping away from Forge and manually making these changes.
--
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, 7 months
[JBoss JIRA] (FORGE-1201) getSearchPredicates should use case insensitive search
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1201?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1201:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.0.1.Final
(was: 2.x Future)
Resolution: Done
> getSearchPredicates should use case insensitive search
> ------------------------------------------------------
>
> Key: FORGE-1201
> URL: https://issues.jboss.org/browse/FORGE-1201
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.0.1.Final
>
>
> Hi,
> When you do JSF scaffolding, the generated code for research is as follow :
> {code}
> private Predicate[] getSearchPredicates(Root<Talk> root) {
> CriteriaBuilder builder = this.entityManager.getCriteriaBuilder();
> List<Predicate> predicatesList = new ArrayList<>();
> String title = this.example.getTitle();
> if (title != null && !"".equals(title)) {
> predicatesList.add(builder.like(root.<String>get("title"), '%' + title + '%'));
> }
> {code}
> The problem with that is the search is case sensitive and searching for "java" or "Java" doesn't bring the same results. It would be more natural to have case insensitive search as follow :
> {code}
> private Predicate[] getSearchPredicates(Root<Talk> root) {
> CriteriaBuilder builder = this.entityManager.getCriteriaBuilder();
> List<Predicate> predicatesList = new ArrayList<>();
> String title = this.example.getTitle();
> if (title != null && !"".equals(title)) {
> predicatesList.add(builder.like(builder.lower(root.<String>get("title")), "%" + title.toLowerCase() + "%"));
> }
> {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, 7 months
[JBoss JIRA] (FORGE-1580) Integrating the generated JSF pages better into a entire web application
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1580:
----------------------------------------
Summary: Integrating the generated JSF pages better into a entire web application
Key: FORGE-1580
URL: https://issues.jboss.org/browse/FORGE-1580
Project: Forge
Issue Type: Feature Request
Components: Scaffold
Affects Versions: 2.0.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
I often use Forge to create separate administration pages that will fit an entire web application (a bit like in TicketMonster). The problem is that all JSF pages use {{pageTemplate.xhtml}} and this template declares a navigation menu. So the other pages of the web site cannot use this template.
Forge could either :
* use 2 level of templates : the {{pageTemplate.xhtml}} only does the header and footer, and we had a new {{forgeTemplate.xhtml}} that uses {{pageTemplate.xhtml}} and adds a navigation menu
* we only use {{pageTemplate.xhtml}} but the menu is an external component that could only be used by Forge pages.
--
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, 7 months
[JBoss JIRA] (FORGE-1579) Create command faces-generate-pages-from-services
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1579:
----------------------------------------
Summary: Create command faces-generate-pages-from-services
Key: FORGE-1579
URL: https://issues.jboss.org/browse/FORGE-1579
Project: Forge
Issue Type: Sub-task
Components: Scaffold
Affects Versions: 2.0.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
This command would create JSF beans from a transactional EJB tier. Instead of accessing an {{EntityManager}} (like the {{scaffold-generate}} command), the generated JSF beans would delegate CRUD operations to the EJB tier
--
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, 7 months