[JBoss JIRA] (FORGE-1807) Being able to have inheritance and implementation in most of the generated artifacts
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1807:
----------------------------------------
Summary: Being able to have inheritance and implementation in most of the generated artifacts
Key: FORGE-1807
URL: https://issues.jboss.org/browse/FORGE-1807
Project: Forge
Issue Type: Feature Request
Components: Java EE
Affects Versions: 2.5.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
Most of the generated artifact could benefit from being able to extend classes and/or implement interfaces. Something like :
{code}
jpa-new-entity --named Customer --extends Person
jpa-new-entity --named Customer --extends Person --implements Clonable, Identifiable
java-new-class --named MyClass --extends MyAbstractClass
java-new-class --named MyClass --extends MyAbstractClass --implements Serializable
cdi-new-bean --named MyBean --extends MyAbstractBean
cdi-new-bean --named MyBean --extends MyAbstractClass --implements MyInterface
ejb-new-bean --named MyEJB --extends MyAbstractService
ejb-new-bean --named MyEjb --implements MyInterface
faces-new-bean --named MyBackingBean --implements MyInterface
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1478) Being able to have inheritance in JPA
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1478?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1478:
-------------------------------------
Parent Issue: FORGE-1807 (was: FORGE-1491)
> Being able to have inheritance in JPA
> -------------------------------------
>
> Key: FORGE-1478
> URL: https://issues.jboss.org/browse/FORGE-1478
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE, UI - Shell
> Affects Versions: 2.0.0.CR2
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> JPA inheritance is really needed. It would be good to have an option to create an entity that inherits either from a java class, an entity or a mapped superclass. Something like :
> {code}
> jpa-new-entity --named Customer --extends Person
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1445) ls command on an entity is not as clear
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1445?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1445:
----------------------------------------
Thank you Robert, just merged your changes
> ls command on an entity is not as clear
> ---------------------------------------
>
> Key: FORGE-1445
> URL: https://issues.jboss.org/browse/FORGE-1445
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: Robert Balent
> Fix For: 2.5.1.Final
>
>
> When I've created an entity and type the {{ls}} command, in Forge 1.x I have the following (in color) :
> {code}
> [forge1] Talk.java $ ls
> [fields]
> private::Date::date; private::Long::id; private::String::description; private::String::room; private::String::title;
> private::int::version;
> [methods]
> public::equals(Object that)::boolean public::getDate()::Date public::getDescription()::String
> public::getId()::Long public::getRoom()::String public::getTitle()::String
> public::getVersion()::int public::hashCode()::int public::setDate(final Date date)::void
> public::setDescription(final String description)::void public::setId(final Long id)::void public::setRoom(final String room)::void
> public::setTitle(final String title)::void public::setVersion(final int version)::void public::toString()::String
> {code}
> While in Forge 2.Beta I have :
> {code}
> [Talk.java]$ ls
> date::Date getDate()::Date getRoom()::String hashCode()::int setDate(Date)::void setRoom(String)::void title::String
> description::String getDescription()::String getTitle()::String id::Long setDescription(String)::void setTitle(String)::void toString()::String
> equals(Object)::boolean getId()::Long getVersion()::int room::String setId(Long)::void setVersion(int)::void version::int
> {code}
> Despite the Forge 1.x output being in color and not the Forge 2.Beta output (which always helps in readability), there is not separation between {{[fields]}} and {{[methods]}}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1445) ls command on an entity is not as clear
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1445?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1445:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.5.1.Final
(was: 2.x Future)
Resolution: Done
> ls command on an entity is not as clear
> ---------------------------------------
>
> Key: FORGE-1445
> URL: https://issues.jboss.org/browse/FORGE-1445
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: Robert Balent
> Fix For: 2.5.1.Final
>
>
> When I've created an entity and type the {{ls}} command, in Forge 1.x I have the following (in color) :
> {code}
> [forge1] Talk.java $ ls
> [fields]
> private::Date::date; private::Long::id; private::String::description; private::String::room; private::String::title;
> private::int::version;
> [methods]
> public::equals(Object that)::boolean public::getDate()::Date public::getDescription()::String
> public::getId()::Long public::getRoom()::String public::getTitle()::String
> public::getVersion()::int public::hashCode()::int public::setDate(final Date date)::void
> public::setDescription(final String description)::void public::setId(final Long id)::void public::setRoom(final String room)::void
> public::setTitle(final String title)::void public::setVersion(final int version)::void public::toString()::String
> {code}
> While in Forge 2.Beta I have :
> {code}
> [Talk.java]$ ls
> date::Date getDate()::Date getRoom()::String hashCode()::int setDate(Date)::void setRoom(String)::void title::String
> description::String getDescription()::String getTitle()::String id::Long setDescription(String)::void setTitle(String)::void toString()::String
> equals(Object)::boolean getId()::Long getVersion()::int room::String setId(Long)::void setVersion(int)::void version::int
> {code}
> Despite the Forge 1.x output being in color and not the Forge 2.Beta output (which always helps in readability), there is not separation between {{[fields]}} and {{[methods]}}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1445) ls command on an entity is not as clear
by Robert Balent (JIRA)
[ https://issues.jboss.org/browse/FORGE-1445?page=com.atlassian.jira.plugin... ]
Robert Balent updated FORGE-1445:
---------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/455
I've created pull request[1]. Please comment if you have any concerns or you want to change anything. Now it is showing fields and methods separately.
Thanks.
[1] https://github.com/forge/core/pull/455
> ls command on an entity is not as clear
> ---------------------------------------
>
> Key: FORGE-1445
> URL: https://issues.jboss.org/browse/FORGE-1445
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: Robert Balent
> Fix For: 2.x Future
>
>
> When I've created an entity and type the {{ls}} command, in Forge 1.x I have the following (in color) :
> {code}
> [forge1] Talk.java $ ls
> [fields]
> private::Date::date; private::Long::id; private::String::description; private::String::room; private::String::title;
> private::int::version;
> [methods]
> public::equals(Object that)::boolean public::getDate()::Date public::getDescription()::String
> public::getId()::Long public::getRoom()::String public::getTitle()::String
> public::getVersion()::int public::hashCode()::int public::setDate(final Date date)::void
> public::setDescription(final String description)::void public::setId(final Long id)::void public::setRoom(final String room)::void
> public::setTitle(final String title)::void public::setVersion(final int version)::void public::toString()::String
> {code}
> While in Forge 2.Beta I have :
> {code}
> [Talk.java]$ ls
> date::Date getDate()::Date getRoom()::String hashCode()::int setDate(Date)::void setRoom(String)::void title::String
> description::String getDescription()::String getTitle()::String id::Long setDescription(String)::void setTitle(String)::void toString()::String
> equals(Object)::boolean getId()::Long getVersion()::int room::String setId(Long)::void setVersion(int)::void version::int
> {code}
> Despite the Forge 1.x output being in color and not the Forge 2.Beta output (which always helps in readability), there is not separation between {{[fields]}} and {{[methods]}}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1445) ls command on an entity is not as clear
by Robert Balent (JIRA)
[ https://issues.jboss.org/browse/FORGE-1445?page=com.atlassian.jira.plugin... ]
Robert Balent reassigned FORGE-1445:
------------------------------------
Assignee: Robert Balent
> ls command on an entity is not as clear
> ---------------------------------------
>
> Key: FORGE-1445
> URL: https://issues.jboss.org/browse/FORGE-1445
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: Robert Balent
> Fix For: 2.x Future
>
>
> When I've created an entity and type the {{ls}} command, in Forge 1.x I have the following (in color) :
> {code}
> [forge1] Talk.java $ ls
> [fields]
> private::Date::date; private::Long::id; private::String::description; private::String::room; private::String::title;
> private::int::version;
> [methods]
> public::equals(Object that)::boolean public::getDate()::Date public::getDescription()::String
> public::getId()::Long public::getRoom()::String public::getTitle()::String
> public::getVersion()::int public::hashCode()::int public::setDate(final Date date)::void
> public::setDescription(final String description)::void public::setId(final Long id)::void public::setRoom(final String room)::void
> public::setTitle(final String title)::void public::setVersion(final int version)::void public::toString()::String
> {code}
> While in Forge 2.Beta I have :
> {code}
> [Talk.java]$ ls
> date::Date getDate()::Date getRoom()::String hashCode()::int setDate(Date)::void setRoom(String)::void title::String
> description::String getDescription()::String getTitle()::String id::Long setDescription(String)::void setTitle(String)::void toString()::String
> equals(Object)::boolean getId()::Long getVersion()::int room::String setId(Long)::void setVersion(int)::void version::int
> {code}
> Despite the Forge 1.x output being in color and not the Forge 2.Beta output (which always helps in readability), there is not separation between {{[fields]}} and {{[methods]}}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1804) Generated code is not properly indented
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1804?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1804:
------------------------------------------
It's really weird. I've updated to the latest version of the code, executed the exact same commands, and ended up with badly formatted code.
Could anyone else tried ? I'm running on a Mac with JDK 1.7_45
> Generated code is not properly indented
> ---------------------------------------
>
> Key: FORGE-1804
> URL: https://issues.jboss.org/browse/FORGE-1804
> Project: Forge
> Issue Type: Enhancement
> Components: Java EE
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> *The affected version is 2.5.1-SNAPSHOT*. I noticed a regression in 2.5.1-SNAPSHOT.
> I create an Entity and an EJB :
> {code}
> [temp]$ project-new --named proj251
> [proj251]$ jpa-new-entity --named MyEntity
> [MyEntity.java]$ ejb-new-bean --named MyService
> {code}
> If I run this script in 2.5.0 the generated code is well indented. Here for the entity :
> {code}
> import java.lang.Override;
> @Entity
> public class MyEntity implements Serializable
> {code}
> And for the EJB :
> {code}
> import java.io.Serializable;
> @Stateless
> @LocalBean
> public class MyService implements Serializable
> {code}
> But when I do that with 2.5.1-SNAPSHOT, the class annotation is not right :
> {code}
> import java.lang.Override;@Entity
> public class MyEntity implements Serializable {
> {code}
> And
> {code}
> import java.io.Serializable;@Stateless
> @LocalBean
> public class MyService implements Serializable {
> {code}
> I haven't tried with all the other artifacts, I'm wondering if it's on all the generated code or not
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months