[JBoss JIRA] (FORGE-1445) ls command on an entity is not as clear
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1445:
----------------------------------------
Summary: 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
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 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, 3 months
[JBoss JIRA] (FORGE-1399) Cannot create a relationship between two entities
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1399?page=com.atlassian.jira.plugin... ]
Antonio Goncalves edited comment on FORGE-1399 at 1/15/14 4:18 PM:
-------------------------------------------------------------------
I've installed the latest SNAPSHOT of Forge 2.Beta and I still cannot create realtionships. Here is what happens when I create a {{Speaker}} entity and then try to create a One-to-Many between {{Talk}} and {{Speaker}} :
{code}
[Talk.java]$ jpa-new-field --named speakers --entity org.forge2s.test.model.Speaker --relationshipType One-to-Many
***ERROR*** cannot obtain stream to file: file does not exist: /Users/antoniombp/Documents/Code/temp/Forge/forge2s/src/main/java/String.java
{code}
Don't know where the {{String.java}} comes from
was (Author: agoncal):
I've installed the latest SNAPSHOP of Forge 2.Beta and I still cannot create realtionships. Here is what happens when I create a {{Speaker}} entity and then try to create a One-to-Many between {{Talk}} and {{Speaker}} :
{code}
[Talk.java]$ jpa-new-field --named speakers --entity org.forge2s.test.model.Speaker --relationshipType One-to-Many
***ERROR*** cannot obtain stream to file: file does not exist: /Users/antoniombp/Documents/Code/temp/Forge/forge2s/src/main/java/String.java
{code}
Don't know where the {{String.java}} comes from
> Cannot create a relationship between two entities
> -------------------------------------------------
>
> Key: FORGE-1399
> URL: https://issues.jboss.org/browse/FORGE-1399
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I've created a {{Country}} entity and then a {{Customer}}. When I create a relationship between both, I have an error :
> {code}
> [Customer.java]$ jpa-new-field --named country --entity org.agoncal.application.petstore.model.Country --relationshipType Many-to-One
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> [Customer.java]$ jpa-setup
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> {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, 3 months
[JBoss JIRA] (FORGE-1399) Cannot create a relationship between two entities
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1399?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1399:
------------------------------------------
I've installed the latest SNAPSHOP of Forge 2.Beta and I still cannot create realtionships. Here is what happens when I create a {{Speaker}} entity and then try to create a One-to-Many between {{Talk}} and {{Speaker}} :
{code}
[Talk.java]$ jpa-new-field --named speakers --entity org.forge2s.test.model.Speaker --relationshipType One-to-Many
***ERROR*** cannot obtain stream to file: file does not exist: /Users/antoniombp/Documents/Code/temp/Forge/forge2s/src/main/java/String.java
{code}
Don't know where the {{String.java}} comes from
> Cannot create a relationship between two entities
> -------------------------------------------------
>
> Key: FORGE-1399
> URL: https://issues.jboss.org/browse/FORGE-1399
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I've created a {{Country}} entity and then a {{Customer}}. When I create a relationship between both, I have an error :
> {code}
> [Customer.java]$ jpa-new-field --named country --entity org.agoncal.application.petstore.model.Country --relationshipType Many-to-One
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> [Customer.java]$ jpa-setup
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> {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, 3 months
[JBoss JIRA] (FORGE-1444) jpa-new-field --entity disapearing on TAB completion
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1444?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1444:
-------------------------------------
Summary: jpa-new-field --entity disapearing on TAB completion (was: jpa-new-field --typeName disapearing on TAB completion)
Description:
I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--entity}} parameter
{code}
[Talk.java]$ jpa-new-field --named speakers --
--typeName --lob --relationshipType --entity --length --primitive
{code}
But if I set the relationship first, and then hit TAB, the {{--entity}} parameter doesn't show
{code}
[Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many --
--inverseFieldName --cascadeType --fetchType --required
{code}
Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear
was:
I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--typeName}} parameter
{code}
[Talk.java]$ jpa-new-field --named speakers --
--typeName --lob --relationshipType --entity --length --primitive
{code}
But if I set the relationship first, and then hit TAB, the {{--typeName}} parameter doesn't show
{code}
[Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many --
--inverseFieldName --cascadeType --fetchType --required
{code}
Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear
> jpa-new-field --entity disapearing on TAB completion
> ----------------------------------------------------
>
> Key: FORGE-1444
> URL: https://issues.jboss.org/browse/FORGE-1444
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--entity}} parameter
> {code}
> [Talk.java]$ jpa-new-field --named speakers --
> --typeName --lob --relationshipType --entity --length --primitive
> {code}
> But if I set the relationship first, and then hit TAB, the {{--entity}} parameter doesn't show
> {code}
> [Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many --
> --inverseFieldName --cascadeType --fetchType --required
> {code}
> Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear
--
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, 3 months
[JBoss JIRA] (FORGE-1444) jpa-new-field --typeName disapearing on TAB completion
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1444:
----------------------------------------
Summary: jpa-new-field --typeName disapearing on TAB completion
Key: FORGE-1444
URL: https://issues.jboss.org/browse/FORGE-1444
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
Fix For: 2.x Future
I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--typeName}} parameter
{code}
[Talk.java]$ jpa-new-field --named speakers --
--typeName --lob --relationshipType --entity --length --primitive
{code}
But if I set the relationship first, and then hit TAB, the {{--typeName}} parameter doesn't show
{code}
[Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many --
--inverseFieldName --cascadeType --fetchType --required
{code}
Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear
--
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, 3 months
[JBoss JIRA] (FORGE-1443) database.action property in persistence.xml should be drop-and-create
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1443:
----------------------------------------
Summary: database.action property in persistence.xml should be drop-and-create
Key: FORGE-1443
URL: https://issues.jboss.org/browse/FORGE-1443
Project: Forge
Issue Type: Sub-task
Components: Scaffold
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
Fix For: 2.x Future
When you setup JPA in Forge 1.x you get :
{code}
<property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
{code}
In Forge 2.Beta instead of {{drop-and-create}} you get only {{create}} :
{code}
<property name="javax.persistence.schema-generation.database.action" value="create"/>
{code}
Instead you should have
{code}
<property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/>
{code}
And by the way, why not generating the DDL script as well ? You could have :
{code}
<property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation.scripts.create-target" value="<projectName>Create.ddl"/>
<property name="javax.persistence.schema-generation.scripts.drop-target" value="<projectName>Drop.ddl"/>
{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, 3 months