[JBoss JIRA] (FORGE-1962) CLAC throws NPE with proxied ArrayList
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1962?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1962:
-----------------------------------
Fix Version/s: 2.7.3.Final
> CLAC throws NPE with proxied ArrayList
> --------------------------------------
>
> Key: FORGE-1962
> URL: https://issues.jboss.org/browse/FORGE-1962
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Furnace (Container)
> Affects Versions: 2.7.2.Final
> Environment: Windows 7 64bit, JDK8, Furnace embedded in IntelliJ plugin
> Reporter: Adam Wyłuda
> Fix For: 2.7.3.Final
>
>
> When ArrayList is passed to a proxied object, CLAC creates another proxy for the passed list. The problem is, that this proxy is ForgeProxy, but behaves like unwrapped object (it doesn't have getHandler() method). When the same list is being retrieved from the proxied object, CLAC throws NPE in stripClassLoaderAdapters() method, because isForgeProxy(list) returns true, but getForgeProxyHandler(list) is null.
> Stack trace:
> {code}
> java.lang.NullPointerException
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.stripClassLoaderAdapters(ClassLoaderAdapterCallback.java:414)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:237)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$300(ClassLoaderAdapterCallback.java:37)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_ca9c3fe3-6195-4aaf-8a37-f0adc8d997f5.getValue(AbstractFaceted_$$_javassist_ca9c3fe3-6195-4aaf-8a37-f0adc8d997f5.java)
> at org.jboss.forge.plugin.idea.ui.component.many.CheckBoxTableComponentBuilder$1.updateState(CheckBoxTableComponentBuilder.java:90)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1962) CLAC throws NPE with proxied ArrayList
by Adam Wyłuda (JIRA)
Adam Wyłuda created FORGE-1962:
----------------------------------
Summary: CLAC throws NPE with proxied ArrayList
Key: FORGE-1962
URL: https://issues.jboss.org/browse/FORGE-1962
Project: Forge
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Furnace (Container)
Affects Versions: 2.7.2.Final
Environment: Windows 7 64bit, JDK8, Furnace embedded in IntelliJ plugin
Reporter: Adam Wyłuda
When ArrayList is passed to a proxied object, CLAC creates another proxy for the passed list. The problem is, that this proxy is ForgeProxy, but behaves like unwrapped object (it doesn't have getHandler() method). When the same list is being retrieved from the proxied object, CLAC throws NPE in stripClassLoaderAdapters() method, because isForgeProxy(list) returns true, but getForgeProxyHandler(list) is null.
Stack trace:
{code}
java.lang.NullPointerException
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.stripClassLoaderAdapters(ClassLoaderAdapterCallback.java:414)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:237)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$300(ClassLoaderAdapterCallback.java:37)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:40)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_ca9c3fe3-6195-4aaf-8a37-f0adc8d997f5.getValue(AbstractFaceted_$$_javassist_ca9c3fe3-6195-4aaf-8a37-f0adc8d997f5.java)
at org.jboss.forge.plugin.idea.ui.component.many.CheckBoxTableComponentBuilder$1.updateState(CheckBoxTableComponentBuilder.java:90)
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (ROASTER-27) Create an API for producing String representations of Roaster model objects
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-27?page=com.atlassian.jira.plugin... ]
George Gastaldi moved FORGE-1930 to ROASTER-27:
-----------------------------------------------
Project: Roaster (was: Forge)
Key: ROASTER-27 (was: FORGE-1930)
Component/s: API
(was: Parsers / File Manipulation)
> Create an API for producing String representations of Roaster model objects
> ---------------------------------------------------------------------------
>
> Key: ROASTER-27
> URL: https://issues.jboss.org/browse/ROASTER-27
> Project: Roaster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: API
> Reporter: Vineet Reynolds
>
> Based on the [discussion here|https://github.com/forge/core/pull/484/files#r14695944] it would be a good idea to create a Roaster based API where snippets of code could be created as String objects to be embedded in templates.
> The snippets could be created with Roaster model objects. The new API would be responsible for exporting the model as a String. The existing Roaster model may not be good enough and require extension, since it assumes/expects the presence of a target or a source to begin with (like a JavaClassSource or a Method or a Field all of which may not be convenient to create).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1960) Support creation and management of Cordova projects
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1960?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1960:
-----------------------------------
Fix Version/s: 2.x Future
> Support creation and management of Cordova projects
> ---------------------------------------------------
>
> Key: FORGE-1960
> URL: https://issues.jboss.org/browse/FORGE-1960
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Projects
> Affects Versions: 2.7.2.Final
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> We should support creation of new Cordova projects in Forge. This is primarily to help with FORGEPLUGINS-113 and FORGEPLUGINS-166 so that projects with a different build system unlike Maven or Gradle can be supported by Forge.
> We should also allow existing Cordova projects to be recognized as projects in Forge so that additional contextual commands maybe activated for the benefit of end-users.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1033) Review the path spec for shell file and directory paths on Linux and Windows
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1033?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1033.
----------------------------------
Fix Version/s: (was: 2.x Future)
Resolution: Out of Date
Forge 2 should not have this problem, given that we change the impl to Aesh
> Review the path spec for shell file and directory paths on Linux and Windows
> ----------------------------------------------------------------------------
>
> Key: FORGE-1033
> URL: https://issues.jboss.org/browse/FORGE-1033
> Project: Forge
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: UI - Shell
> Affects Versions: 1.3.3.Final
> Reporter: Vineet Reynolds
>
> Coming from the fix for FORGE-93, it is desirable to document the path specification for files and directories in both Linux (and Mac OS X), and Windows. In Linux, {{'/'}} is the only allowed separator, whereas in Windows, both {{'\'}} and {{'/'}} are allowed.
> This obviously has an impact on the FSH script compatibility across these OSes. On the other hand, constraining the directory separator to {{'/'}} for Windows, to achieve commonality would probably work against usability as well as result in unusable paths in Windows.
> Additionally, escape sequences need to be determined (for escaping whitespaces and other characters that can be interpreted differently by the shell), and whether paths need to be quoted to handle whitespaces etc. Autocompletion of inputs should ideally work in both of these cases.
> Discuss.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1961) Incorrect default value for database in JPA:Setup when JBoss Enterprise Application Server is chosen
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1961?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1961.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.7.3.Final
Resolution: Done
> Incorrect default value for database in JPA:Setup when JBoss Enterprise Application Server is chosen
> ----------------------------------------------------------------------------------------------------
>
> Key: FORGE-1961
> URL: https://issues.jboss.org/browse/FORGE-1961
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java EE
> Affects Versions: 2.7.2.Final
> Reporter: Vineet Reynolds
> Assignee: George Gastaldi
> Fix For: 2.7.3.Final
>
>
> The default value for the database input field is HSQLDB instead of H2, when the application server is selected as JBoss EAP (the default). This results in an incorrect dialect being specified in the project's persistence.xml file.
> Apparently this appears to cause no problems, since the dialects might be similar, but this should still be fixed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months