May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1855) Simple Container should support singleton services

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] Matej Briskar reassigned FORGE-1855: ------------------------------------ Assignee: Matej Briskar > Simple Container should support singleton services > -------------------------------------------------- > > Key: FORGE-1855 > URL: https://issues.jboss.org/browse/FORGE-1855 > Project: Forge > Issue Type: Feature Request > Components: Furnace Simple > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. > I propose a {{public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1787: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done Pull request merged. Thank you Ivan! [~agoncal], can you confirm this is fixed? Please reopen the issue if not. Thanks > 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: Ivan St. Ivanov > Priority: Blocker > Fix For: 2.6.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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ] Ivan St. Ivanov updated FORGE-1787: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/forge/core/pull/462 > 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: Ivan St. Ivanov > Priority: Blocker > Fix For: 2.6.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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ] Work on FORGE-1787 started by Ivan St. Ivanov. > 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: Ivan St. Ivanov > Priority: Blocker > Fix For: 2.6.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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1856) Shell commands should fallback to native commands if a command is not found

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1856: -------------------------------------- Summary: Shell commands should fallback to native commands if a command is not found Key: FORGE-1856 URL: https://issues.jboss.org/browse/FORGE-1856 Project: Forge Issue Type: Enhancement Components: UI - Shell Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future {quote} gastaldi 12:23 maybe we could fallback to native lincolnthree 12:24 gastaldi: fallback to native would be nice. we need passthrough to the native command line if possible gastaldi 12:24 in our CommandNotFoundHandler, we could fallback to running a native command lincolnthree 12:24 stalep: any idea how to do that? :p gastaldi 12:25 lincolnthree: https://github.com/forge/core/blob/master/shell/impl/src/main/java/org/jb... 12:25 we should have a flag that allows that {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1855) Simple Container should support singleton services

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1855: -------------------------------------- Summary: Simple Container should support singleton services Key: FORGE-1855 URL: https://issues.jboss.org/browse/FORGE-1855 Project: Forge Issue Type: Feature Request Components: Furnace Simple Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. I propose a {{ public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1855) Simple Container should support singleton services

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1855: ----------------------------------- Description: In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. I propose a {{public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} was: In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. I propose a {{ public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} > Simple Container should support singleton services > -------------------------------------------------- > > Key: FORGE-1855 > URL: https://issues.jboss.org/browse/FORGE-1855 > Project: Forge > Issue Type: Feature Request > Components: Furnace Simple > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. > I propose a {{public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1854) Support tilde when specifying the package

by Matej Briskar (JIRA)

Matej Briskar created FORGE-1854: ------------------------------------ Summary: Support tilde when specifying the package Key: FORGE-1854 URL: https://issues.jboss.org/browse/FORGE-1854 Project: Forge Issue Type: Feature Request Reporter: Matej Briskar When specifying the package, the support for tilde (~) was present in forge 1 but is not in the forge 2. Examples, where it could be used: {code} java-new-class --targetPackage ~.mypackage java-new-field --type ~.entities.MyEntity {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1854) Support tilde when specifying the package

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1854?page=com.atlassian.jira.plugin... ] Matej Briskar updated FORGE-1854: --------------------------------- Description: When specifying the package, the support for tilde (~) was present in forge 1, but is not in the forge 2. Examples, where it could be used: {code} java-new-class --targetPackage ~.mypackage java-new-field --type ~.entities.MyEntity {code} was: When specifying the package, the support for tilde (~) was present in forge 1 but is not in the forge 2. Examples, where it could be used: {code} java-new-class --targetPackage ~.mypackage java-new-field --type ~.entities.MyEntity {code} > Support tilde when specifying the package > ----------------------------------------- > > Key: FORGE-1854 > URL: https://issues.jboss.org/browse/FORGE-1854 > Project: Forge > Issue Type: Feature Request > Reporter: Matej Briskar > > When specifying the package, the support for tilde (~) was present in forge 1, but is not in the forge 2. > Examples, where it could be used: > {code} > java-new-class --targetPackage ~.mypackage > java-new-field --type ~.entities.MyEntity > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-16) Be able to indent code

by Antonio Goncalves (JIRA)

Antonio Goncalves created ROASTER-16: ---------------------------------------- Summary: Be able to indent code Key: ROASTER-16 URL: https://issues.jboss.org/browse/ROASTER-16 Project: Roaster Issue Type: Feature Request Components: API Affects Versions: 2.4.0.Final Reporter: Antonio Goncalves I would be good to have a method that indents the code. Something like {{Refactry.indent}}. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014