[JBoss JIRA] (FORGE-928) IllegalArgumentException with CLAC when UISelectMany.getValues() is called
by George Gastaldi (JIRA)
George Gastaldi created FORGE-928:
-------------------------------------
Summary: IllegalArgumentException with CLAC when UISelectMany.getValues() is called
Key: FORGE-928
URL: https://issues.jboss.org/browse/FORGE-928
Project: Forge
Issue Type: Bug
Components: Container, UI - Eclipse
Affects Versions: 2.0.0.Alpha4
Reporter: George Gastaldi
The following exception happens when UISelectMany.getValue() is called in CheckboxTableControlBuilder (in order to know which values are already selected):
{code:java}
java.lang.IllegalArgumentException: Class loader to inspect must not be null.
at org.jboss.forge.furnace.util.Assert.notNull(Assert.java:18)
at org.jboss.forge.furnace.util.ClassLoaders.containsClass(ClassLoaders.java:48)
at org.jboss.forge.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:150)
at org.jboss.forge.proxy.ClassLoaderAdapterCallback.access$300(ClassLoaderAdapterCallback.java:30)
at org.jboss.forge.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:83)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:59)
at org.javassist.tmp.java.lang.Iterable_$$_javassist_2c062bdb-f227-4881-bace-b471ab43bbfa.iterator(Iterable_$$_javassist_2c062bdb-f227-4881-bace-b471ab43bbfa.java)
{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, 7 months
[JBoss JIRA] (FORGE-928) IllegalArgumentException with CLAC when UISelectMany.getValues() is called
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-928?page=com.atlassian.jira.plugin.... ]
George Gastaldi reassigned FORGE-928:
-------------------------------------
Assignee: Lincoln Baxter III
> IllegalArgumentException with CLAC when UISelectMany.getValues() is called
> --------------------------------------------------------------------------
>
> Key: FORGE-928
> URL: https://issues.jboss.org/browse/FORGE-928
> Project: Forge
> Issue Type: Bug
> Components: Container, UI - Eclipse
> Affects Versions: 2.0.0.Alpha4
> Reporter: George Gastaldi
> Assignee: Lincoln Baxter III
>
> The following exception happens when UISelectMany.getValue() is called in CheckboxTableControlBuilder (in order to know which values are already selected):
> {code:java}
> java.lang.IllegalArgumentException: Class loader to inspect must not be null.
> at org.jboss.forge.furnace.util.Assert.notNull(Assert.java:18)
> at org.jboss.forge.furnace.util.ClassLoaders.containsClass(ClassLoaders.java:48)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:150)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.access$300(ClassLoaderAdapterCallback.java:30)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:83)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:59)
> at org.javassist.tmp.java.lang.Iterable_$$_javassist_2c062bdb-f227-4881-bace-b471ab43bbfa.iterator(Iterable_$$_javassist_2c062bdb-f227-4881-bace-b471ab43bbfa.java)
> {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, 7 months
[JBoss JIRA] (FORGE-912) UI Scaffolding does not support entities with EmbeddedId
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-912?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-912:
----------------------------------
Issue Type: Enhancement (was: Story)
Workflow: GIT Pull Request workflow (was: jira)
> UI Scaffolding does not support entities with EmbeddedId
> --------------------------------------------------------
>
> Key: FORGE-912
> URL: https://issues.jboss.org/browse/FORGE-912
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.3.0.Final
> Environment: Linux 3.8 - Firefox 20 - MySQL 5.5 - PostgresSQL 9.1
> Reporter: Hanine Hanynowsky
> Priority: Critical
>
> UI Scaffolding does not support Entities with EnbeddedId.
> The value of ID generated is always null and there is no way to view a corresponding object.
> The generated entity and EmbeddedId class seem fine to me. The issue is with the VIEW scaffolding (The beans and the way XHTML files values are binded).
--
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, 7 months
[JBoss JIRA] (FORGE-749) Support rendering of choices when prompting user for input
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-749?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-749:
----------------------------------
Issue Type: Feature Request (was: Story)
Workflow: GIT Pull Request workflow (was: jira)
> Support rendering of choices when prompting user for input
> ----------------------------------------------------------
>
> Key: FORGE-749
> URL: https://issues.jboss.org/browse/FORGE-749
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 1.2.0.Final
> Reporter: Aslak Knutsen
>
> In order to display Typed choice objects to the user
> As a Plugin Developer
> I want to be able to control the rendering
> Given a list of choices of type List<T>
> And a call to built in Shell.promptChoice( String, List<T> )
> Then it should be possible to pass in a Renderer to the shell to control out displayed
--
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, 7 months
[JBoss JIRA] (FORGE-424) JavaParser does not understand wildcard imports like "javax.persistence.*"
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-424?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III deleted FORGE-424:
-------------------------------------
> JavaParser does not understand wildcard imports like "javax.persistence.*"
> --------------------------------------------------------------------------
>
> Key: FORGE-424
> URL: https://issues.jboss.org/browse/FORGE-424
> Project: Forge
> Issue Type: Technical task
> Reporter: Lincoln Baxter III
>
> The JavaParser Annotation.getQualifiedName() will return "Column" instead of "javax.persistence.Column" for the following example class scenario. It should be able to understand the wildcard, given the proper metadata:
> {code}package demo.entities;
> import javax.persistence.*;
> @Entity
> public class Contact implements java.io.Serializable {
> @Id
> private @GeneratedValue(strategy = GenerationType.AUTO)
> @Column(name = "id", updatable = false, nullable = false)
> Long id = null;
> @Version
> private @Column(name = "version")
> int version = 0;
> public Long getId() {
> return this.id;
> }
> public void setId(final Long id) {
> this.id = id;
> }
> public int getVersion() {
> return this.version;
> }
> public void setVersion(final int version) {
> this.version = version;
> }
> @Override
> public boolean equals(Object that) {
> if (this == that) {
> return true;
> }
> if (that == null) {
> return false;
> }
> if (getClass() != that.getClass()) {
> return false;
> }
> if (id != null) {
> return id.equals(((Contact) that).id);
> }
> return super.equals(that);
> }
> @Override
> public int hashCode() {
> if (id != null) {
> return id.hashCode();
> }
> return super.hashCode();
> }
> private String name;
> public String getName() {
> return this.name;
> }
> public void setName(final String name) {
> this.name = name;
> }
> public String toString() {
> return "" + name;
> }
> }{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, 7 months
[JBoss JIRA] (FORGE-912) UI Scaffolding does not support entities with EmbeddedId
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-912?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-912:
-------------------------------------
Issue Type: Release (was: Story)
> UI Scaffolding does not support entities with EmbeddedId
> --------------------------------------------------------
>
> Key: FORGE-912
> URL: https://issues.jboss.org/browse/FORGE-912
> Project: Forge
> Issue Type: Release
> Components: Scaffold
> Affects Versions: 1.3.0.Final
> Environment: Linux 3.8 - Firefox 20 - MySQL 5.5 - PostgresSQL 9.1
> Reporter: Hanine Hanynowsky
> Priority: Critical
>
> UI Scaffolding does not support Entities with EnbeddedId.
> The value of ID generated is always null and there is no way to view a corresponding object.
> The generated entity and EmbeddedId class seem fine to me. The issue is with the VIEW scaffolding (The beans and the way XHTML files values are binded).
--
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, 7 months
[JBoss JIRA] (FORGE-912) UI Scaffolding does not support entities with EmbeddedId
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-912?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-912:
-------------------------------------
Issue Type: Story (was: Release)
> UI Scaffolding does not support entities with EmbeddedId
> --------------------------------------------------------
>
> Key: FORGE-912
> URL: https://issues.jboss.org/browse/FORGE-912
> Project: Forge
> Issue Type: Story
> Components: Scaffold
> Affects Versions: 1.3.0.Final
> Environment: Linux 3.8 - Firefox 20 - MySQL 5.5 - PostgresSQL 9.1
> Reporter: Hanine Hanynowsky
> Priority: Critical
>
> UI Scaffolding does not support Entities with EnbeddedId.
> The value of ID generated is always null and there is no way to view a corresponding object.
> The generated entity and EmbeddedId class seem fine to me. The issue is with the VIEW scaffolding (The beans and the way XHTML files values are binded).
--
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, 7 months
[JBoss JIRA] (FORGE-924) It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-924?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on FORGE-924:
------------------------------------------
Yes, if you could list out the specific commands that do not provide default values, we can probably take care of this in the next release! Thanks for bringing this issue to our attention!
> It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-924
> URL: https://issues.jboss.org/browse/FORGE-924
> Project: Forge
> Issue Type: Feature Request
> Components: Forge Scripting Language
> Affects Versions: 1.3.0.Final
> Reporter: Ãbner Oliveira
>
> I'm writing a script to server as a start point to a trainning session in my company. I had some problems because some plugins hava prompts for select versions and there is no way to automatize the process.
> I asked for solution in the #forge channel and one solution was expose the queueInputLines in some way.
> The simplest solution is change the plugins to expose arguments in the commands to allow set the default value for incoming prompts.
--
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, 7 months
[JBoss JIRA] (FORGE-924) It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/FORGE-924?page=com.atlassian.jira.plugin.... ]
Koen Aers commented on FORGE-924:
---------------------------------
Hi Abner, I think it would be a good idea to create corresponding issues for each offending plugin compiling all the prompts-without-default or prompts-without-arguments.
> It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-924
> URL: https://issues.jboss.org/browse/FORGE-924
> Project: Forge
> Issue Type: Feature Request
> Components: Forge Scripting Language
> Affects Versions: 1.3.0.Final
> Reporter: Ãbner Oliveira
>
> I'm writing a script to server as a start point to a trainning session in my company. I had some problems because some plugins hava prompts for select versions and there is no way to automatize the process.
> I asked for solution in the #forge channel and one solution was expose the queueInputLines in some way.
> The simplest solution is change the plugins to expose arguments in the commands to allow set the default value for incoming prompts.
--
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, 7 months
[JBoss JIRA] (FORGE-927) Add Ajax support for Searching entities.
by Hanine Hanynowsky (JIRA)
[ https://issues.jboss.org/browse/FORGE-927?page=com.atlassian.jira.plugin.... ]
Hanine Hanynowsky updated FORGE-927:
------------------------------------
Description:
For a better user experience, adding ajax support for searching entities will be appreciated.
Here are the modifications to have such support:
For example: Let's consider the entity : *World.java*
1- change the method {{public void paginate(){}}} to {{public void paginate(AjaxBehaviorEvent event){}}} in *WorldBean.java*
2- in */world/search.xhtml* : change =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" />}}
bq. to =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
3- embed : {{<f:ajax />}} in {{<h:inputText}} fields and/or {{<h:selecOneMenu}} ... components.....this way:
{{<h:inputText ........>}}
{{<f:ajax event="keyup" render="the_id_of_the_datatable"}} {{execute="@form" />}}
{{</h:inputText>}}
Remark: the ajax event for SelectOneMenu is click, not keyup.
4- finally in *WorldBean.java*, modify the create method, so that it becomes:
bq. {{public String create() {}}
{{if (this.conversation.isTransient()) {}}
{{this.conversation.begin();}}
{{} else {}}
{{this.conversation.end();}}
{{}}}
{{return "create?faces-redirect=true";}}
{{}}}}}
5- Optional: remove the search button in *search.xhtml*
That's all.
Ideally, Forge should let the developer specify if he/she would like to generate these statements in order to enable Ajax or not. Example:
{{*scaffold-x from World.java --enableAjax true*}}
was:
For a better user experience, adding ajax support for searching entities will be appreciated.
Here are the modifications to have such support:
For example: Let's consider the entity : *World.java*
1- change the method {{public void paginate(){}}} to {{public void paginate(AjaxBehavioreven event){}}} in *WorldBean.java*
2- in */world/search.xhtml* : change =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" />}}
bq. to =>
bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
3- embed : {{<f:ajax />}} in {{<h:inputText}} fields and/or {{<h:selecOneMenu}} ... components.....this way:
{{<h:inputText ........>}}
{{<f:ajax event="keyup" render="the_id_of_the_datatable"}} {{execute="@form" />}}
{{</h:inputText>}}
Remark: the ajax event for SelectOneMenu is click, not keyup.
4- finally in *WorldBean.java*, modify the create method, so that it becomes:
bq. {{public String create() {}}
{{if (this.conversation.isTransient()) {}}
{{this.conversation.begin();}}
{{} else {}}
{{this.conversation.end();}}
{{}}}
{{return "create?faces-redirect=true";}}
{{}}}}}
5- Optional: remove the search button in *search.xhtml*
That's all.
Ideally, Forge should let the developer specify if he/she would like to generate these statements in order to enable Ajax or not. Example:
{{*scaffold-x from World.java --enableAjax true*}}
> Add Ajax support for Searching entities.
> ----------------------------------------
>
> Key: FORGE-927
> URL: https://issues.jboss.org/browse/FORGE-927
> Project: Forge
> Issue Type: Feature Request
> Components: Scaffold
> Affects Versions: 2.0.0.Alpha4
> Environment: Any
> Reporter: Hanine Hanynowsky
> Priority: Optional
>
> For a better user experience, adding ajax support for searching entities will be appreciated.
> Here are the modifications to have such support:
> For example: Let's consider the entity : *World.java*
> 1- change the method {{public void paginate(){}}} to {{public void paginate(AjaxBehaviorEvent event){}}} in *WorldBean.java*
> 2- in */world/search.xhtml* : change =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate()}" />}}
> bq. to =>
> bq. {{<f:event type="preRenderView" listener="#{helpBean.paginate(this)}" />}}
> 3- embed : {{<f:ajax />}} in {{<h:inputText}} fields and/or {{<h:selecOneMenu}} ... components.....this way:
> {{<h:inputText ........>}}
> {{<f:ajax event="keyup" render="the_id_of_the_datatable"}} {{execute="@form" />}}
> {{</h:inputText>}}
> Remark: the ajax event for SelectOneMenu is click, not keyup.
> 4- finally in *WorldBean.java*, modify the create method, so that it becomes:
> bq. {{public String create() {}}
> {{if (this.conversation.isTransient()) {}}
> {{this.conversation.begin();}}
> {{} else {}}
> {{this.conversation.end();}}
> {{}}}
> {{return "create?faces-redirect=true";}}
> {{}}}}}
> 5- Optional: remove the search button in *search.xhtml*
> That's all.
> Ideally, Forge should let the developer specify if he/she would like to generate these statements in order to enable Ajax or not. Example:
> {{*scaffold-x from World.java --enableAjax true*}}
--
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, 7 months