You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by BERTIN Matthieu <M....@oberthur.com> on 2010/12/01 16:36:09 UTC
Unable to run the jsf-components maven archetype
Hello,
I've been trying to run the maven JSF Components archetype for JSF 1.2
on Tomcat 6.0, created this way:
mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
(choice nbr. 6)
Unfortunately, I have been unable to find why the EL expressions are not
evaluated.
For instance, I can read this on the home.jsp:
My JSF Components Library(Version #{buildInfo['mycomponents_version']},
using #{buildInfo ['jsf_implementation']})
Or even
#{sayHelloBean.oddNumber} as the default value in a field.
The logs in tomcat show no missing jar at deployment, only a
facesexceptions when it tries to bind a method to an actionlistener
attribute.
My guess is there is something missing in the following web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<description>debug web.xml</description>
<context-param>
<description>Comma separated list of URIs of (additional) faces
config files.
(e.g. /WEB-INF/my-config.xml)
See JSF 1.0 PRD2, 10.3.2
Attention: You do not need to put /WEB-INF/faces-config.xml
in here.
</description>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/examples-config.xml</param-value>
</context-param>
<context-param>
<description>State saving method: "client" or "server" (= default)
See JSF Specification 2.5.3</description>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
/listener-class>
</listener>
</web-app>
Sincerely,
Matthieu Bertin
Re: RE : RE : Unable to run the jsf-components maven archetype
Posted by Jakob Korherr <ja...@gmail.com>.
Hi Matthieu,
You're welcome!
For the other problems please open an issue in our issue-tracker at
[1]. Just click on "create new issue" and choose "MyFaces core" as
project and "Archetype" as component.
Furthermore you can provide patches (svn diff files) for the problems
you're having on the issue entry in the issue-tracker via "upload
file". Having a good patch for an issue means that it will be solved
soon. Without a patch it may take a while until somebody has time for
it..
The source code for the archetypes is at [2].
Regards,
Jakob
[1] https://issues.apache.org/jira/browse/MYFACES
[2] https://svn.apache.org/repos/asf/myfaces/myfaces-build-tools/trunk/maven2-archetypes/
2010/12/2 BERTIN Matthieu <M....@oberthur.com>:
> I figured out some other little details that trouble jsp & xml validation.
>
> The taglib vm template should put the 'description' node on top of its siblings node and display name node just behind it. The taglib version should be changed from 1.1.7 to 1.2 as well.
>
> How do we help changing the archetype?
> Sincerely,
>
> Matthieu Bertin
>
>
> -----Message d'origine-----
> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
> Envoyé : mercredi 1 décembre 2010 18:09
> À : MyFaces Discussion
> Objet : Re: RE : Unable to run the jsf-components maven archetype
>
> Related issue: https://issues.apache.org/jira/browse/MYFACES-2987
>
> 2010/12/1 Jakob Korherr <ja...@gmail.com>:
>> Hi,
>>
>> I just found out the problem:
>>
>> The web.xml specifies the web-app with version="2.4" which means there
>> is no unified EL available and thus the EL expressions don't work.
>>
>> Just change version="2.4" to version="2.5" on web.xml and everything
>> works as expected!
>>
>> Thanks for reporting this - I'll commit it on the archetype itself too!
>>
>> Regards,
>> Jakob
>>
>> 2010/12/1 Jakob Korherr <ja...@gmail.com>:
>>> Hi,
>>>
>>> Yes, the listener is automatically added via a tld file, so no need to
>>> configure it.
>>>
>>> I just created the archetype myself and tried it using maven and jetty
>>> (first mvn clean install on the outer project and then mvn clean
>>> jetty:run on the examples project) and everything works great! However
>>> when using tomcat 6.0.29 I get the same error you're getting - thus I
>>> think it is an EL impl problem.
>>>
>>> I will investigate further on this one and ping you when I found out
>>> what causes this problem!
>>>
>>> Regards,
>>> Jakob
>>>
>>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>>> That's what I looked for, but I went through
>>>> http://localhost:8080/artifact-examples/home.jsf
>>>>
>>>> so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
>>>>
>>>> <listener>
>>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener
>>>> </listener-class>
>>>> </listener>
>>>>
>>>> to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
>>>>
>>>> Sincerely,
>>>>
>>>> Matthieu Bertin
>>>> -Office 168
>>>> -Phone 5407
>>>>
>>>>
>>>> -----Message d'origine-----
>>>> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
>>>> Envoyé : mercredi 1 décembre 2010 16:55
>>>> À : MyFaces Discussion
>>>> Objet : Re: Unable to run the jsf-components maven archetype
>>>>
>>>> Hi Matthieu,
>>>>
>>>> What URL do you use for accessing the website in the browser? For
>>>> example do you use index.jsf or index.jsp?
>>>>
>>>> Only *.jsf works correctly here and I guess that when you use *.jsp
>>>> you will get the error you're seeing.
>>>>
>>>> Regards,
>>>> Jakob
>>>>
>>>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>>>> Hello,
>>>>>
>>>>> I've been trying to run the maven JSF Components archetype for JSF 1.2
>>>>> on Tomcat 6.0, created this way:
>>>>>
>>>>> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>>>>>
>>>>> (choice nbr. 6)
>>>>>
>>>>> Unfortunately, I have been unable to find why the EL expressions are not
>>>>> evaluated.
>>>>> For instance, I can read this on the home.jsp:
>>>>>
>>>>>
>>>>> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
>>>>> using #{buildInfo ['jsf_implementation']})
>>>>>
>>>>> Or even
>>>>>
>>>>> #{sayHelloBean.oddNumber} as the default value in a field.
>>>>>
>>>>> The logs in tomcat show no missing jar at deployment, only a
>>>>> facesexceptions when it tries to bind a method to an actionlistener
>>>>> attribute.
>>>>>
>>>>> My guess is there is something missing in the following web.xml:
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>>>> version="2.4">
>>>>>
>>>>> <description>debug web.xml</description>
>>>>>
>>>>> <context-param>
>>>>> <description>Comma separated list of URIs of (additional) faces
>>>>> config files.
>>>>> (e.g. /WEB-INF/my-config.xml)
>>>>> See JSF 1.0 PRD2, 10.3.2
>>>>> Attention: You do not need to put /WEB-INF/faces-config.xml
>>>>> in here.
>>>>> </description>
>>>>> <param-name>javax.faces.CONFIG_FILES</param-name>
>>>>> <param-value>/WEB-INF/examples-config.xml</param-value>
>>>>> </context-param>
>>>>>
>>>>> <context-param>
>>>>> <description>State saving method: "client" or "server" (= default)
>>>>> See JSF Specification 2.5.3</description>
>>>>> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>>>>> <param-value>server</param-value>
>>>>> </context-param>
>>>>>
>>>>> <servlet>
>>>>> <servlet-name>Faces Servlet</servlet-name>
>>>>> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
>>>>> <load-on-startup>1</load-on-startup>
>>>>> </servlet>
>>>>>
>>>>> <servlet-mapping>
>>>>> <servlet-name>Faces Servlet</servlet-name>
>>>>> <url-pattern>*.jsf</url-pattern>
>>>>> </servlet-mapping>
>>>>>
>>>>> <welcome-file-list>
>>>>> <welcome-file>index.jsp</welcome-file>
>>>>> </welcome-file-list>
>>>>>
>>>>> <listener>
>>>>>
>>>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
>>>>> /listener-class>
>>>>> </listener>
>>>>>
>>>>>
>>>>> </web-app>
>>>>>
>>>>> Sincerely,
>>>>>
>>>>> Matthieu Bertin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jakob Korherr
>>>>
>>>> blog: http://www.jakobk.com
>>>> twitter: http://twitter.com/jakobkorherr
>>>> work: http://www.irian.at
>>>>
>>>
>>>
>>>
>>> --
>>> Jakob Korherr
>>>
>>> blog: http://www.jakobk.com
>>> twitter: http://twitter.com/jakobkorherr
>>> work: http://www.irian.at
>>>
>>
>>
>>
>> --
>> Jakob Korherr
>>
>> blog: http://www.jakobk.com
>> twitter: http://twitter.com/jakobkorherr
>> work: http://www.irian.at
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
RE : RE : Unable to run the jsf-components maven archetype
Posted by BERTIN Matthieu <M....@oberthur.com>.
And that does work! Thanks a lot, this helped a lot. I hope I'll be able to give this back some time !
Sincerely,
Matthieu Bertin
-Office 168
-Phone 5407
-----Message d'origine-----
De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
Envoyé : mercredi 1 décembre 2010 18:09
À : MyFaces Discussion
Objet : Re: RE : Unable to run the jsf-components maven archetype
Related issue: https://issues.apache.org/jira/browse/MYFACES-2987
2010/12/1 Jakob Korherr <ja...@gmail.com>:
> Hi,
>
> I just found out the problem:
>
> The web.xml specifies the web-app with version="2.4" which means there
> is no unified EL available and thus the EL expressions don't work.
>
> Just change version="2.4" to version="2.5" on web.xml and everything
> works as expected!
>
> Thanks for reporting this - I'll commit it on the archetype itself too!
>
> Regards,
> Jakob
>
> 2010/12/1 Jakob Korherr <ja...@gmail.com>:
>> Hi,
>>
>> Yes, the listener is automatically added via a tld file, so no need to
>> configure it.
>>
>> I just created the archetype myself and tried it using maven and jetty
>> (first mvn clean install on the outer project and then mvn clean
>> jetty:run on the examples project) and everything works great! However
>> when using tomcat 6.0.29 I get the same error you're getting - thus I
>> think it is an EL impl problem.
>>
>> I will investigate further on this one and ping you when I found out
>> what causes this problem!
>>
>> Regards,
>> Jakob
>>
>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>> That's what I looked for, but I went through
>>> http://localhost:8080/artifact-examples/home.jsf
>>>
>>> so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
>>>
>>> <listener>
>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener
>>> </listener-class>
>>> </listener>
>>>
>>> to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
>>>
>>> Sincerely,
>>>
>>> Matthieu Bertin
>>> -Office 168
>>> -Phone 5407
>>>
>>>
>>> -----Message d'origine-----
>>> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
>>> Envoyé : mercredi 1 décembre 2010 16:55
>>> À : MyFaces Discussion
>>> Objet : Re: Unable to run the jsf-components maven archetype
>>>
>>> Hi Matthieu,
>>>
>>> What URL do you use for accessing the website in the browser? For
>>> example do you use index.jsf or index.jsp?
>>>
>>> Only *.jsf works correctly here and I guess that when you use *.jsp
>>> you will get the error you're seeing.
>>>
>>> Regards,
>>> Jakob
>>>
>>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>>> Hello,
>>>>
>>>> I've been trying to run the maven JSF Components archetype for JSF 1.2
>>>> on Tomcat 6.0, created this way:
>>>>
>>>> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>>>>
>>>> (choice nbr. 6)
>>>>
>>>> Unfortunately, I have been unable to find why the EL expressions are not
>>>> evaluated.
>>>> For instance, I can read this on the home.jsp:
>>>>
>>>>
>>>> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
>>>> using #{buildInfo ['jsf_implementation']})
>>>>
>>>> Or even
>>>>
>>>> #{sayHelloBean.oddNumber} as the default value in a field.
>>>>
>>>> The logs in tomcat show no missing jar at deployment, only a
>>>> facesexceptions when it tries to bind a method to an actionlistener
>>>> attribute.
>>>>
>>>> My guess is there is something missing in the following web.xml:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>>> version="2.4">
>>>>
>>>> <description>debug web.xml</description>
>>>>
>>>> <context-param>
>>>> <description>Comma separated list of URIs of (additional) faces
>>>> config files.
>>>> (e.g. /WEB-INF/my-config.xml)
>>>> See JSF 1.0 PRD2, 10.3.2
>>>> Attention: You do not need to put /WEB-INF/faces-config.xml
>>>> in here.
>>>> </description>
>>>> <param-name>javax.faces.CONFIG_FILES</param-name>
>>>> <param-value>/WEB-INF/examples-config.xml</param-value>
>>>> </context-param>
>>>>
>>>> <context-param>
>>>> <description>State saving method: "client" or "server" (= default)
>>>> See JSF Specification 2.5.3</description>
>>>> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>>>> <param-value>server</param-value>
>>>> </context-param>
>>>>
>>>> <servlet>
>>>> <servlet-name>Faces Servlet</servlet-name>
>>>> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
>>>> <load-on-startup>1</load-on-startup>
>>>> </servlet>
>>>>
>>>> <servlet-mapping>
>>>> <servlet-name>Faces Servlet</servlet-name>
>>>> <url-pattern>*.jsf</url-pattern>
>>>> </servlet-mapping>
>>>>
>>>> <welcome-file-list>
>>>> <welcome-file>index.jsp</welcome-file>
>>>> </welcome-file-list>
>>>>
>>>> <listener>
>>>>
>>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
>>>> /listener-class>
>>>> </listener>
>>>>
>>>>
>>>> </web-app>
>>>>
>>>> Sincerely,
>>>>
>>>> Matthieu Bertin
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Jakob Korherr
>>>
>>> blog: http://www.jakobk.com
>>> twitter: http://twitter.com/jakobkorherr
>>> work: http://www.irian.at
>>>
>>
>>
>>
>> --
>> Jakob Korherr
>>
>> blog: http://www.jakobk.com
>> twitter: http://twitter.com/jakobkorherr
>> work: http://www.irian.at
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
RE : RE : Unable to run the jsf-components maven archetype
Posted by BERTIN Matthieu <M....@oberthur.com>.
I figured out some other little details that trouble jsp & xml validation.
The taglib vm template should put the 'description' node on top of its siblings node and display name node just behind it. The taglib version should be changed from 1.1.7 to 1.2 as well.
How do we help changing the archetype?
Sincerely,
Matthieu Bertin
-----Message d'origine-----
De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
Envoyé : mercredi 1 décembre 2010 18:09
À : MyFaces Discussion
Objet : Re: RE : Unable to run the jsf-components maven archetype
Related issue: https://issues.apache.org/jira/browse/MYFACES-2987
2010/12/1 Jakob Korherr <ja...@gmail.com>:
> Hi,
>
> I just found out the problem:
>
> The web.xml specifies the web-app with version="2.4" which means there
> is no unified EL available and thus the EL expressions don't work.
>
> Just change version="2.4" to version="2.5" on web.xml and everything
> works as expected!
>
> Thanks for reporting this - I'll commit it on the archetype itself too!
>
> Regards,
> Jakob
>
> 2010/12/1 Jakob Korherr <ja...@gmail.com>:
>> Hi,
>>
>> Yes, the listener is automatically added via a tld file, so no need to
>> configure it.
>>
>> I just created the archetype myself and tried it using maven and jetty
>> (first mvn clean install on the outer project and then mvn clean
>> jetty:run on the examples project) and everything works great! However
>> when using tomcat 6.0.29 I get the same error you're getting - thus I
>> think it is an EL impl problem.
>>
>> I will investigate further on this one and ping you when I found out
>> what causes this problem!
>>
>> Regards,
>> Jakob
>>
>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>> That's what I looked for, but I went through
>>> http://localhost:8080/artifact-examples/home.jsf
>>>
>>> so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
>>>
>>> <listener>
>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener
>>> </listener-class>
>>> </listener>
>>>
>>> to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
>>>
>>> Sincerely,
>>>
>>> Matthieu Bertin
>>> -Office 168
>>> -Phone 5407
>>>
>>>
>>> -----Message d'origine-----
>>> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
>>> Envoyé : mercredi 1 décembre 2010 16:55
>>> À : MyFaces Discussion
>>> Objet : Re: Unable to run the jsf-components maven archetype
>>>
>>> Hi Matthieu,
>>>
>>> What URL do you use for accessing the website in the browser? For
>>> example do you use index.jsf or index.jsp?
>>>
>>> Only *.jsf works correctly here and I guess that when you use *.jsp
>>> you will get the error you're seeing.
>>>
>>> Regards,
>>> Jakob
>>>
>>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>>> Hello,
>>>>
>>>> I've been trying to run the maven JSF Components archetype for JSF 1.2
>>>> on Tomcat 6.0, created this way:
>>>>
>>>> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>>>>
>>>> (choice nbr. 6)
>>>>
>>>> Unfortunately, I have been unable to find why the EL expressions are not
>>>> evaluated.
>>>> For instance, I can read this on the home.jsp:
>>>>
>>>>
>>>> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
>>>> using #{buildInfo ['jsf_implementation']})
>>>>
>>>> Or even
>>>>
>>>> #{sayHelloBean.oddNumber} as the default value in a field.
>>>>
>>>> The logs in tomcat show no missing jar at deployment, only a
>>>> facesexceptions when it tries to bind a method to an actionlistener
>>>> attribute.
>>>>
>>>> My guess is there is something missing in the following web.xml:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>>> version="2.4">
>>>>
>>>> <description>debug web.xml</description>
>>>>
>>>> <context-param>
>>>> <description>Comma separated list of URIs of (additional) faces
>>>> config files.
>>>> (e.g. /WEB-INF/my-config.xml)
>>>> See JSF 1.0 PRD2, 10.3.2
>>>> Attention: You do not need to put /WEB-INF/faces-config.xml
>>>> in here.
>>>> </description>
>>>> <param-name>javax.faces.CONFIG_FILES</param-name>
>>>> <param-value>/WEB-INF/examples-config.xml</param-value>
>>>> </context-param>
>>>>
>>>> <context-param>
>>>> <description>State saving method: "client" or "server" (= default)
>>>> See JSF Specification 2.5.3</description>
>>>> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>>>> <param-value>server</param-value>
>>>> </context-param>
>>>>
>>>> <servlet>
>>>> <servlet-name>Faces Servlet</servlet-name>
>>>> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
>>>> <load-on-startup>1</load-on-startup>
>>>> </servlet>
>>>>
>>>> <servlet-mapping>
>>>> <servlet-name>Faces Servlet</servlet-name>
>>>> <url-pattern>*.jsf</url-pattern>
>>>> </servlet-mapping>
>>>>
>>>> <welcome-file-list>
>>>> <welcome-file>index.jsp</welcome-file>
>>>> </welcome-file-list>
>>>>
>>>> <listener>
>>>>
>>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
>>>> /listener-class>
>>>> </listener>
>>>>
>>>>
>>>> </web-app>
>>>>
>>>> Sincerely,
>>>>
>>>> Matthieu Bertin
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Jakob Korherr
>>>
>>> blog: http://www.jakobk.com
>>> twitter: http://twitter.com/jakobkorherr
>>> work: http://www.irian.at
>>>
>>
>>
>>
>> --
>> Jakob Korherr
>>
>> blog: http://www.jakobk.com
>> twitter: http://twitter.com/jakobkorherr
>> work: http://www.irian.at
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
Re: RE : Unable to run the jsf-components maven archetype
Posted by Jakob Korherr <ja...@gmail.com>.
Related issue: https://issues.apache.org/jira/browse/MYFACES-2987
2010/12/1 Jakob Korherr <ja...@gmail.com>:
> Hi,
>
> I just found out the problem:
>
> The web.xml specifies the web-app with version="2.4" which means there
> is no unified EL available and thus the EL expressions don't work.
>
> Just change version="2.4" to version="2.5" on web.xml and everything
> works as expected!
>
> Thanks for reporting this - I'll commit it on the archetype itself too!
>
> Regards,
> Jakob
>
> 2010/12/1 Jakob Korherr <ja...@gmail.com>:
>> Hi,
>>
>> Yes, the listener is automatically added via a tld file, so no need to
>> configure it.
>>
>> I just created the archetype myself and tried it using maven and jetty
>> (first mvn clean install on the outer project and then mvn clean
>> jetty:run on the examples project) and everything works great! However
>> when using tomcat 6.0.29 I get the same error you're getting - thus I
>> think it is an EL impl problem.
>>
>> I will investigate further on this one and ping you when I found out
>> what causes this problem!
>>
>> Regards,
>> Jakob
>>
>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>> That's what I looked for, but I went through
>>> http://localhost:8080/artifact-examples/home.jsf
>>>
>>> so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
>>>
>>> <listener>
>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener
>>> </listener-class>
>>> </listener>
>>>
>>> to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
>>>
>>> Sincerely,
>>>
>>> Matthieu Bertin
>>> -Office 168
>>> -Phone 5407
>>>
>>>
>>> -----Message d'origine-----
>>> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
>>> Envoyé : mercredi 1 décembre 2010 16:55
>>> À : MyFaces Discussion
>>> Objet : Re: Unable to run the jsf-components maven archetype
>>>
>>> Hi Matthieu,
>>>
>>> What URL do you use for accessing the website in the browser? For
>>> example do you use index.jsf or index.jsp?
>>>
>>> Only *.jsf works correctly here and I guess that when you use *.jsp
>>> you will get the error you're seeing.
>>>
>>> Regards,
>>> Jakob
>>>
>>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>>> Hello,
>>>>
>>>> I've been trying to run the maven JSF Components archetype for JSF 1.2
>>>> on Tomcat 6.0, created this way:
>>>>
>>>> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>>>>
>>>> (choice nbr. 6)
>>>>
>>>> Unfortunately, I have been unable to find why the EL expressions are not
>>>> evaluated.
>>>> For instance, I can read this on the home.jsp:
>>>>
>>>>
>>>> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
>>>> using #{buildInfo ['jsf_implementation']})
>>>>
>>>> Or even
>>>>
>>>> #{sayHelloBean.oddNumber} as the default value in a field.
>>>>
>>>> The logs in tomcat show no missing jar at deployment, only a
>>>> facesexceptions when it tries to bind a method to an actionlistener
>>>> attribute.
>>>>
>>>> My guess is there is something missing in the following web.xml:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>>> version="2.4">
>>>>
>>>> <description>debug web.xml</description>
>>>>
>>>> <context-param>
>>>> <description>Comma separated list of URIs of (additional) faces
>>>> config files.
>>>> (e.g. /WEB-INF/my-config.xml)
>>>> See JSF 1.0 PRD2, 10.3.2
>>>> Attention: You do not need to put /WEB-INF/faces-config.xml
>>>> in here.
>>>> </description>
>>>> <param-name>javax.faces.CONFIG_FILES</param-name>
>>>> <param-value>/WEB-INF/examples-config.xml</param-value>
>>>> </context-param>
>>>>
>>>> <context-param>
>>>> <description>State saving method: "client" or "server" (= default)
>>>> See JSF Specification 2.5.3</description>
>>>> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>>>> <param-value>server</param-value>
>>>> </context-param>
>>>>
>>>> <servlet>
>>>> <servlet-name>Faces Servlet</servlet-name>
>>>> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
>>>> <load-on-startup>1</load-on-startup>
>>>> </servlet>
>>>>
>>>> <servlet-mapping>
>>>> <servlet-name>Faces Servlet</servlet-name>
>>>> <url-pattern>*.jsf</url-pattern>
>>>> </servlet-mapping>
>>>>
>>>> <welcome-file-list>
>>>> <welcome-file>index.jsp</welcome-file>
>>>> </welcome-file-list>
>>>>
>>>> <listener>
>>>>
>>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
>>>> /listener-class>
>>>> </listener>
>>>>
>>>>
>>>> </web-app>
>>>>
>>>> Sincerely,
>>>>
>>>> Matthieu Bertin
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Jakob Korherr
>>>
>>> blog: http://www.jakobk.com
>>> twitter: http://twitter.com/jakobkorherr
>>> work: http://www.irian.at
>>>
>>
>>
>>
>> --
>> Jakob Korherr
>>
>> blog: http://www.jakobk.com
>> twitter: http://twitter.com/jakobkorherr
>> work: http://www.irian.at
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
Re: RE : Unable to run the jsf-components maven archetype
Posted by Jakob Korherr <ja...@gmail.com>.
Hi,
I just found out the problem:
The web.xml specifies the web-app with version="2.4" which means there
is no unified EL available and thus the EL expressions don't work.
Just change version="2.4" to version="2.5" on web.xml and everything
works as expected!
Thanks for reporting this - I'll commit it on the archetype itself too!
Regards,
Jakob
2010/12/1 Jakob Korherr <ja...@gmail.com>:
> Hi,
>
> Yes, the listener is automatically added via a tld file, so no need to
> configure it.
>
> I just created the archetype myself and tried it using maven and jetty
> (first mvn clean install on the outer project and then mvn clean
> jetty:run on the examples project) and everything works great! However
> when using tomcat 6.0.29 I get the same error you're getting - thus I
> think it is an EL impl problem.
>
> I will investigate further on this one and ping you when I found out
> what causes this problem!
>
> Regards,
> Jakob
>
> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>> That's what I looked for, but I went through
>> http://localhost:8080/artifact-examples/home.jsf
>>
>> so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
>>
>> <listener>
>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener
>> </listener-class>
>> </listener>
>>
>> to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
>>
>> Sincerely,
>>
>> Matthieu Bertin
>> -Office 168
>> -Phone 5407
>>
>>
>> -----Message d'origine-----
>> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
>> Envoyé : mercredi 1 décembre 2010 16:55
>> À : MyFaces Discussion
>> Objet : Re: Unable to run the jsf-components maven archetype
>>
>> Hi Matthieu,
>>
>> What URL do you use for accessing the website in the browser? For
>> example do you use index.jsf or index.jsp?
>>
>> Only *.jsf works correctly here and I guess that when you use *.jsp
>> you will get the error you're seeing.
>>
>> Regards,
>> Jakob
>>
>> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>>> Hello,
>>>
>>> I've been trying to run the maven JSF Components archetype for JSF 1.2
>>> on Tomcat 6.0, created this way:
>>>
>>> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>>>
>>> (choice nbr. 6)
>>>
>>> Unfortunately, I have been unable to find why the EL expressions are not
>>> evaluated.
>>> For instance, I can read this on the home.jsp:
>>>
>>>
>>> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
>>> using #{buildInfo ['jsf_implementation']})
>>>
>>> Or even
>>>
>>> #{sayHelloBean.oddNumber} as the default value in a field.
>>>
>>> The logs in tomcat show no missing jar at deployment, only a
>>> facesexceptions when it tries to bind a method to an actionlistener
>>> attribute.
>>>
>>> My guess is there is something missing in the following web.xml:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>> version="2.4">
>>>
>>> <description>debug web.xml</description>
>>>
>>> <context-param>
>>> <description>Comma separated list of URIs of (additional) faces
>>> config files.
>>> (e.g. /WEB-INF/my-config.xml)
>>> See JSF 1.0 PRD2, 10.3.2
>>> Attention: You do not need to put /WEB-INF/faces-config.xml
>>> in here.
>>> </description>
>>> <param-name>javax.faces.CONFIG_FILES</param-name>
>>> <param-value>/WEB-INF/examples-config.xml</param-value>
>>> </context-param>
>>>
>>> <context-param>
>>> <description>State saving method: "client" or "server" (= default)
>>> See JSF Specification 2.5.3</description>
>>> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>>> <param-value>server</param-value>
>>> </context-param>
>>>
>>> <servlet>
>>> <servlet-name>Faces Servlet</servlet-name>
>>> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
>>> <load-on-startup>1</load-on-startup>
>>> </servlet>
>>>
>>> <servlet-mapping>
>>> <servlet-name>Faces Servlet</servlet-name>
>>> <url-pattern>*.jsf</url-pattern>
>>> </servlet-mapping>
>>>
>>> <welcome-file-list>
>>> <welcome-file>index.jsp</welcome-file>
>>> </welcome-file-list>
>>>
>>> <listener>
>>>
>>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
>>> /listener-class>
>>> </listener>
>>>
>>>
>>> </web-app>
>>>
>>> Sincerely,
>>>
>>> Matthieu Bertin
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Jakob Korherr
>>
>> blog: http://www.jakobk.com
>> twitter: http://twitter.com/jakobkorherr
>> work: http://www.irian.at
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
Re: RE : Unable to run the jsf-components maven archetype
Posted by Jakob Korherr <ja...@gmail.com>.
Hi,
Yes, the listener is automatically added via a tld file, so no need to
configure it.
I just created the archetype myself and tried it using maven and jetty
(first mvn clean install on the outer project and then mvn clean
jetty:run on the examples project) and everything works great! However
when using tomcat 6.0.29 I get the same error you're getting - thus I
think it is an EL impl problem.
I will investigate further on this one and ping you when I found out
what causes this problem!
Regards,
Jakob
2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
> That's what I looked for, but I went through
> http://localhost:8080/artifact-examples/home.jsf
>
> so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
>
> <listener>
> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener
> </listener-class>
> </listener>
>
> to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
>
> Sincerely,
>
> Matthieu Bertin
> -Office 168
> -Phone 5407
>
>
> -----Message d'origine-----
> De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
> Envoyé : mercredi 1 décembre 2010 16:55
> À : MyFaces Discussion
> Objet : Re: Unable to run the jsf-components maven archetype
>
> Hi Matthieu,
>
> What URL do you use for accessing the website in the browser? For
> example do you use index.jsf or index.jsp?
>
> Only *.jsf works correctly here and I guess that when you use *.jsp
> you will get the error you're seeing.
>
> Regards,
> Jakob
>
> 2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
>> Hello,
>>
>> I've been trying to run the maven JSF Components archetype for JSF 1.2
>> on Tomcat 6.0, created this way:
>>
>> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>>
>> (choice nbr. 6)
>>
>> Unfortunately, I have been unable to find why the EL expressions are not
>> evaluated.
>> For instance, I can read this on the home.jsp:
>>
>>
>> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
>> using #{buildInfo ['jsf_implementation']})
>>
>> Or even
>>
>> #{sayHelloBean.oddNumber} as the default value in a field.
>>
>> The logs in tomcat show no missing jar at deployment, only a
>> facesexceptions when it tries to bind a method to an actionlistener
>> attribute.
>>
>> My guess is there is something missing in the following web.xml:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>> version="2.4">
>>
>> <description>debug web.xml</description>
>>
>> <context-param>
>> <description>Comma separated list of URIs of (additional) faces
>> config files.
>> (e.g. /WEB-INF/my-config.xml)
>> See JSF 1.0 PRD2, 10.3.2
>> Attention: You do not need to put /WEB-INF/faces-config.xml
>> in here.
>> </description>
>> <param-name>javax.faces.CONFIG_FILES</param-name>
>> <param-value>/WEB-INF/examples-config.xml</param-value>
>> </context-param>
>>
>> <context-param>
>> <description>State saving method: "client" or "server" (= default)
>> See JSF Specification 2.5.3</description>
>> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>> <param-value>server</param-value>
>> </context-param>
>>
>> <servlet>
>> <servlet-name>Faces Servlet</servlet-name>
>> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
>> <load-on-startup>1</load-on-startup>
>> </servlet>
>>
>> <servlet-mapping>
>> <servlet-name>Faces Servlet</servlet-name>
>> <url-pattern>*.jsf</url-pattern>
>> </servlet-mapping>
>>
>> <welcome-file-list>
>> <welcome-file>index.jsp</welcome-file>
>> </welcome-file-list>
>>
>> <listener>
>>
>> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
>> /listener-class>
>> </listener>
>>
>>
>> </web-app>
>>
>> Sincerely,
>>
>> Matthieu Bertin
>>
>>
>>
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
RE : RE : Unable to run the jsf-components maven archetype
Posted by BERTIN Matthieu <M....@oberthur.com>.
I think i may stepped on another problem. I thought it might be a problem of language version, so I modified the home.jsp like this:
<h:outputText value=" (Version ${buildInfo['mycomponents_version']}, using #{buildInfo ['jsf_implementation']})"/>
Instead of
<h:outputText value=" (Version #{buildInfo['mycomponents_version']}, using #{buildInfo ['jsf_implementation']})"/>
the change from # to $ provoked an error I could translate into:
According to the TLD, the value attribute accepts no expression.
Sincerely,
Matthieu Bertin
-Office 168
-Phone 5407
-----Message d'origine-----
De : BERTIN Matthieu [mailto:M.BERTIN2@oberthur.com]
Envoyé : mercredi 1 décembre 2010 17:36
À : MyFaces Discussion
Objet : RE : Unable to run the jsf-components maven archetype
That's what I looked for, but I went through
http://localhost:8080/artifact-examples/home.jsf
so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener
</listener-class>
</listener>
to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
Sincerely,
Matthieu Bertin
-Office 168
-Phone 5407
-----Message d'origine-----
De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
Envoyé : mercredi 1 décembre 2010 16:55
À : MyFaces Discussion
Objet : Re: Unable to run the jsf-components maven archetype
Hi Matthieu,
What URL do you use for accessing the website in the browser? For
example do you use index.jsf or index.jsp?
Only *.jsf works correctly here and I guess that when you use *.jsp
you will get the error you're seeing.
Regards,
Jakob
2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
> Hello,
>
> I've been trying to run the maven JSF Components archetype for JSF 1.2
> on Tomcat 6.0, created this way:
>
> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>
> (choice nbr. 6)
>
> Unfortunately, I have been unable to find why the EL expressions are not
> evaluated.
> For instance, I can read this on the home.jsp:
>
>
> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
> using #{buildInfo ['jsf_implementation']})
>
> Or even
>
> #{sayHelloBean.oddNumber} as the default value in a field.
>
> The logs in tomcat show no missing jar at deployment, only a
> facesexceptions when it tries to bind a method to an actionlistener
> attribute.
>
> My guess is there is something missing in the following web.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> version="2.4">
>
> <description>debug web.xml</description>
>
> <context-param>
> <description>Comma separated list of URIs of (additional) faces
> config files.
> (e.g. /WEB-INF/my-config.xml)
> See JSF 1.0 PRD2, 10.3.2
> Attention: You do not need to put /WEB-INF/faces-config.xml
> in here.
> </description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value>/WEB-INF/examples-config.xml</param-value>
> </context-param>
>
> <context-param>
> <description>State saving method: "client" or "server" (= default)
> See JSF Specification 2.5.3</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.jsf</url-pattern>
> </servlet-mapping>
>
> <welcome-file-list>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
>
> <listener>
>
> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
> /listener-class>
> </listener>
>
>
> </web-app>
>
> Sincerely,
>
> Matthieu Bertin
>
>
>
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
RE : Unable to run the jsf-components maven archetype
Posted by BERTIN Matthieu <M....@oberthur.com>.
That's what I looked for, but I went through
http://localhost:8080/artifact-examples/home.jsf
so the error is definitely somewhere else. It still might be my mistake, but I haven't touched anything in the code except adding
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener
</listener-class>
</listener>
to the web.xml. But adding it/removing it don't seem to solve or modify the problem.
Sincerely,
Matthieu Bertin
-Office 168
-Phone 5407
-----Message d'origine-----
De : sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] De la part de Jakob Korherr
Envoyé : mercredi 1 décembre 2010 16:55
À : MyFaces Discussion
Objet : Re: Unable to run the jsf-components maven archetype
Hi Matthieu,
What URL do you use for accessing the website in the browser? For
example do you use index.jsf or index.jsp?
Only *.jsf works correctly here and I guess that when you use *.jsp
you will get the error you're seeing.
Regards,
Jakob
2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
> Hello,
>
> I've been trying to run the maven JSF Components archetype for JSF 1.2
> on Tomcat 6.0, created this way:
>
> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>
> (choice nbr. 6)
>
> Unfortunately, I have been unable to find why the EL expressions are not
> evaluated.
> For instance, I can read this on the home.jsp:
>
>
> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
> using #{buildInfo ['jsf_implementation']})
>
> Or even
>
> #{sayHelloBean.oddNumber} as the default value in a field.
>
> The logs in tomcat show no missing jar at deployment, only a
> facesexceptions when it tries to bind a method to an actionlistener
> attribute.
>
> My guess is there is something missing in the following web.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> version="2.4">
>
> <description>debug web.xml</description>
>
> <context-param>
> <description>Comma separated list of URIs of (additional) faces
> config files.
> (e.g. /WEB-INF/my-config.xml)
> See JSF 1.0 PRD2, 10.3.2
> Attention: You do not need to put /WEB-INF/faces-config.xml
> in here.
> </description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value>/WEB-INF/examples-config.xml</param-value>
> </context-param>
>
> <context-param>
> <description>State saving method: "client" or "server" (= default)
> See JSF Specification 2.5.3</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.jsf</url-pattern>
> </servlet-mapping>
>
> <welcome-file-list>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
>
> <listener>
>
> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
> /listener-class>
> </listener>
>
>
> </web-app>
>
> Sincerely,
>
> Matthieu Bertin
>
>
>
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
Re: Unable to run the jsf-components maven archetype
Posted by Jakob Korherr <ja...@gmail.com>.
Hi Matthieu,
What URL do you use for accessing the website in the browser? For
example do you use index.jsf or index.jsp?
Only *.jsf works correctly here and I guess that when you use *.jsp
you will get the error you're seeing.
Regards,
Jakob
2010/12/1 BERTIN Matthieu <M....@oberthur.com>:
> Hello,
>
> I've been trying to run the maven JSF Components archetype for JSF 1.2
> on Tomcat 6.0, created this way:
>
> mvn archetype:generate -DarchetypeCatalog=http://myfaces.apache.org
>
> (choice nbr. 6)
>
> Unfortunately, I have been unable to find why the EL expressions are not
> evaluated.
> For instance, I can read this on the home.jsp:
>
>
> My JSF Components Library(Version #{buildInfo['mycomponents_version']},
> using #{buildInfo ['jsf_implementation']})
>
> Or even
>
> #{sayHelloBean.oddNumber} as the default value in a field.
>
> The logs in tomcat show no missing jar at deployment, only a
> facesexceptions when it tries to bind a method to an actionlistener
> attribute.
>
> My guess is there is something missing in the following web.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> version="2.4">
>
> <description>debug web.xml</description>
>
> <context-param>
> <description>Comma separated list of URIs of (additional) faces
> config files.
> (e.g. /WEB-INF/my-config.xml)
> See JSF 1.0 PRD2, 10.3.2
> Attention: You do not need to put /WEB-INF/faces-config.xml
> in here.
> </description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value>/WEB-INF/examples-config.xml</param-value>
> </context-param>
>
> <context-param>
> <description>State saving method: "client" or "server" (= default)
> See JSF Specification 2.5.3</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.jsf</url-pattern>
> </servlet-mapping>
>
> <welcome-file-list>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
>
> <listener>
>
> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener<
> /listener-class>
> </listener>
>
>
> </web-app>
>
> Sincerely,
>
> Matthieu Bertin
>
>
>
>
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at