[JBoss JIRA] (FORGE-972) The generated Faces scaffold contains functional errors for entities with immutable properties or collections of immutable properties
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-972?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-972:
-------------------------------------
Fix Version/s: 2.x Future
> The generated Faces scaffold contains functional errors for entities with immutable properties or collections of immutable properties
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-972
> URL: https://issues.jboss.org/browse/FORGE-972
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 1.3.1.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Fix For: 2.x Future
>
>
> This is related to an issue in the generated scaffold of the TicketMonster model: JDF-391.
> The generated Faces scaffold does not treat immutable properties and collections of immutable properties differently. Differential treatment is required since immutable properties lack setters and hence instances of them need to be created via the specialized constructors that exist for the immutable entities.
> Updates of immutable properties will require deletion of existing immutable instances followed by creation of new ones.
--
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
[JBoss JIRA] (FORGE-1075) REST plugin should detect if an existing JAX-RS resource is mapped to the same @Path
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1075?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1075:
--------------------------------------
Fix Version/s: 2.x Future
> REST plugin should detect if an existing JAX-RS resource is mapped to the same @Path
> ------------------------------------------------------------------------------------
>
> Key: FORGE-1075
> URL: https://issues.jboss.org/browse/FORGE-1075
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.3.3.Final
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> When an existing resource in a project already maps to a Path, it may conflict with the JAX-RS resource newly created by the REST plugin.
> The REST plugin should therefore create the JAX-RS resource only when it is certain (to a degree) that there are no conflicting paths.
> This would have to be done for several cases including:
> * JAX-RS resources
> * JAX-RS sub-resources
> * JAX-RS resources and sub-resources across projects (may have to wait until binary inspection can be done)
--
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
[JBoss JIRA] (FORGE-1044) Redirect Furnace output to a file
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1044?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1044:
--------------------------------------
Fix Version/s: 2.x Future
> Redirect Furnace output to a file
> ---------------------------------
>
> Key: FORGE-1044
> URL: https://issues.jboss.org/browse/FORGE-1044
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha7
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> At the moment, I need to start Eclipse from a console, and monitor the console output to determine failures in Weld like WELD-001408 errors, since all such output is written to System.out/System.err. This is not intuitive.
> It would be better to write this out to the workbench log (preferably, unless there is a better place in Eclipse for this), or some log file in {{~/.forge}}.
--
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
[JBoss JIRA] (FORGEPLUGINS-151) Forge OpenShift plugin hangs when creating a JBoss app in Windows
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-151?page=com.atlassian.jira.... ]
Lincoln Baxter III moved FORGE-1054 to FORGEPLUGINS-151:
--------------------------------------------------------
Project: Forge Plugins (was: Forge)
Key: FORGEPLUGINS-151 (was: FORGE-1054)
Affects Version/s: (was: 1.3.3.Final)
> Forge OpenShift plugin hangs when creating a JBoss app in Windows
> -----------------------------------------------------------------
>
> Key: FORGEPLUGINS-151
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-151
> Project: Forge Plugins
> Issue Type: Bug
> Environment: Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> Reporter: nan wei
> Assignee: William DeCoste
>
> Description of problem:
> When creating a jboss app, app creation process hang there.
> Version:
> forge-distribution-1.3.3.Final.zip
> Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> How reproducible:
> always
> Steps to Reproduce:
> 1. Ensure that you have already installed a Java 6+ JDK.
> 1.1 install jdk-7u25-windows-x64
> 1.2 set JAVA_HOME.
> 2. Download Forge 1.3.2.Final and Un-zip Forge into a folder on your hard-disk, this folder will be your FORGE_HOME.
> 2.1 Add '$FORGE_HOME/bin' to your windows path.
> 2.2 installing Git(Git-1.8.3-preview2013.6.1)
> 3. Open a command prompt and run 'forge.bat'.
> 4. Install OpenShift plugin for forge.
> 5. create a jboss app.
> Actual results:
> [forge-openshift-demo] forge-openshift-demo $ rhc setup
> ***INFO*** Loaded OpenShift configuration from C:\Users\nanwei/.openshift/expres
> s.conf
> ? Enter the application name [forgeopenshiftd] [forgeopenshiftd] wsy
> ***INFO*** Using RHLOGIN:nwei for https://10.4.59.171
> ? Enter your Red Hat Openshift password: ******
> ***INFO*** Found OpenShift User: nwei
> Choose a JBoss Cartridge:
>
> 1 - [Cartridge [name=jbosseap-6.0]]*
> 2 - [Cartridge [name=jbossews-2.0]]
> 3 - [Cartridge [name=jbossews-1.0]]
>
> ? Choose an option by typing the number of the selection [*-default] [0] 1
> ***INFO*** Using JBoss Cartridge: jbosseap-6.0
> Initialized empty Git repository in C:/Users/nanwei/Downloads/forge/bin/forge-op
> enshift-demo/.git/
> ***INFO*** Waiting for OpenShift to propagate DNS
> ***INFO*** Trying to contact http://forge-nweidomain.osetestv2.com/ (attempt 1 of
> 500)
> Updating openshift
> Expected results:
> The process will hang there for ever.
> Additional info:
--
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
[JBoss JIRA] (FORGEPLUGINS-151) Forge OpenShift plugin hangs when creating a JBoss app in Windows
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-151?page=com.atlassian.jira.... ]
Lincoln Baxter III updated FORGEPLUGINS-151:
--------------------------------------------
Component/s: OpenShift Plugin
> Forge OpenShift plugin hangs when creating a JBoss app in Windows
> -----------------------------------------------------------------
>
> Key: FORGEPLUGINS-151
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-151
> Project: Forge Plugins
> Issue Type: Bug
> Components: OpenShift Plugin
> Environment: Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> Reporter: nan wei
> Assignee: William DeCoste
>
> Description of problem:
> When creating a jboss app, app creation process hang there.
> Version:
> forge-distribution-1.3.3.Final.zip
> Window7
> Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> How reproducible:
> always
> Steps to Reproduce:
> 1. Ensure that you have already installed a Java 6+ JDK.
> 1.1 install jdk-7u25-windows-x64
> 1.2 set JAVA_HOME.
> 2. Download Forge 1.3.2.Final and Un-zip Forge into a folder on your hard-disk, this folder will be your FORGE_HOME.
> 2.1 Add '$FORGE_HOME/bin' to your windows path.
> 2.2 installing Git(Git-1.8.3-preview2013.6.1)
> 3. Open a command prompt and run 'forge.bat'.
> 4. Install OpenShift plugin for forge.
> 5. create a jboss app.
> Actual results:
> [forge-openshift-demo] forge-openshift-demo $ rhc setup
> ***INFO*** Loaded OpenShift configuration from C:\Users\nanwei/.openshift/expres
> s.conf
> ? Enter the application name [forgeopenshiftd] [forgeopenshiftd] wsy
> ***INFO*** Using RHLOGIN:nwei for https://10.4.59.171
> ? Enter your Red Hat Openshift password: ******
> ***INFO*** Found OpenShift User: nwei
> Choose a JBoss Cartridge:
>
> 1 - [Cartridge [name=jbosseap-6.0]]*
> 2 - [Cartridge [name=jbossews-2.0]]
> 3 - [Cartridge [name=jbossews-1.0]]
>
> ? Choose an option by typing the number of the selection [*-default] [0] 1
> ***INFO*** Using JBoss Cartridge: jbosseap-6.0
> Initialized empty Git repository in C:/Users/nanwei/Downloads/forge/bin/forge-op
> enshift-demo/.git/
> ***INFO*** Waiting for OpenShift to propagate DNS
> ***INFO*** Trying to contact http://forge-nweidomain.osetestv2.com/ (attempt 1 of
> 500)
> Updating openshift
> Expected results:
> The process will hang there for ever.
> Additional info:
--
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