[JBoss JIRA] (FORGE-1303) Use Weld's new Singleton API
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1303?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1303.
-------------------------------------
Resolution: Won't Fix
Probably won't fix this unless we move to using WeldBootstrap in the future. But thanks!
> Use Weld's new Singleton API
> ----------------------------
>
> Key: FORGE-1303
> URL: https://issues.jboss.org/browse/FORGE-1303
> Project: Forge
> Issue Type: Task
> Components: Furnace (Container)
> Reporter: Jozef Hartinger
>
> Since Weld 2.1 it is possible to use the new Singleton API http://docs.jboss.org/weld/javadoc/2.1/weld-spi/org/jboss/weld/bootstrap/...
> A String identifier was added to all Singleton's methods. The identifier is used to identify a Weld container. As a result, it is no longer necessary to use the TCCL to identify the right Weld container.
> I am not sure if Forge currently sets the TCCL just because Weld required it in the past or if it is used for something else but either way the new SPI should simplify integration.
> For each module Forge should generate a unique id and pass it to Weld when calling WeldBootstrap.startContainer().
--
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, 5 months
[JBoss JIRA] (FORGE-1309) Git apply command fails if the --directory option is specified
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1309?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1309.
-------------------------------------
Resolution: Won't Fix
Unfortunately, due to the fact that this is an FSH parsing issue related to MVEL, we won't be able to fix this. But you can probably get it to work by some creative quoting.
> Git apply command fails if the --directory option is specified
> --------------------------------------------------------------
>
> Key: FORGE-1309
> URL: https://issues.jboss.org/browse/FORGE-1309
> Project: Forge
> Issue Type: Bug
> Components: Builtin Plugins, UI - Shell
> Affects Versions: 1.4.1.Final
> Reporter: Vineet Reynolds
>
> This seems to be an issue in Shell or the Git plugin, or both.
> Running the following command: {{git apply -v --directory=demo --ignore-whitespace --ignore-space-change patches/admin_layer_functional.patch;}} blows up with the following error:
> {noformat}
> ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> [Error: could not access: git; in class: org.jboss.forge.shell.command.fshparser.FSHRuntime]
> [Near : {... git apply -v --directory = dem ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:676)
> at org.mvel2.PropertyAccessor.getNormal(PropertyAccessor.java:178)
> at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:147)
> at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:127)
> at org.mvel2.ast.ASTNode.getReducedValue(ASTNode.java:187)
> at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:106)
> at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:49)
> at org.mvel2.MVEL.eval(MVEL.java:185)
> at org.jboss.forge.shell.command.fshparser.Parse.executeScript(Parse.java:138)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue.reduce(AutoReducingQueue.java:84)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue.peek(AutoReducingQueue.java:75)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue$1.next(AutoReducingQueue.java:171)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue$1.next(AutoReducingQueue.java:159)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:78)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.shell(FSHRuntime.java:117)
> at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1104)
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:987)
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:344)
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:143)
> at org.mvel2.optimizers.dynamic.DynamicOptimizer.optimizeAccessor(DynamicOptimizer.java:67)
> at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159)
> at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85)
> at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:100)
> at org.mvel2.ast.IfNode.getReducedValueAccelerated(IfNode.java:74)
> at org.mvel2.ast.IfNode.getReducedValueAccelerated(IfNode.java:77)
> at org.mvel2.compiler.ExecutableAccessor.getValue(ExecutableAccessor.java:38)
> at org.mvel2.ast.IfNode.getReducedValueAccelerated(IfNode.java:74)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85)
> at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113)
> at org.mvel2.ast.Function.call(Function.java:157)
> at org.mvel2.PropertyAccessor.getMethod(PropertyAccessor.java:885)
> at org.mvel2.PropertyAccessor.getNormal(PropertyAccessor.java:181)
> at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:147)
> at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:127)
> at org.mvel2.ast.ASTNode.getReducedValue(ASTNode.java:187)
> at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:106)
> at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:49)
> at org.mvel2.MVEL.eval(MVEL.java:185)
> at org.jboss.forge.shell.command.fshparser.Parse.executeScript(Parse.java:138)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue.reduce(AutoReducingQueue.java:84)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue.peek(AutoReducingQueue.java:75)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue$1.next(AutoReducingQueue.java:171)
> at org.jboss.forge.shell.command.fshparser.AutoReducingQueue$1.next(AutoReducingQueue.java:159)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:78)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:938)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.execute(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> at org.jboss.forge.shell.plugins.builtin.RunPlugin.run(RunPlugin.java:46)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
> The same command works in bash.
--
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, 5 months
[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-974:
-------------------------------------
Fix Version/s: 2.x Future
> Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-974
> URL: https://issues.jboss.org/browse/FORGE-974
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.3.1.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 2.x Future
>
>
> The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA.
> This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state.
> Addition of members to the collection property are however performed correctly. Since the Faces scaffold does not allow updates to properties of the the individual members in the collection, no other issue is observed, except for the inability to update the collection state correctly.
--
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, 5 months
[JBoss JIRA] (FORGE-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-914:
-------------------------------------
Fix Version/s: 2.x Future
(was: 1.x Future)
> Rework the handling of 1:M relationships by the Faces/RichFaces scaffold
> ------------------------------------------------------------------------
>
> Key: FORGE-914
> URL: https://issues.jboss.org/browse/FORGE-914
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.0.5.Final, 1.3.0.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 2.x Future
>
>
> The generated Faces scaffold for 1:M relationships does not handle certain usability aspects.
> For example, a new row is automatically added by default when displaying a 1:M relationship upon create. However, unless the add button is clicked, the contents of the row are not added to the underlying managed bean. If the add button is not clicked, the contents of the row are not treated as a new item to be added. This is very confusing.
> Also, if bean validation is performed on the entities (in the rows of the 1:M relationship), and if it fails, then the contents need to be corrected, even though they may not be persisted in the database. Again, this is confusing behavior.
> Additionally, deletion of entities from the collection (1-side of the association) seems to be broken (FORGE-974).
--
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, 5 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III closed FORGE-875.
------------------------------------
Fix Version/s: 2.0.0.Beta4
(was: 1.x Future)
Resolution: Out of Date
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Bug
> Components: Scaffold, UI - Eclipse
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Assignee: Koen Aers
> Priority: Critical
> Labels: forge
> Fix For: 2.0.0.Beta4
>
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
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, 5 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:
-------------------------------------
Fix Version/s: 2.x Future
(was: 1.x Future)
> 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
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 2.x Future
>
>
> 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, 5 months