July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-770: ------------------------------------- Summary: Ability to restrict ServiceRegistry and AddonRegistry services by version (was: Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version ) Fix Version/s: 2.0.0.Alpha7 (was: 2.x Future) > Ability to restrict ServiceRegistry and AddonRegistry services by version > ------------------------------------------------------------------------- > > Key: FORGE-770 > URL: https://issues.jboss.org/browse/FORGE-770 > Project: Forge > Issue Type: Feature Request > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha7 > > > Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.) > {code} > (A) -> (B, v1) > -> Service 1 > (B, v2) > -> Service 1v2 > -> Service 2v1 > {code} > A should receive only the instance of Service 1 from (B, v1) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1006) The entity plugin should generate equals and hashcode implementations considering all suitable fields in the JPA entity

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1006: -------------------------------------- Summary: The entity plugin should generate equals and hashcode implementations considering all suitable fields in the JPA entity Key: FORGE-1006 URL: https://issues.jboss.org/browse/FORGE-1006 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds As a result for FORGE-995 and FORGE-1005 the generated {{equals}} and {{hashcode}} implementations for JPA entities would be typically incorrect due to reliance on the auto-generated primary key value. Additionally, since the {[equals}} and {{hashCode}} methods are generated only once during creation of the JPA entity class, these methods would be out of date as more fields are added (unlike the {{toString}} method). We should enhance or regenerate the existing methods as new fields are added via the field plugin. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1005) Consider Superclasses other than Object during generation of equals and hashcode implementations

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1005: -------------------------------------- Summary: Consider Superclasses other than Object during generation of equals and hashcode implementations Key: FORGE-1005 URL: https://issues.jboss.org/browse/FORGE-1005 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds The current generated implementations of {{equals}} and {{hashCode}} (in FORGE-995) do not delegate to the super class of the object. This should be done for all types whose immediate super classes are not {{Object}}. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-914) Rework the handling of 1:M relationships by the Faces/RichFaces scaffold

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on FORGE-914: ----------------------------------------------- Sneha <snagarwa(a)redhat.com> made a comment on [bug 977956|https://bugzilla.redhat.com/show_bug.cgi?id=977956] Updated doc text. > 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 > Fix For: 1.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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1004) Display a descriptive text for dependencies in the New Forge Addon dialog

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1004: -------------------------------------- Summary: Display a descriptive text for dependencies in the New Forge Addon dialog Key: FORGE-1004 URL: https://issues.jboss.org/browse/FORGE-1004 Project: Forge Issue Type: Feature Request Components: UI - API Affects Versions: 2.0.0.Alpha5 Reporter: Vineet Reynolds Priority: Minor It would be better to have some descriptive text that provide information about each addon that can be added as a dependency when creating a new Forge addon project. At the moment, only the GAV of the addon is displayed which is not informative to beginners. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-995) The generated hashcode() and equals() methods should not reference the hardcoded 'id' field

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-995?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-995: ---------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.3.Final 2.0.0.Alpha7 Resolution: Done > The generated hashcode() and equals() methods should not reference the hardcoded 'id' field > ------------------------------------------------------------------------------------------- > > Key: FORGE-995 > URL: https://issues.jboss.org/browse/FORGE-995 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The field name(s) should be provided as a parameter -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1003) Parse a JavaClass from an URL

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1003?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1003. ---------------------------------- Resolution: Done > Parse a JavaClass from an URL > ----------------------------- > > Key: FORGE-1003 > URL: https://issues.jboss.org/browse/FORGE-1003 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.3.2.Final, 2.0.0.Alpha6 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > It should be possible to parse classes from URLs -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-889) Cannot parse package-info.java

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-889?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-889. --------------------------------- Assignee: Yann Albou Resolution: Done > Cannot parse package-info.java > ------------------------------ > > Key: FORGE-889 > URL: https://issues.jboss.org/browse/FORGE-889 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Yann Albou > Assignee: Yann Albou > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The parsing of package-info.java file (see http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javadoc.html...) raises the following exeption: > "org.jboss.forge.parser.ParserException: Could not find type declaration in Java source - is this actually 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-889) Cannot parse package-info.java

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-889?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-889: --------------------------------------- Changes merged > Cannot parse package-info.java > ------------------------------ > > Key: FORGE-889 > URL: https://issues.jboss.org/browse/FORGE-889 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Yann Albou > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The parsing of package-info.java file (see http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javadoc.html...) raises the following exeption: > "org.jboss.forge.parser.ParserException: Could not find type declaration in Java source - is this actually 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1003) Parse a JavaClass from an URL

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1003: -------------------------------------- Summary: Parse a JavaClass from an URL Key: FORGE-1003 URL: https://issues.jboss.org/browse/FORGE-1003 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.0.0.Alpha6, 1.3.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 1.3.3.Final, 2.0.0.Alpha7 It should be possible to parse classes from URLs -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013