November 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-393) PersistencePlugin should create Lists, not Sets, for @OneToMany

by Richard Kennard (Created) (JIRA)

PersistencePlugin should create Lists, not Sets, for @OneToMany --------------------------------------------------------------- Key: FORGE-393 URL: https://issues.jboss.org/browse/FORGE-393 Project: Forge Issue Type: Enhancement Reporter: Richard Kennard It would be cleaner for the UI if the persistence plugin could base its collections on Lists, rather than Sets. This is because JSF's built-in h:dataTable needs something with a defined ordering. It is possible to work around this in various ways, such as adding special getters to the view Bean, but I think for the sake of clear, concise code the easiest way would be to make the generated code be a List. For example: @OneToMany private List<Grocery> groceries = new ArrayList<Grocery>(); public List<Grocery> getGroceries() { return this.groceries; } public void setGroceries(final List<Grocery> groceries) { this.groceries = groceries; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (FORGE-386) PersistencePlugin needs to generate hashCode and equals based on Id

by Richard Kennard (Created) (JIRA)

PersistencePlugin needs to generate hashCode and equals based on Id ------------------------------------------------------------------- Key: FORGE-386 URL: https://issues.jboss.org/browse/FORGE-386 Project: Forge Issue Type: Enhancement Reporter: Richard Kennard Assignee: Lincoln Baxter III Domain classes generated by Forge need to override hashCode/equals if they are to be useful in a UI (among other places). This is hard to do if we know nothing about the semantics of the class, but the PersistencePlugin *does* know something: namely, the Id. The following implementation would suffice for my purposes: @Override public boolean equals(Object that) { if (this == that) { return true; } if (that == null) { return false; } if (getClass() != that.getClass()) { return false; } if (id != null) { return id.equals(((Employer) that).id); } return super.equals(that); } @Override public int hashCode() { if (id != null) { return id.hashCode(); } return super.hashCode(); } But I'm happy for other implementations too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] (FORGE-388) Better support for multi-modules projects in FORGE

by Serhiy V (Created) (JIRA)

Better support for multi-modules projects in FORGE -------------------------------------------------- Key: FORGE-388 URL: https://issues.jboss.org/browse/FORGE-388 Project: Forge Issue Type: Feature Request Components: Forge Build, Maven Integration, Shell Affects Versions: 1.0.0.Beta3 Environment: Any Reporter: Serhiy V By default "new-project" command creates a simple "war" project with everything inside. This is good for simple projects. But in real world scenario you will most likely would like to split your project on few modules - e.g. "common", "integration", "business" and "ui". How to do this with FORGE? Well, it's still a maven projects so you can manually edit pom.xml files and add necessary dependencies and changes. But will FORGE be able to setup JPA in "integration" module (should be packaged as jar) and use it "ui" module which should be packages as war? Same questions with other functionality like ability to have EJBs in "business" and test them with arquillian. And what about EAR support? I can't find any documentation or samples howto do this with current FORGE. List of all available commands does not return anything that can be used to break projects into modules or add existing projects to the current project as new modules. There is a FORGE-120 issue. ButI've just downloaded forge-distribution-1.0.0.Beta3.zip and there is no such functionality there. >From my point of view it is really important to support complex projects but not just simple single war projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
8
0 / 0

[JBoss JIRA] (FORGE-394) Attach the Actual Option Values to the CommandExecuted Event

by Koen Aers (Created) (JIRA)

Attach the Actual Option Values to the CommandExecuted Event ------------------------------------------------------------ Key: FORGE-394 URL: https://issues.jboss.org/browse/FORGE-394 Project: Forge Issue Type: Feature Request Components: Shell Affects Versions: 1.0.0.Beta3 Reporter: Koen Aers Assignee: Koen Aers Fix For: 1.0.0.Beta4 It is not only needed to have the metadata about the executed command, also the actual values are needed to do meaningful stuff afterwards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (FORGE-395) Fix Broken JavaClassTest on Windows

by Koen Aers (Created) (JIRA)

Fix Broken JavaClassTest on Windows ----------------------------------- Key: FORGE-395 URL: https://issues.jboss.org/browse/FORGE-395 Project: Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.0.0.Beta3 Reporter: Koen Aers Assignee: Koen Aers Fix For: 1.0.0.Beta4 The assertions in the test depend on the line separator being '\n'. This is not platform independent. The correct way is to use System.getProperty("line.separator"). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (FORGE-387) org.jboss.forge.parser.java.Method needs getGenericReturnType (or equivalent)

