[JBoss JIRA] (FORGE-1420) Create a UICommand to create test classes
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1420:
--------------------------------------
Summary: Create a UICommand to create test classes
Key: FORGE-1420
URL: https://issues.jboss.org/browse/FORGE-1420
Project: Forge
Issue Type: Feature Request
Components: Blessed Plugins, Test Harness
Reporter: George Gastaldi
Fix For: 2.x Future
There should be two commands:
- should be able to setup test dependencies;
- should be able to create a test class and configure the Furnace Arquillian provider
--
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, 3 months
[JBoss JIRA] (FORGE-1407) Shell is missing options in wizards where default values allow immediately moving to next step
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1407?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1407.
----------------------------------
Assignee: George Gastaldi (was: Lincoln Baxter III)
Resolution: Done
Fixed
> Shell is missing options in wizards where default values allow immediately moving to next step
> ----------------------------------------------------------------------------------------------
>
> Key: FORGE-1407
> URL: https://issues.jboss.org/browse/FORGE-1407
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.0.0.Final
>
>
> Should have a lot more options:
> {code}
> [jpa-demo]$ jpa-setup
> --dataSourceName --dbType --persistenceUnitName
> {code}
> The problem is here in ShellWizard.java (in shell addon)
> {code}
> private CommandLineParser populate(ShellContext shellContext, String line,
> final Map<String, InputComponent<?, ?>> inputs)
> throws Exception
> {
> inputs.putAll(getController().getInputs());
> CommandLineParser parser = commandLineUtil.generateParser(getController(), shellContext, inputs);
> CommandLine cmdLine = parser.parse(line, true);
> Map<String, InputComponent<?, ?>> populatedInputs = commandLineUtil.populateUIInputs(cmdLine, inputs);
> if (getController().isValid())
> {
> if (getController().canMoveToNextStep())
> {
> // The bug is here. we are immediately moving to the next step and removing all inputs that are not populated.
> // this really needs to know if we have defaulted to next step or actually moved there willingly
> // it should not remove old choices until a new choice has been made
> getController().next().initialize();
> inputs.keySet().retainAll(populatedInputs.keySet());
> parser = populate(shellContext, line, inputs);
> }
> }
> return parser;
> }
> {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, 3 months
[JBoss JIRA] (FORGE-1419) Review the addon structure for scaffold and scaffold-faces
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1419:
--------------------------------------
Summary: Review the addon structure for scaffold and scaffold-faces
Key: FORGE-1419
URL: https://issues.jboss.org/browse/FORGE-1419
Project: Forge
Issue Type: Task
Components: Scaffold
Affects Versions: 2.0.0.Beta4
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Currently there is some form of interdependency between the scaffold addon and the scaffold-faces addon. The scaffold-faces addon depends on the APIs and SPIs provided by the scaffold addon, while the scaffold-addon embeds the scaffold-faces addon. This was done so that the faces addon that supplies JSF scaffolding is available OOTB, without requiring an additional addon to be installed.
We need to simplify this, since this is confusing for maintenance.
--
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, 3 months
[JBoss JIRA] (FORGE-1415) Target Unreachable, 'entityName' returned null after Bean Validation failure
by Esteve Aviles (JIRA)
[ https://issues.jboss.org/browse/FORGE-1415?page=com.atlassian.jira.plugin... ]
Esteve Aviles commented on FORGE-1415:
--------------------------------------
George,
You can clone https://github.com/esteveavi/forge-test .
To reproduce the problem, remove errors configuration from web.xml and try to save the entity 'Item' twice with the field 'name' with the same value. It will cause a ConstraintViolationException as it is marked Unique. When you change the field name to a different value you will get:
javax.servlet.ServletException: /item/create.xhtml @41,72 value="#{itemBean.item.name}": Target Unreachable, 'item' returned null
javax.faces.webapp.FacesServlet.service(FacesServlet.java:606)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
root cause
javax.el.PropertyNotFoundException: /item/create.xhtml @41,72 value="#{itemBean.item.name}": Target Unreachable, 'item' returned null
com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100)
com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95)
javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030)
javax.faces.component.UIInput.validate(UIInput.java:960)
javax.faces.component.UIInput.executeValidate(UIInput.java:1233)
javax.faces.component.UIInput.processValidators(UIInput.java:698)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214)
javax.faces.component.UIForm.processValidators(UIForm.java:253)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214)
javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214)
javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1172)
com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
Thanks in advance.
> Target Unreachable, 'entityName' returned null after Bean Validation failure
> ----------------------------------------------------------------------------
>
> Key: FORGE-1415
> URL: https://issues.jboss.org/browse/FORGE-1415
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.3.Final
> Environment: JBossAS7.1
> Reporter: Esteve Aviles
>
> Hi,
> When you want to persist a new entity through create.xhtml page and the information produces a server side error then the error is show and when you fix it and try to summit again an Exception occurs:
> {noformat}
> /view/operacio/inventariMobilePos/create.xhtml @50,58 value="#{inventariMobilePosBean.inventariMobilePos.codiTmb}": Target Unreachable, 'inventariMobilePos' returned null
> {noformat}
--
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, 3 months
[JBoss JIRA] (FORGE-1407) Shell is missing options in wizards where default values allow immediately moving to next step
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1407?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III reopened FORGE-1407:
---------------------------------------
Not quite working for the `scaffold-setup` wizard:
{code}
[jpa-demo]$ scaffold-
scaffold-generate scaffold-setup
[jpa-demo]$ scaffold-setup --facesVersion 2.
2.2 2.1 2.0
[jpa-demo]$ scaffold-setup --facesVersion 2.
2.2 2.1 2.0
[jpa-demo]$ scaffold-setup --facesVersion 2.2
{code}
As you can see, the options that should be available are not, and the wizard moves immediately to the next setup step:
{code}
@Inject
@WithAttributes(label = "Provider", required = true)
private UISelectOne<ScaffoldProvider> provider;
@Inject
@WithAttributes(label = "Target Directory")
private UIInput<String> target;
@Inject
@WithAttributes(label = "Overwrite existing files?", defaultValue = "false")
private UIInput<Boolean> overwrite;
{code}
> Shell is missing options in wizards where default values allow immediately moving to next step
> ----------------------------------------------------------------------------------------------
>
> Key: FORGE-1407
> URL: https://issues.jboss.org/browse/FORGE-1407
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Lincoln Baxter III
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Final
>
>
> Should have a lot more options:
> {code}
> [jpa-demo]$ jpa-setup
> --dataSourceName --dbType --persistenceUnitName
> {code}
> The problem is here in ShellWizard.java (in shell addon)
> {code}
> private CommandLineParser populate(ShellContext shellContext, String line,
> final Map<String, InputComponent<?, ?>> inputs)
> throws Exception
> {
> inputs.putAll(getController().getInputs());
> CommandLineParser parser = commandLineUtil.generateParser(getController(), shellContext, inputs);
> CommandLine cmdLine = parser.parse(line, true);
> Map<String, InputComponent<?, ?>> populatedInputs = commandLineUtil.populateUIInputs(cmdLine, inputs);
> if (getController().isValid())
> {
> if (getController().canMoveToNextStep())
> {
> // The bug is here. we are immediately moving to the next step and removing all inputs that are not populated.
> // this really needs to know if we have defaulted to next step or actually moved there willingly
> // it should not remove old choices until a new choice has been made
> getController().next().initialize();
> inputs.keySet().retainAll(populatedInputs.keySet());
> parser = populate(shellContext, line, inputs);
> }
> }
> return parser;
> }
> {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, 3 months