[JBoss JIRA] (FORGE-893) UIInput<?> should support setValidator(UIIInputValidator) getValidator() for input-level-validation
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-893?page=com.atlassian.jira.plugin.... ]
George Gastaldi reassigned FORGE-893:
-------------------------------------
Assignee: George Gastaldi
> UIInput<?> should support setValidator(UIIInputValidator) getValidator() for input-level-validation
> ---------------------------------------------------------------------------------------------------
>
> Key: FORGE-893
> URL: https://issues.jboss.org/browse/FORGE-893
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Eclipse, UI - IntelliJ IDEA, UI - Shell
> Affects Versions: 2.0.0.Alpha3
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> Currently Forge 2 UI API supports command-level validation, but we don't support field-level validation, which would be useful for dev simplification/ease of use.
> This may or may not be able to live on the base InputComponent interface, but more likely it will need to be customized for each of UISelectOne, UISelectMany, UIInput, and UIInputMany types.
> {code}
> public interface InputComponent<IMPLTYPE, VALUETYPE> extends Faceted<HintsFacet>
> {
> Validator<VALUETYPE> getValidator();
> IMPLTYPE setValidator(Validator<VALUETYPE>);
> }
> {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
11 years, 1 month
[JBoss JIRA] (FORGE-1129) Support interactive merging of changes performed on existing files
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1129:
--------------------------------------
Summary: Support interactive merging of changes performed on existing files
Key: FORGE-1129
URL: https://issues.jboss.org/browse/FORGE-1129
Project: Forge
Issue Type: Feature Request
Components: UI - API, UI - Eclipse, UI - IntelliJ IDEA, UI - Shell
Reporter: Vineet Reynolds
Fix For: 2.x Future
Currently, in Forge 1, we merely prompt the users to overwrite the existing file if located. Either the existing file is lost or the changes made by Forge are not saved. No attempt is made to retain the existing file with changes performed by the user, while merging in changes performed by Forge.
Forge should support interactive diffing and merging of the changes made on the existing file. Integration with existing diff tools in various IDEs and shells would be a plus.
This should ideally be exposed as a service for other addons.
--
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
11 years, 1 month
[JBoss JIRA] (FORGE-606) Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-606?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds commented on FORGE-606:
---------------------------------------
Introduced a strategy option to create two-level DTOs that resolve this. More strategies would be added later as this matures. FORGE-1061 and FORGE-1094 are other related issues that would determine the strategies to use.
> Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities
> ----------------------------------------------------------------------------------------------
>
> Key: FORGE-606
> URL: https://issues.jboss.org/browse/FORGE-606
> Project: Forge
> Issue Type: Feature Request
> Components: Blessed Plugins
> Reporter: Dan Allen
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 1.x Future
>
>
> Currently the REST plugin generates broken endpoints if there are cyclic references in the JPA entities. Forge should provide a plugin to hep the developer resolve these references to get past this bump in the road.
--
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
11 years, 1 month
[JBoss JIRA] (FORGEPLUGINS-133) Arquillian Forge plugin installation fails on Forge 1.3.3.FINAL
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-133?page=com.atlassian.jira.... ]
Vineet Reynolds commented on FORGEPLUGINS-133:
----------------------------------------------
Sadly, I'm unable to reproduce this on the current Forge master.
> Arquillian Forge plugin installation fails on Forge 1.3.3.FINAL
> ---------------------------------------------------------------
>
> Key: FORGEPLUGINS-133
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-133
> Project: Forge Plugins
> Issue Type: Bug
> Components: Arquillian Plugin
> Environment: Forge 1.3.3.Final
> Reporter: Vineet Reynolds
> Assignee: Aslak Knutsen
>
> Cloned from : https://github.com/forge/plugin-arquillian/issues/31
> Plugin install fails with forge 1.3.3.FINAL. I am trying to follow the arquillian tutorial.
> {noformat}
> forge install-plugin arquillian
> Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
> ***INFO*** Preparing to install plugin: arquillian
> ***INFO*** Checking out plugin source files to [/tmp/forgetemp2717179280024408314] via 'git'
> ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
> ***INFO*** Project found
> ***INFO*** Name: arquillian-plugin
> ***INFO*** Version: 1.0.0-SNAPSHOT
> ***INFO*** Type: Java Application
> ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] y
> ***INFO*** Project found
> ***INFO*** Name: arquillian-demo
> ***INFO*** Version: 1.0.0-SNAPSHOT
> ***INFO*** Type: Java Application
> ***INFO*** Cleaning up temp workspace [/tmp/forgetemp2717179280024408314]
> Wrote /home/dbeer/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
> Deleted /tmp/forgetemp2717179280024408314
> ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> java.lang.NullPointerException
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:625)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:414)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:233)
> 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:795)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608)
> 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:724)
> {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
11 years, 1 month
[JBoss JIRA] (FORGE-1060) REST plugin should support creation of DTOs for the underlying JPA entities of REST resources
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1060?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1060.
----------------------------------
Fix Version/s: 1.4.0.Final
Resolution: Done
Merged
> REST plugin should support creation of DTOs for the underlying JPA entities of REST resources
> ---------------------------------------------------------------------------------------------
>
> Key: FORGE-1060
> URL: https://issues.jboss.org/browse/FORGE-1060
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 1.4.0.Final
>
>
> Using JPA entities directly in the REST resources is obviously not proving to be of much help:
> * It leads to problems when working with cyclic dependencies, as seen in FORGE-606. Using {{@JsonIdentityInfo}} to resolve this has lead to further problems on the client side due to the lack of support in JavaScript clients to handle JSON object references out of the box.
> * It requires the entire object graph to be eagerly fetched and made available during the serialization process. During deserialization, JPA merges could result in incorrect behavior since merges of object graphs depend on whether the collection was previously fetched or not. Merges are not expected to occur by spec, unless the collection was fetched. See [HHH-4135|https://hibernate.atlassian.net/browse/HHH-4135] and [HHH-5187|https://hibernate.atlassian.net/browse/HHH-5187] for some details on Hibernate, with differing behavior in EclipseLink.
> * It requires manipulation of the relational associations across entities to modify the resource representations, thus lacking separation of concerns.
> * It provides no control over the depth of the object graph to be serialized. Annotations like {{@JsonIgnore}} are required to be placed on JPA entities which does not aid in separation of concerns. Custom serializers/deserializers offer little benefit concerning standards since they requires compilation against specific versions of the JSON libraries like Jackson for every container that is to be supported.
> Therefore it is proposed to have the REST plugin create DTOs for representing the state of the JPA entities in the REST resources.
--
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
11 years, 1 month
[JBoss JIRA] (FORGEPLUGINS-133) Arquillian Forge plugin installation fails on Forge 1.3.3.FINAL
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGEPLUGINS-133:
--------------------------------------------
Summary: Arquillian Forge plugin installation fails on Forge 1.3.3.FINAL
Key: FORGEPLUGINS-133
URL: https://issues.jboss.org/browse/FORGEPLUGINS-133
Project: Forge Plugins
Issue Type: Bug
Components: Arquillian Plugin
Environment: Forge 1.3.3.Final
Reporter: Vineet Reynolds
Assignee: Aslak Knutsen
Cloned from : https://github.com/forge/plugin-arquillian/issues/31
Plugin install fails with forge 1.3.3.FINAL. I am trying to follow the arquillian tutorial.
{noformat}
forge install-plugin arquillian
Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
***INFO*** Preparing to install plugin: arquillian
***INFO*** Checking out plugin source files to [/tmp/forgetemp2717179280024408314] via 'git'
***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
***INFO*** Project found
***INFO*** Name: arquillian-plugin
***INFO*** Version: 1.0.0-SNAPSHOT
***INFO*** Type: Java Application
? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] y
***INFO*** Project found
***INFO*** Name: arquillian-demo
***INFO*** Version: 1.0.0-SNAPSHOT
***INFO*** Type: Java Application
***INFO*** Cleaning up temp workspace [/tmp/forgetemp2717179280024408314]
Wrote /home/dbeer/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
Deleted /tmp/forgetemp2717179280024408314
***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
java.lang.NullPointerException
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:625)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:414)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:233)
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:795)
at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818)
at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608)
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:724)
{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
11 years, 1 month