by Richard Kennard (Created) (JIRA)

org.jboss.forge.parser.java.Method needs getGenericReturnType (or equivalent) ----------------------------------------------------------------------------- Key: FORGE-387 URL: https://issues.jboss.org/browse/FORGE-387 Project: Forge Issue Type: Enhancement Reporter: Richard Kennard Assignee: Lincoln Baxter III Currently, if I have a method... public List<Foo> getList(); ...then org.jboss.forge.parser.java.Method.getReturnType() returns... java.util.List There doesn't appear to be a way to get hold of the generic type <Foo>? java.lang.Method has a special method 'getGenericReturnType' method which returns a ParameterizedType which you can then call 'getActualTypeArguments' on. I don't necessarily like that API, but we need some equivalent to it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
3
0 / 0

[JBoss JIRA] (FORGE-370) org.jboss.forge.parser.java.Annotation.getQualifiedName()

by Richard Kennard (Created) (JIRA)

org.jboss.forge.parser.java.Annotation.getQualifiedName() --------------------------------------------------------- Key: FORGE-370 URL: https://issues.jboss.org/browse/FORGE-370 Project: Forge Issue Type: Feature Request Reporter: Richard Kennard Assignee: Lincoln Baxter III org.jboss.forge.parser.java.Annotation.getName() appears to return the name (eg. Id), not the fully qualified name (eg. javax.persistence.Id), of the annotation. I need the fully qualified name so that I can instantiate the actual annotation (see https://issues.jboss.org/browse/FORGE-369). Although, if FORGE-369 is done maybe the qualified name can be handled internally instead? I don't have a use case requiring both. Up to you. Lincoln said: "I think we'd need to look at the parent Source File and figure out if there is a matching Import, then also add a getQualifiedName() method to this Interface" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (FORGE-366) new-plugin command throws a NPE

by Paul Bakker (Created) (JIRA)

new-plugin command throws a NPE ------------------------------- Key: FORGE-366 URL: https://issues.jboss.org/browse/FORGE-366 Project: Forge Issue Type: Bug Components: Builtin Plugins Reporter: Paul Bakker Assignee: Lincoln Baxter III $ plugins new-plugin --named EasyTest ? In which package you'd like to create [EasyTest], or enter for default [demo] easytest ***ERROR*** [plugins new-plugin] null org.jboss.forge.shell.exceptions.CommandExecutionException at org.jboss.forge.shell.command.Execution.perform(Execution.java:152) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:716) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:500) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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:87) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.forge.shell.command.Execution.perform(Execution.java:147) ... 30 more Caused by: java.lang.NullPointerException at org.jboss.seam.render.template.CompositionContext.peek(CompositionContext.java:91) at org.jboss.seam.render.template.CompiledTemplateResource.<init>(CompiledTemplateResource.java:72) at org.jboss.seam.render.TemplateCompiler.compile(TemplateCompiler.java:131) at org.jboss.seam.render.TemplateCompiler.compile(TemplateCompiler.java:121) at org.jboss.seam.render.TemplateCompiler.compileResource(TemplateCompiler.java:85) at org.jboss.forge.dev.PluginsPlugin.newPlugin(PluginsPlugin.java:110) ... 35 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (FORGE-371) Method.getReturnType does not return fully qualified name

by Richard Kennard (Created) (JIRA)

Method.getReturnType does not return fully qualified name --------------------------------------------------------- Key: FORGE-371 URL: https://issues.jboss.org/browse/FORGE-371 Project: Forge Issue Type: Feature Request Reporter: Richard Kennard Assignee: Lincoln Baxter III org.jboss.forge.parser.java.Method.getReturnType returns a String, rather than a JavaClass, because "there's no way to tell if the type we are returning is actually something we can get the sources of" (Lincoln). I think this is fine, but if we're using Strings it needs to be the fully qualified name, or else there's no way to understand what it actually is. At the moment it just returns "Long" instead of "java.lang.Long" and "Date" instead of "java.util.Date" etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] (FORGE-381) Add forge version command

by Pete Muir (Created) (JIRA)

Add forge version command ------------------------- Key: FORGE-381 URL: https://issues.jboss.org/browse/FORGE-381 Project: Forge Issue Type: Feature Request Affects Versions: 1.0.0.Beta3 Reporter: Pete Muir Assignee: Lincoln Baxter III Very useful to be able to quickly determine the version I'm using! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2011