[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1787:
------------------------------------------
Hum... and of course, when there is a one to many relationship, the {{view.xhtml}} does not work either. It has :
{code}
<h:dataTable id="cDBeanCDMusicians" styleClass="data-table" value="#{forgeview:asList(CDBean.CD.musicians)}" var="_item">
<h:column>
<f:facet name="header">
<h:outputText value="First Name"/>
</f:facet>
<h:link outcome="/musician/view">
<f:param name="id" value="#{_item.id}"/>
<h:outputText id="itemFirstName" value="#{_item.firstName}"/>
</h:link>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Last Name"/>
</f:facet>
<h:link outcome="/musician/view">
<f:param name="id" value="#{_item.id}"/>
<h:outputText id="itemLastName" value="#{_item.lastName}"/>
</h:link>
</h:column>
</h:dataTable>
{code}
Instead of
{code}
<h:dataTable id="cDBeanCDMusicians" styleClass="data-table" value="#{forgeview:asList(CDBean.CD.musicians)}" var="_item">
<h:column>
<f:facet name="header">
<h:outputText value="First Name"/>
</f:facet>
<h:link outcome="/admin/musician/view">
<f:param name="id" value="#{_item.id}"/>
<h:outputText id="itemFirstName" value="#{_item.firstName}"/>
</h:link>
</h:column>
<h:column>
<f:facet name="header">
<h:outputText value="Last Name"/>
</f:facet>
<h:link outcome="/admin/musician/view">
<f:param name="id" value="#{_item.id}"/>
<h:outputText id="itemLastName" value="#{_item.lastName}"/>
</h:link>
</h:column>
</h:dataTable>
{code}
> When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right
> --------------------------------------------------------------------------------------------
>
> Key: FORGE-1787
> URL: https://issues.jboss.org/browse/FORGE-1787
> Project: Forge
> Issue Type: Bug
> Components: Scaffold
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 2.5.1.Final
>
>
> When scaffolding a JSF application, without using a {{--webRoot}} parameter, the navigation in the {{pageTemplate.xhtml}} works as expected :
> {code}
> scaffold-setup ;
> scaffold-generate --targets org.agoncal.training.javaee6adv.model.Author ;
> scaffold-generate --targets org.agoncal.training.javaee6adv.model.CD ;
> {code}
> The template navigation looks like :
> {code}
> <ul>
> <li>
> <h:link outcome="/CD/search" value="CD"/>
> </li>
> <li>
> <h:link outcome="/author/search" value="Author"/>
> </li>
> </ul>
> {code}
> But if I specify the {{--webRoot}} parameter, then the navigation does not work as there is a {{/}} missing :
> {code}
> scaffold-setup ;
> scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.Author ;
> scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.CD ;
> {code}
> The template :
> {code}
> <ul>
> <li>
> <h:link outcome="admin/CD/search" value="CD"/>
> </li>
> <li>
> <h:link outcome="admin/author/search" value="Author"/>
> </li>
> </ul>
> {code}
> The correct navigation would be :
> {code}
> <ul>
> <li>
> <h:link outcome="/admin/CD/search" value="CD"/>
> </li>
> <li>
> <h:link outcome="/admin/author/search" value="Author"/>
> </li>
> </ul>
> {code}
> The only way to make it work is to add a {{/}} to the {{webroot}}, which is not very intuitive :
> {code}
> scaffold-setup ;
> scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.Author ;
> scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.CD ;
> {code}
> But this trick doesn't work for the {{search.xhtml}} page. The generated code is :
> {code}
> <h:link outcome="/genre/view">
> <f:param name="id" value="#{_item.id}"/>
> <h:outputText id="itemName" value="#{_item.name}"/>
> </h:link>
> {code}
> The {{outcome}} is not right, and should contain a {{/admin}}
> {code}
> <h:link outcome="/admin/genre/view">
> <f:param name="id" value="#{_item.id}"/>
> <h:outputText id="itemName" value="#{_item.name}"/>
> </h:link>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1802) Console hangs when running an invalid script
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1802:
----------------------------------------
Summary: Console hangs when running an invalid script
Key: FORGE-1802
URL: https://issues.jboss.org/browse/FORGE-1802
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.5.0.Final
Reporter: Antonio Goncalves
Priority: Critical
Fix For: 2.x Future
I am executing a script (with the {{run}} command) and the console hanged and stopped working completely (I had to kill the process). I realized that there is an error in the script (missing {{;}} at the end of line {{--named ISBN}}).
Take the following script, and save it on a {{hangs.fsh}} file
{code}
# ##################### #
# Creates a new project #
# ##################### #
project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
# Setup the persistence unit in persistence.xml
# ############
jpa-setup --persistenceUnitName cdbookstorePU ;
# ######################## #
# Creates the domain model #
# ######################## #
# ISBN constraint
# ############
constraint-new-annotation --named ISBN
# Genre entity
# ############
jpa-new-entity --named Genre ;
jpa-new-field --named name --length 100 ;
{code}
Now, execute the script, and see the error message :
{code}
[temp]$ run hangs.fsh
project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
***SUCCESS*** Project named 'cdbookstore' has been created.
[cdbookstore]$ jpa-setup --persistenceUnitName cdbookstorePU ;
***SUCCESS*** Persistence (JPA) is installed.
[cdbookstore]$ constraint-new-annotation --named ISBN
***SUCCESS*** Bean Validation Constraint Annotations org.agoncal.training.javaee6adv.constraints.ISBN was created
[ISBN.java]$ jpa-new-entity --named Genre ;
Exception when parsing/running: jpa-new-entity --named Genre , org.jboss.forge.roaster.model.impl.JavaAnnotationImpl cannot be cast to org.jboss.forge.roaster.model.MemberHolder
[ISBN.java]$
{code}
At this point, I can't interact with the console and need to kill the process.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1800) Install Forge 2.5.0.Final in JBoss Developer Studio - no run
by William Diaz Pabón (JIRA)
[ https://issues.jboss.org/browse/FORGE-1800?page=com.atlassian.jira.plugin... ]
William Diaz Pabón edited comment on FORGE-1800 at 5/9/14 7:28 AM:
-------------------------------------------------------------------
Forge Tools upgraded with url which gave me and installed some libraries but not change version of forge, I try to re-upgrade, but I get indicating the image I attached.
Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_05.png
was (Author: william.diaz):
Forge Tools upgraded with url which gave me and installed some libraries but not change version of forge, I try to re-upgrade, but I get indicating the image I attached.
> Install Forge 2.5.0.Final in JBoss Developer Studio - no run
> ------------------------------------------------------------
>
> Key: FORGE-1800
> URL: https://issues.jboss.org/browse/FORGE-1800
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.5.0.Final
> Environment: JBoss Developer Studio 7.1.1.GA
> Reporter: William Diaz Pabón
> Attachments: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_01.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_02.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_03.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_04.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_05.png
>
>
> IDE: JBoss Developer Studio 7.1.1.GA
> Forge: 2.5.0.Final
> S.O: Windows 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1800) Install Forge 2.5.0.Final in JBoss Developer Studio - no run
by William Diaz Pabón (JIRA)
[ https://issues.jboss.org/browse/FORGE-1800?page=com.atlassian.jira.plugin... ]
William Diaz Pabón updated FORGE-1800:
--------------------------------------
Attachment: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_05.png
Forge Tools upgraded with url which gave me and installed some libraries but not change version of forge, I try to re-upgrade, but I get indicating the image I attached.
> Install Forge 2.5.0.Final in JBoss Developer Studio - no run
> ------------------------------------------------------------
>
> Key: FORGE-1800
> URL: https://issues.jboss.org/browse/FORGE-1800
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.5.0.Final
> Environment: JBoss Developer Studio 7.1.1.GA
> Reporter: William Diaz Pabón
> Attachments: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_01.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_02.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_03.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_04.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_05.png
>
>
> IDE: JBoss Developer Studio 7.1.1.GA
> Forge: 2.5.0.Final
> S.O: Windows 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1801) Being able to add a custom annotation to a property
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1801:
----------------------------------------
Summary: Being able to add a custom annotation to a property
Key: FORGE-1801
URL: https://issues.jboss.org/browse/FORGE-1801
Project: Forge
Issue Type: Sub-task
Components: Java EE
Affects Versions: 2.5.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
With [FORGE-1616] I can now create my own constraint. For example, this is the way I create an ISBN constraint :
{code}
constraint-new-annotation --named ISBN
{code}
The constraint is created, by default, under the {{constraint}} package. Now the problem, is that I can't apply it to a property because the constraint is not known. If I add a constraint, and press TAB for completion, ISBN does not appear :
{code}
[Book.java]$ constraint-add --onProperty isbn --constraint TAB
Valid Null NotNull AssertTrue AssertFalse Min Max DecimalMin DecimalMax Size Digits Past Future Pattern
{code}
Even if I try to add the location of the constraint, it does not work :
{code}
[Book.java]$ constraint-add --onProperty isbn --constraint ../constraints/ISBN
[0] - Valid
[1] - Null
[2] - NotNull
[3] - AssertTrue
[4] - AssertFalse
[5] - Min
[6] - Max
[7] - DecimalMin
[8] - DecimalMax
[9] - Size
[10] - Digits
[11] - Past
[12] - Future
[13] - Pattern
***ERROR*** Constraint must be specified.
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1743) Rename addon-git-install command to addon-install-from-git
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1743?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1743.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.5.1.Final
(was: 2.x Future)
Resolution: Done
> Rename addon-git-install command to addon-install-from-git
> ----------------------------------------------------------
>
> Key: FORGE-1743
> URL: https://issues.jboss.org/browse/FORGE-1743
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.4.1.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.5.1.Final
>
>
> To follow the naming convention <topic>-<verb>, the command should be renamed :
> {code}
> addon-install-from-git
> {code}
> Makes it sound like the existing command :
> {code}
> rest-generate-endpoints-from-entities
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1800) Install Forge 2.5.0.Final in JBoss Developer Studio - no run
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1800?page=com.atlassian.jira.plugin... ]
George Gastaldi reopened FORGE-1800:
------------------------------------
> Install Forge 2.5.0.Final in JBoss Developer Studio - no run
> ------------------------------------------------------------
>
> Key: FORGE-1800
> URL: https://issues.jboss.org/browse/FORGE-1800
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.5.0.Final
> Environment: JBoss Developer Studio 7.1.1.GA
> Reporter: William Diaz Pabón
> Attachments: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_01.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_02.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_03.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_04.png
>
>
> IDE: JBoss Developer Studio 7.1.1.GA
> Forge: 2.5.0.Final
> S.O: Windows 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1800) Install Forge 2.5.0.Final in JBoss Developer Studio - no run
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1800?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1800:
----------------------------------------
Let me know if it works
> Install Forge 2.5.0.Final in JBoss Developer Studio - no run
> ------------------------------------------------------------
>
> Key: FORGE-1800
> URL: https://issues.jboss.org/browse/FORGE-1800
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.5.0.Final
> Environment: JBoss Developer Studio 7.1.1.GA
> Reporter: William Diaz Pabón
> Attachments: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_01.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_02.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_03.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_04.png
>
>
> IDE: JBoss Developer Studio 7.1.1.GA
> Forge: 2.5.0.Final
> S.O: Windows 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months