[JBoss JIRA] (FORGE-1799) Forge 1.4.3 in JBoss Developer Studio - forge install-plugin arquillian - Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1799?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1799.
----------------------------------
Resolution: Rejected
You are using a JRE, please install a JDK.
Also please use the forums for help.
Best Regards
> Forge 1.4.3 in JBoss Developer Studio - forge install-plugin arquillian - Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-1799
> URL: https://issues.jboss.org/browse/FORGE-1799
> Project: Forge
> Issue Type: Bug
> Environment: JBoss Developer Studio 7.1.1
> Reporter: William Diaz Pabón
>
> IDE: JBoss Developer Studio 7.1.1.
> Forge: 1.4.3.Final
> S.O: Window 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
> Command: forge install-plugin arquillian
> Out:
> [arquillian-tutorial] arquillian-tutorial $ forge install-plugin arquillian
> ***INFO*** Preparing to install plugin: arquillian
> ***INFO*** Checking out plugin source files to [C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389] via 'git'
> ***INFO*** Switching to branch/tag [refs/heads/1.4.0.Final]
> ***INFO*** Invoking build with underlying build system.
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building arquillian-plugin 1.0.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ arquillian-plugin ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ arquillian-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 6 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ arquillian-plugin ---
> [INFO] Compiling 25 source files to C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389\target\classes
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.402s
> [INFO] Finished at: Fri May 09 00:18:33 COT 2014
> [INFO] Final Memory: 32M/86M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project arquillian-plugin: Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> ***INFO*** Cleaning up temp workspace [C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389]
> org.jboss.forge.project.build.BuildException: Build failed.Deleted C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389
> ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> [arquillian-tutorial] arquillian-tutorial $
> at org.jboss.forge.maven.facets.MavenProjectBuilder.build(MavenProjectBuilder.java:87)
> at org.jboss.forge.shell.plugins.PluginManager.installFromProject(PluginManager.java:179)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:387)
> at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:206)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186)
> at java.lang.Thread.run(Unknown Source)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (FORGE-1799) Forge 1.4.3 in JBoss Developer Studio - forge install-plugin arquillian - Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]
by William Diaz Pabón (JIRA)
William Diaz Pabón created FORGE-1799:
-----------------------------------------
Summary: Forge 1.4.3 in JBoss Developer Studio - forge install-plugin arquillian - Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]
Key: FORGE-1799
URL: https://issues.jboss.org/browse/FORGE-1799
Project: Forge
Issue Type: Bug
Environment: JBoss Developer Studio 7.1.1
Reporter: William Diaz Pabón
IDE: JBoss Developer Studio 7.1.1.
Forge: 1.4.3.Final
S.O: Window 7
JDK: C:\Java\32-bit\jdk1.7.0_55
Command: forge install-plugin arquillian
Out:
[arquillian-tutorial] arquillian-tutorial $ forge install-plugin arquillian
***INFO*** Preparing to install plugin: arquillian
***INFO*** Checking out plugin source files to [C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389] via 'git'
***INFO*** Switching to branch/tag [refs/heads/1.4.0.Final]
***INFO*** Invoking build with underlying build system.
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building arquillian-plugin 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ arquillian-plugin ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ arquillian-plugin ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ arquillian-plugin ---
[INFO] Compiling 25 source files to C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389\target\classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.402s
[INFO] Finished at: Fri May 09 00:18:33 COT 2014
[INFO] Final Memory: 32M/86M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project arquillian-plugin: Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
***INFO*** Cleaning up temp workspace [C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389]
org.jboss.forge.project.build.BuildException: Build failed.Deleted C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389
***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
[arquillian-tutorial] arquillian-tutorial $
at org.jboss.forge.maven.facets.MavenProjectBuilder.build(MavenProjectBuilder.java:87)
at org.jboss.forge.shell.plugins.PluginManager.installFromProject(PluginManager.java:179)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:387)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)
at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796)
at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819)
at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186)
at java.lang.Thread.run(Unknown Source)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (FORGE-1780) "Addon: New UI Command" should default commandName based on type name camelcase
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1780?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1780:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.5.1.Final
(was: 2.x Future)
Resolution: Done
Thanks [~danielcunha]
> "Addon: New UI Command" should default commandName based on type name camelcase
> -------------------------------------------------------------------------------
>
> Key: FORGE-1780
> URL: https://issues.jboss.org/browse/FORGE-1780
> Project: Forge
> Issue Type: Enhancement
> Components: Addon Development, Builtin Plugins
> Affects Versions: 2.5.0.Final
> Reporter: Lincoln Baxter III
> Assignee: Daniel Cunha
> Labels: starter
> Fix For: 2.5.1.Final
>
>
> addon-new-ui-command --named TechNewPropertyCommand --commandName xxxxxxx
> This should be the default commandName value for this scenario:
> addon-new-ui-command --named TechNewPropertyCommand --commandName tech-new-property
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (FORGE-1595) Being able to create an empty JSF backing bean
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1595?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1595:
-------------------------------------------
Awesome job Antonio! You are the man!
> Being able to create an empty JSF backing bean
> ----------------------------------------------
>
> Key: FORGE-1595
> URL: https://issues.jboss.org/browse/FORGE-1595
> Project: Forge
> Issue Type: Sub-task
> Components: Scaffold
> Affects Versions: 2.0.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Priority: Minor
> Fix For: 2.5.1.Final
>
>
> At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such :
> {code}
> faces-new-bean --named MyBean
> {code}
> This will create a {{MyBean}}, with no scope, under the {{view}} package. You could also give a different sub-package with :
> {code}
> faces-new-page --named MyBean --targetPackage view.admin
> {code}
> This will create the page under {{view/admin/MyBean.java}}.
> {code}
> @Named
> public class MyBean {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (FORGE-1595) Being able to create an empty JSF backing bean
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1595?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1595:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.5.1.Final
(was: 2.x Future)
Resolution: Done
> Being able to create an empty JSF backing bean
> ----------------------------------------------
>
> Key: FORGE-1595
> URL: https://issues.jboss.org/browse/FORGE-1595
> Project: Forge
> Issue Type: Sub-task
> Components: Scaffold
> Affects Versions: 2.0.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Priority: Minor
> Fix For: 2.5.1.Final
>
>
> At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such :
> {code}
> faces-new-bean --named MyBean
> {code}
> This will create a {{MyBean}}, with no scope, under the {{view}} package. You could also give a different sub-package with :
> {code}
> faces-new-page --named MyBean --targetPackage view.admin
> {code}
> This will create the page under {{view/admin/MyBean.java}}.
> {code}
> @Named
> public class MyBean {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (FORGE-1594) Being able to create an empty JSF page
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1594?page=com.atlassian.jira.plugin... ]
Vineet Reynolds reassigned FORGE-1594:
--------------------------------------
Assignee: Vineet Reynolds
> Being able to create an empty JSF page
> --------------------------------------
>
> Key: FORGE-1594
> URL: https://issues.jboss.org/browse/FORGE-1594
> Project: Forge
> Issue Type: Sub-task
> Components: Scaffold
> Affects Versions: 2.0.0.Final
> Reporter: Antonio Goncalves
> Assignee: Vineet Reynolds
> Priority: Minor
> Fix For: 2.x Future
>
>
> At the moment the only way to generate JSF pages is with scaffolding. When you create an application, you realize that these scaffolded pages are not enough and that you need to create new ones. To save time and help the developer in creating new pages, it would be good to have a command such :
> {code}
> faces-new-view --named mypage
> {code}
> This will create a mypage.xhtml on the root of the webapp directory. You could also give a different directory with :
> {code}
> faces-new-view --named mypage --targetDirectory admin
> {code}
> This will create the page under webapp/admin/mypage.xhtml.
> {code}
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://xmlns.jcp.org/jsf/html"
> xmlns:f="http://xmlns.jcp.org/jsf/core"
> xmlns:ui="http://xmlns.jcp.org/jsf/facelets"
> template="/resources/scaffold/pageTemplate.xhtml">
> <ui:param name="pageTitle" value="mypage"/>
> <ui:define name="header">
> mypage
> </ui:define>
> <ui:define name="subheader">
> mypage
> </ui:define>
> <ui:define name="footer"/>
> <ui:define name="main">
> </ui:define>
> </ui:composition>
> {code}
> The name of the page {{mypage}} is used for the title, header, subheader. But we could customize this using optional attributes for title, header, subheader :
> {code}
> faces-new-view --named mypage --targetDirectory admin --title Administration Page --header Admin Header --subheader Admin Sub Header
> {code}
> It would just create a minimum JSF page such as :
> {code}
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://xmlns.jcp.org/jsf/html"
> xmlns:f="http://xmlns.jcp.org/jsf/core"
> xmlns:ui="http://xmlns.jcp.org/jsf/facelets"
> template="/resources/scaffold/pageTemplate.xhtml">
> <ui:param name="pageTitle" value="Administration Page"/>
> <ui:define name="header">
> Admin Header
> </ui:define>
> <ui:define name="subheader">
> Admin Sub Header
> </ui:define>
> <ui:define name="footer"/>
> <ui:define name="main">
> </ui:define>
> </ui:composition>
> {code}
> If there were several templates, we could do :
> {code}
> faces-new-view --named mypage --template MyTemplate.xhtml
> {code}
> PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[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 reopened FORGE-1787:
--------------------------------------
The template works fine, but {{search.xhtml}} has not been fixed
> 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, 1 month