June 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1829) setItemLabelConverter cause NullPointerException in Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1829?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1829: ----------------------------------- Fix Version/s: 2.x Future > setItemLabelConverter cause NullPointerException in Eclipse > ----------------------------------------------------------- > > Key: FORGE-1829 > URL: https://issues.jboss.org/browse/FORGE-1829 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI - Eclipse > Reporter: Aslak Knutsen > Fix For: 2.x Future > > > {code} > containerAdapter.setItemLabelConverter(new Converter<Container, String>() { > @Override > public String convert(Container source) { > return source.getId(); > } > }); > {code} > In Eclipse, the Converter is called with a "null" argument during Step/Command initialization. Unless the user specifically checks for null a NullPointerException is thrown. > This is especially odd in the case where the user provide a Set of ValueChoices to convert and none of those are null. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1718) RejectedExecutionException when executing a script

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1718?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1718: ----------------------------------- Fix Version/s: 2.x Future > RejectedExecutionException when executing a script > -------------------------------------------------- > > Key: FORGE-1718 > URL: https://issues.jboss.org/browse/FORGE-1718 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Fix For: 2.x Future > > > Using the following script to create a basic Java EE application: > project-new --named javaee-forge --topLevelPackage org.forge.samples.javaee > servlet-setup; cdi-setup; jpa-setup --container JBOSS_EAP6; rest-setup; constraint-setup; faces-setup; ejb-setup; scaffold-setup > jpa-new-entity --named Author --targetPackage org.forge.samples.javaee.entities > jpa-new-entity --named Book --targetPackage org.forge.samples.javaee.entities > jpa-new-field --targetEntity org.forge.samples.javaee.entities.Author --named name --type String --length 30 > jpa-new-field --targetEntity org.forge.samples.javaee.entities.Book --named title --type String --length 30 > jpa-new-field --targetEntity org.forge.samples.javaee.entities.Book --named isbn --type String --length 15 > Executing the script in forge console is randomly throwing the following exception: > [forge-samples]$ jpa-new-field --targetEntity org.forge.samples.javaee.entities.Author --named name --type String --length 30 > jpa-new-field --targetEntity org.forge.samples.javaee.entities.Book --named title --type String --length 30 > Exception in thread "Aesh Process Loop 614867598" java.util.concurrent.RejectedExecutionException: Task AeshProcess{pid=12, manager=org.jboss.aesh.console.ProcessManager@5bc4aef2, consoleCallback=org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl@5ffb3152, operation=ControlOperator: NONE, Buffer: jpa-new-field --targetEntity org.forge.samples.javaee.entities.Book --named title --type String --length 30} rejected from java.util.concurrent.ThreadPoolExecutor@1af9a4c9[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 11] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) > at org.jboss.aesh.console.ProcessManager.startNewProcess(ProcessManager.java:44) > at org.jboss.aesh.console.Console.processOperationResult(Console.java:626) > at org.jboss.aesh.console.Console.processInternalOperation(Console.java:592) > at org.jboss.aesh.console.Console.execute(Console.java:580) > at org.jboss.aesh.console.Console.access$700(Console.java:60) > at org.jboss.aesh.console.Console$6.run(Console.java:499) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > ***SUCCESS*** Field name created -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1614) New JPA entity command does not warn if existing entities are overwritten

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1614?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1614: ----------------------------------- Fix Version/s: 2.x Future > New JPA entity command does not warn if existing entities are overwritten > ------------------------------------------------------------------------- > > Key: FORGE-1614 > URL: https://issues.jboss.org/browse/FORGE-1614 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.1.1.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > When a new JPA entity is created, no warnings are issued when the name of the user-supplied entity matches an already existing entity. The existing entity is lost including any fields, and a new one is created in it's place. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1711) Cleaning up the front page of generated app

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1711?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1711: ----------------------------------- Fix Version/s: 2.x Future > Cleaning up the front page of generated app > ------------------------------------------- > > Key: FORGE-1711 > URL: https://issues.jboss.org/browse/FORGE-1711 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Fix For: 2.x Future > > > After scaffold-setup, a top-level index.xhtml is generated for JSF scaffolds. The front page looks nice and clean but the entity name is little lost with forge icon and "Welcome to Forge" message. Can we highlight somehow that these entities are used within application ? May be make the table little bigger ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1711) Cleaning up the front page of generated app

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1711?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1711: ----------------------------------- Priority: Optional (was: Major) > Cleaning up the front page of generated app > ------------------------------------------- > > Key: FORGE-1711 > URL: https://issues.jboss.org/browse/FORGE-1711 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Priority: Optional > Fix For: 2.x Future > > > After scaffold-setup, a top-level index.xhtml is generated for JSF scaffolds. The front page looks nice and clean but the entity name is little lost with forge icon and "Welcome to Forge" message. Can we highlight somehow that these entities are used within application ? May be make the table little bigger ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1548?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1548. ---------------------------------- Resolution: Out of Date Looks like it was fixed for some time ago > 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 > Security Level: Public(Everyone can see) > Components: UI - Eclipse > Affects Versions: 2.0.0.CR2, 2.0.0.Final > Environment: JBDS 7.1 Macbook Pro Maverick OS. > Reporter: Robb Greathouse > Assignee: Koen Aers > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1774) Default --help for Forge commands

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1774?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1774: ----------------------------------- Fix Version/s: 2.x Future > Default --help for Forge commands > --------------------------------- > > Key: FORGE-1774 > URL: https://issues.jboss.org/browse/FORGE-1774 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jess Sightler > Fix For: 2.x Future > > > If a command does not specify a --help parameter, forge should provide a default for this that simply displays the man page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1710) web.xml is not generated for faces-setup

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1710?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1710. ---------------------------------- Resolution: Won't Fix That's because web.xml is not required in Servlet 3.0+. > web.xml is not generated for faces-setup > ---------------------------------------- > > Key: FORGE-1710 > URL: https://issues.jboss.org/browse/FORGE-1710 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > > Creating a new project as: > project-new --named jsf-test --topLevelPackage org.forge.samples.javaee > And setting up Faces as: > faces-setup > generates the following directory structure: > jsf-test > jsf-test/pom.xml > jsf-test/src > jsf-test/src/main > jsf-test/src/main/java > jsf-test/src/main/resources > jsf-test/src/main/webapp > jsf-test/src/main/webapp/WEB-INF > jsf-test/src/main/webapp/WEB-INF/faces-config.xml > jsf-test/src/test > jsf-test/src/test/java > jsf-test/src/test/resources > There is no web.xml generated. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1650) Support creation of JSON object models from application code through JSON-P APIs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1650?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1650. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.7.0.Final Resolution: Done Already implemented in the parser-json addon. > Support creation of JSON object models from application code through JSON-P APIs > -------------------------------------------------------------------------------- > > Key: FORGE-1650 > URL: https://issues.jboss.org/browse/FORGE-1650 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.1.1.Final > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > > One could automate generation of parsers that construct JSONObjects from application models, through Forge. This would reduce unnecessary typing involved in mapping the application model to the JSON model. > This could be supported for both the object-model ({{JSONObjectBuilder}}) as well as the stream-model ({{JsonParser}}) of JSON-P. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1723) Incorrect web.xml generated for REST

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1723?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1723. ---------------------------------- Resolution: Out of Date Fixed in Forge 2.x > Incorrect web.xml generated for REST > ------------------------------------ > > Key: FORGE-1723 > URL: https://issues.jboss.org/browse/FORGE-1723 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 1.4.4.Final > Reporter: Arun Gupta > > Create a project using Forge 1.4.4 as: > [no project] tmp $ new-project --named basic-javaee-forge --topLevelPackage org.forge.samples.javaee --type war > ? Use [/Users/arungupta/tmp/basic-javaee-forge] as project directory? [Y/n] y > ***SUCCESS*** Created project [basic-javaee-forge] in new working directory [/Users/arungupta/tmp/basic-javaee-forge] > Wrote /Users/arungupta/tmp/basic-javaee-forge > Wrote /Users/arungupta/tmp/basic-javaee-forge/pom.xml > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/main/webapp > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/main/java > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/test/java > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/main/resources > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/test/resources > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/main/java/org/forge/samples/javaee > [basic-javaee-forge] basic-javaee-forge $ rest setup > Use which version of 'jboss-javaee-6.0' ? > 1 - [org.jboss.spec:jboss-javaee-6.0:pom::1.0.0.Beta4] > 2 - [org.jboss.spec:jboss-javaee-6.0:pom::1.0.0.Beta5] > 3 - [org.jboss.spec:jboss-javaee-6.0:pom::1.0.0.Beta6] > 4 - [org.jboss.spec:jboss-javaee-6.0:pom::1.0.0.Beta7] > 5 - [org.jboss.spec:jboss-javaee-6.0:pom::1.0.0.CR1] > 6 - [org.jboss.spec:jboss-javaee-6.0:pom::1.0.0.Final] > 7 - [org.jboss.spec:jboss-javaee-6.0:pom::2.0.0.Beta1] > 8 - [org.jboss.spec:jboss-javaee-6.0:pom::2.0.0.CR1] > 9 - [org.jboss.spec:jboss-javaee-6.0:pom::2.0.0.Final] > 10 - [org.jboss.spec:jboss-javaee-6.0:pom::2.1.0.Beta1] > 11 - [org.jboss.spec:jboss-javaee-6.0:pom::3.0.0.Beta1] > 12 - [org.jboss.spec:jboss-javaee-6.0:pom::3.0.0.Final] > 13 - [org.jboss.spec:jboss-javaee-6.0:pom::3.0.1.Final] > 14 - [org.jboss.spec:jboss-javaee-6.0:pom::3.0.2.Final]* > ? Choose an option by typing the number of the selection [*-default] [0] > ***SUCCESS*** Installed [forge.spec.servlet] successfully. > ? What root path do you want to use for your resources? [/rest] > ***SUCCESS*** Installed [forge.spec.jaxrs.webxml] successfully. > ***SUCCESS*** Installed [forge.spec.jaxrs] successfully. > ***SUCCESS*** Rest Web Services (JAX-RS) is installed. > Wrote /Users/arungupta/tmp/basic-javaee-forge/pom.xml > Wrote /Users/arungupta/tmp/basic-javaee-forge/src/main/webapp/WEB-INF/web.xml > Generated web.xml is shown below: > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.0" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> > <display-name>basic-javaee-forge</display-name> > <session-config> > <session-timeout>30</session-timeout> > </session-config> > <servlet> > <servlet-name>javax.ws.rs.core.Application</servlet-name> > <load-on-startup>1</load-on-startup> > </servlet> > <servlet-mapping> > <servlet-name>javax.ws.rs.core.Application</servlet-name> > <url-pattern>/rest/*</url-pattern> > </servlet-mapping> > </web-app> > Deploying this project in JBoss EAP 6.2 gives the error: > 17:34:18,770 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/basic-javaee-forge]] (ServerService Thread Pool -- 126) JBWEB000289: Servlet javax.ws.rs.core.Application threw load() exception: javax.servlet.ServletException: JBWEB000260: No servlet class has been specified for servlet javax.ws.rs.core.Application > at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1147) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > This is because javax.ws.rs.core.Application is not a Servlet. There is even no need to generated web.xml, a combination of Application and ApplicationPath will be sufficient. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014