January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1525) Being able to create custom Id for JPA entities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1525?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1525: ----------------------------------- Affects Version/s: 2.0.0.CR2 > Being able to create custom Id for JPA entities > ----------------------------------------------- > > Key: FORGE-1525 > URL: https://issues.jboss.org/browse/FORGE-1525 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Affects Versions: 2.0.0.CR2 > Reporter: Manuel Rascioni > > As per FORGE-1398 there should be the possibility to customize the {{@Id}} for an {{@Entity}} make it use {{@EmbeddedId}} when creating the entity. > Something like: > {{entity --named Document --idType custom --idClass DocumentCode}} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1525) Being able to create custom Id for JPA entities

by Manuel Rascioni (JIRA)

Manuel Rascioni created FORGE-1525: -------------------------------------- Summary: Being able to create custom Id for JPA entities Key: FORGE-1525 URL: https://issues.jboss.org/browse/FORGE-1525 Project: Forge Issue Type: Feature Request Components: Java EE APIs Reporter: Manuel Rascioni As per FORGE-1398 there should be the possibility to customize the {{@Id}} for an {{@Entity}} make it use {{@EmbeddedId}} when creating the entity. Something like: {{entity --named Document --idType custom --idClass DocumentCode}} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1510) When executing jpa-setup it cd the persistence.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1510?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1510. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > When executing jpa-setup it cd the persistence.xml > -------------------------------------------------- > > Key: FORGE-1510 > URL: https://issues.jboss.org/browse/FORGE-1510 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > Inside a project, no matter where you are, when you type {{jpa-setup}} the shell goes to the {{persistence.xml}} file. It's a bit strange. This could be a feature but if you do a {{contraint-setup}} it doesn't go to {{validation.xml}}. So the behavior is not consistent : > {code} > [pluralsight-persistence]$ jpa-setup > Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/pom.xml > Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/resources > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/resources/META-INF > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/resources/META-INF/persistence.xml > Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/resources/META-INF/persistence.xml > ***SUCCESS*** Persistence (JPA) is installed. > [persistence.xml]$ constraint-setup > Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/pom.xml > Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/resources/META-INF > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/resources/META-INF/validation.xml > ***SUCCESS*** Bean Validation is installed. > [persistence.xml]$ > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1523) Change the JSF namespaces to fit new Java EE 7 standard

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1523?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1523: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/368 > Change the JSF namespaces to fit new Java EE 7 standard > ------------------------------------------------------- > > Key: FORGE-1523 > URL: https://issues.jboss.org/browse/FORGE-1523 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > > When a JSF page is generated, the namespaces look like this : > {code} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:c="http://java.sun.com/jsp/jstl/core" > template="/resources/scaffold/pageTemplate.xhtml"> > {code} > They use the old {{java.sun.com}} namespace instead of the new {{xmlns.jcp.org}}. They should look like this : > {code} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > template="/resources/scaffold/pageTemplate.xhtml"> > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1523) Change the JSF namespaces to fit new Java EE 7 standard

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1523?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1523: -------------------------------------- Assignee: George Gastaldi > Change the JSF namespaces to fit new Java EE 7 standard > ------------------------------------------------------- > > Key: FORGE-1523 > URL: https://issues.jboss.org/browse/FORGE-1523 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > When a JSF page is generated, the namespaces look like this : > {code} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:c="http://java.sun.com/jsp/jstl/core" > template="/resources/scaffold/pageTemplate.xhtml"> > {code} > They use the old {{java.sun.com}} namespace instead of the new {{xmlns.jcp.org}}. They should look like this : > {code} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > template="/resources/scaffold/pageTemplate.xhtml"> > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1519) Template title has wrong EL

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1519?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1519. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > Template title has wrong EL > --------------------------- > > Key: FORGE-1519 > URL: https://issues.jboss.org/browse/FORGE-1519 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > [FORGE-1191] was fixed in Forge 1.x but it hasn't been fixed in Forge 2.x. Have you used the latest scaffolding templates ? > This bug happens in GlassFish 4 but also in WildFly 8. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1524) Change the JSF preRenderView to fit the new viewAction

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1524: ---------------------------------------- Summary: Change the JSF preRenderView to fit the new viewAction Key: FORGE-1524 URL: https://issues.jboss.org/browse/FORGE-1524 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.CR2 Reporter: Antonio Goncalves Fix For: 2.x Future When a JSF page is generated, it uses the old JSF 2.0 {{preRenderView}} : {code} <f:event type="preRenderView" listener='#{authorBean.retrieve}'/> {code} Instead, it should be using the new Java EE 7 {{viewAction}} : {code} <f:viewAction action="#{authorBean.retrieve}"/> {code} I've replaced all occurrences in every pages and it works fine. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1522) View could not be restored in WildFly

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1522?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1522: ------------------------------------- Priority: Critical (was: Major) > View could not be restored in WildFly > ------------------------------------- > > Key: FORGE-1522 > URL: https://issues.jboss.org/browse/FORGE-1522 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > When I scaffold a JSF application, it works fine with GlassFish 4, I can navigate through my pages, view/create/delete data. But when I run it with WildFly 8 CR1, as soon as I navigate to a page, I get the following : > {code} > [31m12:36:19,670 ERROR [io.undertow.request] (default task-7) UT005023: Exception handling request to /module07/faces/author/search.xhtml: javax.servlet.ServletException: viewId:/author/search.xhtml - View /author/search.xhtml could not be restored. > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:659) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:67) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:654) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > Caused by: javax.faces.application.ViewExpiredException: viewId:/author/search.xhtml - View /author/search.xhtml could not be restored. > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:210) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:121) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:646) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > ... 24 more > {code} > So it makes the application not usable with WildFly 8 CR1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1521) Navigation menu is empty

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1521?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1521: ------------------------------------- Priority: Critical (was: Major) > Navigation menu is empty > ------------------------ > > Key: FORGE-1521 > URL: https://issues.jboss.org/browse/FORGE-1521 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > When scaffolding JSF pages for a few entities I get the following in the {{pageTemplate.xhtml}} : > {code} > <div id="navigation"> > <h:link id="homeLink" outcome="/index.xhtml"> > <img src='#{resource["forge-logo.png"]}' alt="Forge... get hammered" border="0" /> > </h:link> > <ul/> > </div> > {code} > The {{<ul/>}} is empty instead of having links to each entity {{search}} page -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1523) Change the JSF namespaces to fit new Java EE 7 standard

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1523: ---------------------------------------- Summary: Change the JSF namespaces to fit new Java EE 7 standard Key: FORGE-1523 URL: https://issues.jboss.org/browse/FORGE-1523 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.0.0.CR2 Reporter: Antonio Goncalves Priority: Minor Fix For: 2.x Future When a JSF page is generated, the namespaces look like this : {code} <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:c="http://java.sun.com/jsp/jstl/core" template="/resources/scaffold/pageTemplate.xhtml"> {code} They use the old {{java.sun.com}} namespace instead of the new {{xmlns.jcp.org}}. They should look like this : {code} <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://xmlns.jcp.org/jsf/html" xmlns:f="http://xmlns.jcp.org/jsf/core" xmlns:ui="http://xmlns.jcp.org/jsf/facelets" xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" template="/resources/scaffold/pageTemplate.xhtml"> {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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014