Re: [VOTE] release of MyFaces Core 2.2.0
+1 Am 09.01.2014 18:46, schrieb Grant Smith: +1 On Thu, Jan 9, 2014 at 9:07 AM, Paul Nicolucci mailto:pnico...@us.ibm.com>> wrote: +1 Regards, Paul Nicolucci Inactive hide details for Leonardo Uribe ---01/07/2014 11:00:23 PM---Hi, I was running the needed tasks to get the 2.2.0 releasLeonardo Uribe ---01/07/2014 11:00:23 PM---Hi, I was running the needed tasks to get the 2.2.0 release of Apache From: Leonardo Uribe mailto:lu4...@gmail.com>> To: MyFaces Development mailto:dev@myfaces.apache.org>>, Date: 01/07/2014 11:00 PM Subject: [VOTE] release of MyFaces Core 2.2.0 Hi, I was running the needed tasks to get the 2.2.0 release of Apache MyFaces core out. The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.2.1 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.2.0 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.2.0" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-018/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces220binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316396 -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC.
Re: [jira] [Commented] (MYFACES-3104) MyFaces 2 with EL 2.2 in Websphere 7
Some time ago, I had to work with Websphere 6.1 and Myfaces JSF/Trinidad
(1.2).
Assuming what you have is an EAR/WAR app. What I used to do was "Add"
the following parameter through Websphere Administration Console, in
WebContainer/Custom Properties:
/com.ibm.ws.webcontainer.invokefilterscompatibility//= true/
Also at the moment of installing the application, you must instruct WAS
to choose the applications libraries first (not parent).
And that will do the trick.
I hope this apply also for WAS 7.0, and help you.
Regards,
Eduardo
El 09/01/14 03:02, Jesús Pérez Alcaide (ISBAN) (JIRA) escribió:
> [
> https://issues.apache.org/jira/browse/MYFACES-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866450#comment-13866450
> ]
>
> Jesús Pérez Alcaide (ISBAN) commented on MYFACES-3104:
> --
>
> I have experienced this issue (using MyFaces 2 with EL 2.2 in WebSphere 7)
> and I have solved this way:
>
> Create a shared library with the jars from MyFaces 2 and those from EL 2.2
> implementation (JUEL in my case). Check the option to create a isolation
> class loader. This option will create an isolated class loader for these
> library, allowing us to use a different JSF implementation that what is
> shipped with WebSphere.
>
> Assign this shared library to the web module of your application.
>
> In your web.xml, specify the EL ExpressionFactory to use:
>
>
> org.apache.myfaces.EXPRESSION_FACTORY
> de.odysseus.el.ExpressionFactoryImpl
>
>
> You may also need to disable support for old JSP EL:
>
>
>
> org.apache.myfaces.SUPPORT_JSP_AND_FACES_EL
> false
>
>
> This worked for me, I hope it may help someone else.
>
>
>
>> MyFaces 2 with EL 2.2 in Websphere 7
>>
>>
>> Key: MYFACES-3104
>> URL: https://issues.apache.org/jira/browse/MYFACES-3104
>> Project: MyFaces Core
>> Issue Type: Bug
>> Components: General
>>Affects Versions: 2.0.4
>> Environment: WebSphere Platform 7.0.0.13
>> Host Operating System is Windows XP, version 5.1 build 2600 Service Pack 3
>> Java version = 1.6.0, Java Compiler = j9jit24, Java VM name = IBM J9 VM
>> Servlet API : 2.5
>> JSP API : 2.1
>>Reporter: mansour
>> Attachments: MyFacesEL2Sample_was7.zip
>>
>>
>> We have followed your documentation on the wiki in order to enable EL 2.2
>> (http://wiki.apache.org/myfaces/HowToEnableEl22), it doesn't work on
>> Websphere 7.
>> - we have added the 2 jars (el-api-2.2.jar and el-impl-2.2.jar from
>> Glassfish implementation) in th classpath of the web application
>> - we have configured the web.xml like this :
>>
>> org.apache.myfaces.EXPRESSION_FACTORY
>> com.sun.el.ExpressionFactoryImpl
>>
>> [...]
>>
>>
>> org.apache.myfaces.webapp.StartupServletContextListener
>>
>> The web application starts without errors,
>> Problem :
>> 1) When the web application starts we have this first exception :
>> [04/04/11 11:24:39:136 CEST] 000a DefaultFacesC I Reading standard
>> config META-INF/standard-faces-config.xml
>> [04/04/11 11:24:39:277 CEST] 000a DefaultFacesC I Reading config
>> /WEB-INF/faces-config.xml
>> [04/04/11 11:24:39:823 CEST] 000a ExternalSpeci I MyFaces Bean
>> Validation support disabled
>> [04/04/11 11:24:39:855 CEST] 000a ApplicationIm I Couldn't discover
>> the current project stage, using Production
>> [04/04/11 11:24:39:855 CEST] 000a FacesConfigur I Serialization
>> provider : class
>> org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory
>> [04/04/11 11:24:39:855 CEST] 000a DefaultLifecy I Using
>> LifecycleProvider
>> org.apache.myfaces.config.annotation.AllAnnotationLifecycleProvider
>> [04/04/11 11:24:39:933 CEST] 000a FfdcProvider W
>> com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: Incident FFDC émis
>> sur
>> C:\IBM\SDP75\runtimes\base_v7\profiles\was70profile2\logs\ffdc\server1_48704870_11.04.04_11.24.39.8706071861720806063404.txt
>> com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated 1341
>> [04/04/11 11:24:39:933 CEST] 000a webappE
>> com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E:
>> Exception interceptée lors de l''initialisation du contexte : {0}
>> java.lang.VerifyError:
>> javax/servlet/jsp/JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V
>> at
>> org.apache.myfaces.webapp.Jsp21FacesInitializer.configureResolverForJSP(Jsp21FacesInitializer.java:123)
>> at
>> org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:77)
>> at
>> org.apache.myfaces.webapp.AbstractFacesIni
Re: [VOTE] release of MyFaces Core 2.0.20
+1 On Thu, Jan 9, 2014 at 9:07 AM, Paul Nicolucci wrote: > +1 > > Regards, > > Paul Nicolucci > > > [image: Inactive hide details for Leonardo Uribe ---01/07/2014 10:58:13 > PM---Hi, I was running the needed tasks to get the 2.0.20 relea]Leonardo > Uribe ---01/07/2014 10:58:13 PM---Hi, I was running the needed tasks to get > the 2.0.20 release of Apache > > From: Leonardo Uribe > To: MyFaces Development , > Date: 01/07/2014 10:58 PM > Subject: [VOTE] release of MyFaces Core 2.0.20 > -- > > > > Hi, > > I was running the needed tasks to get the 2.0.20 release of Apache > MyFaces core out. > > The artifacts passed all TCK tests. > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.0.20 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.0.20 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with > myfaces-api. > > Please take a look at the "2.0.20" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-016/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces2020binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325349 > > > -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC. <>
Re: [VOTE] release of MyFaces Core 2.1.14
+1 On Thu, Jan 9, 2014 at 9:07 AM, Paul Nicolucci wrote: > +1 > > Regards, > > Paul Nicolucci > > [image: Inactive hide details for Leonardo Uribe ---01/07/2014 10:58:46 > PM---Hi, I was running the needed tasks to get the 2.1.14 relea]Leonardo > Uribe ---01/07/2014 10:58:46 PM---Hi, I was running the needed tasks to get > the 2.1.14 release of Apache > > From: Leonardo Uribe > To: MyFaces Development , > Date: 01/07/2014 10:58 PM > Subject: [VOTE] release of MyFaces Core 2.1.14 > -- > > > > Hi, > > I was running the needed tasks to get the 2.1.14 release of Apache > MyFaces core out. > > The artifacts passed all TCK tests. > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.1.12 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.1.14 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with > myfaces-api. > > Please take a look at the "2.1.14" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-017/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces2114binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325347 > > > -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC. <>
Re: [VOTE] release of MyFaces Core 2.2.0
+1 On Thu, Jan 9, 2014 at 9:07 AM, Paul Nicolucci wrote: > +1 > > Regards, > > Paul Nicolucci > > > [image: Inactive hide details for Leonardo Uribe ---01/07/2014 11:00:23 > PM---Hi, I was running the needed tasks to get the 2.2.0 releas]Leonardo > Uribe ---01/07/2014 11:00:23 PM---Hi, I was running the needed tasks to get > the 2.2.0 release of Apache > > From: Leonardo Uribe > To: MyFaces Development , > Date: 01/07/2014 11:00 PM > Subject: [VOTE] release of MyFaces Core 2.2.0 > -- > > > > Hi, > > I was running the needed tasks to get the 2.2.0 release of Apache > MyFaces core out. > > The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.2.1 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.2.0 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with > myfaces-api. > > Please take a look at the "2.2.0" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-018/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces220binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316396 > > > -- Grant Smith - V.P. Information Technology Marathon Computer Systems, LLC. <>
Re: [VOTE] release of MyFaces Core 2.1.14
+1 Regards, Paul Nicolucci From: Leonardo Uribe To: MyFaces Development , Date: 01/07/2014 10:58 PM Subject:[VOTE] release of MyFaces Core 2.1.14 Hi, I was running the needed tasks to get the 2.1.14 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.1.12 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.1.14 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.1.14" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-017/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces2114binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325347 <>
Re: [VOTE] release of MyFaces Core 2.0.20
+1 Regards, Paul Nicolucci From: Leonardo Uribe To: MyFaces Development , Date: 01/07/2014 10:58 PM Subject:[VOTE] release of MyFaces Core 2.0.20 Hi, I was running the needed tasks to get the 2.0.20 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.0.20 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.0.20 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.0.20" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-016/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces2020binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325349 <>
Re: [VOTE] release of MyFaces Core 2.2.0
+1 Regards, Paul Nicolucci From: Leonardo Uribe To: MyFaces Development , Date: 01/07/2014 11:00 PM Subject:[VOTE] release of MyFaces Core 2.2.0 Hi, I was running the needed tasks to get the 2.2.0 release of Apache MyFaces core out. The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.2.1 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.2.0 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.2.0" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-018/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces220binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316396 <>
[jira] [Updated] (TRINIDAD-2443) Reduce severity of component binding reuse message
[ https://issues.apache.org/jira/browse/TRINIDAD-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Schwartz updated TRINIDAD-2443: Status: Patch Available (was: Open) > Reduce severity of component binding reuse message > -- > > Key: TRINIDAD-2443 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2443 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Reporter: Andy Schwartz >Assignee: Andy Schwartz >Priority: Minor > Attachments: TRINIDAD-2443.patch > > > As part of our changes for: > TRINIDAD-2409 improve diagnostics during tag execution component binding > failures > We added some logging to UIXComponentELTag.createComponent() when we detect a > newly created component with a "stale" parent. > The idea behind this logging is that it should help catch cases where the > component tree is being pinned in memory, typically by using a component > binding that references a long-lived (eg. session scope. > However, it turns out that we're detecting (and logging the severe message > for) other cases. For example: > - A page fragment defines a component with a binding that points to a request > scoped bean. > - The page fragment is jsp:included into both page1.jspx and page2.jspx. > - The user navigates from page1.jspx to page2.jspx (with no redirect). > At this point we see the severe message, even though there is no risk of > component tree pinning. > Unfortunately, we don't just see the message once, but repeatedly on every > navigation. And since the message is being logged as severe, it will likely > show up in (and bloat) logs for production deployments. > I think that this message is still useful, but more for debugging purposes > than for production error reporting. As such, opening this issue to request > that we crank the severity down. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (TRINIDAD-2443) Reduce severity of component binding reuse message
Andy Schwartz created TRINIDAD-2443: --- Summary: Reduce severity of component binding reuse message Key: TRINIDAD-2443 URL: https://issues.apache.org/jira/browse/TRINIDAD-2443 Project: MyFaces Trinidad Issue Type: Bug Components: Components Reporter: Andy Schwartz Assignee: Andy Schwartz Priority: Minor As part of our changes for: TRINIDAD-2409 improve diagnostics during tag execution component binding failures We added some logging to UIXComponentELTag.createComponent() when we detect a newly created component with a "stale" parent. The idea behind this logging is that it should help catch cases where the component tree is being pinned in memory, typically by using a component binding that references a long-lived (eg. session scope. However, it turns out that we're detecting (and logging the severe message for) other cases. For example: - A page fragment defines a component with a binding that points to a request scoped bean. - The page fragment is jsp:included into both page1.jspx and page2.jspx. - The user navigates from page1.jspx to page2.jspx (with no redirect). At this point we see the severe message, even though there is no risk of component tree pinning. Unfortunately, we don't just see the message once, but repeatedly on every navigation. And since the message is being logged as severe, it will likely show up in (and bloat) logs for production deployments. I think that this message is still useful, but more for debugging purposes than for production error reporting. As such, opening this issue to request that we crank the severity down. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [VOTE] release of MyFaces Core 2.2.0
+1 2014/1/8 Leonardo Uribe > Hi, > > I was running the needed tasks to get the 2.2.0 release of Apache > MyFaces core out. > > The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.2.1 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.2.0 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with > myfaces-api. > > Please take a look at the "2.2.0" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-018/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces220binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316396 >
[jira] [Commented] (MYFACES-3104) MyFaces 2 with EL 2.2 in Websphere 7
[
https://issues.apache.org/jira/browse/MYFACES-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866450#comment-13866450
]
Jesús Pérez Alcaide (ISBAN) commented on MYFACES-3104:
--
I have experienced this issue (using MyFaces 2 with EL 2.2 in WebSphere 7) and
I have solved this way:
Create a shared library with the jars from MyFaces 2 and those from EL 2.2
implementation (JUEL in my case). Check the option to create a isolation class
loader. This option will create an isolated class loader for these library,
allowing us to use a different JSF implementation that what is shipped with
WebSphere.
Assign this shared library to the web module of your application.
In your web.xml, specify the EL ExpressionFactory to use:
org.apache.myfaces.EXPRESSION_FACTORY
de.odysseus.el.ExpressionFactoryImpl
You may also need to disable support for old JSP EL:
org.apache.myfaces.SUPPORT_JSP_AND_FACES_EL
false
This worked for me, I hope it may help someone else.
> MyFaces 2 with EL 2.2 in Websphere 7
>
>
> Key: MYFACES-3104
> URL: https://issues.apache.org/jira/browse/MYFACES-3104
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.4
> Environment: WebSphere Platform 7.0.0.13
> Host Operating System is Windows XP, version 5.1 build 2600 Service Pack 3
> Java version = 1.6.0, Java Compiler = j9jit24, Java VM name = IBM J9 VM
> Servlet API : 2.5
> JSP API : 2.1
>Reporter: mansour
> Attachments: MyFacesEL2Sample_was7.zip
>
>
> We have followed your documentation on the wiki in order to enable EL 2.2
> (http://wiki.apache.org/myfaces/HowToEnableEl22), it doesn't work on
> Websphere 7.
> - we have added the 2 jars (el-api-2.2.jar and el-impl-2.2.jar from Glassfish
> implementation) in th classpath of the web application
> - we have configured the web.xml like this :
>
> org.apache.myfaces.EXPRESSION_FACTORY
> com.sun.el.ExpressionFactoryImpl
>
> [...]
>
>
> org.apache.myfaces.webapp.StartupServletContextListener
>
> The web application starts without errors,
> Problem :
> 1) When the web application starts we have this first exception :
> [04/04/11 11:24:39:136 CEST] 000a DefaultFacesC I Reading standard
> config META-INF/standard-faces-config.xml
> [04/04/11 11:24:39:277 CEST] 000a DefaultFacesC I Reading config
> /WEB-INF/faces-config.xml
> [04/04/11 11:24:39:823 CEST] 000a ExternalSpeci I MyFaces Bean
> Validation support disabled
> [04/04/11 11:24:39:855 CEST] 000a ApplicationIm I Couldn't discover the
> current project stage, using Production
> [04/04/11 11:24:39:855 CEST] 000a FacesConfigur I Serialization
> provider : class
> org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory
> [04/04/11 11:24:39:855 CEST] 000a DefaultLifecy I Using
> LifecycleProvider
> org.apache.myfaces.config.annotation.AllAnnotationLifecycleProvider
> [04/04/11 11:24:39:933 CEST] 000a FfdcProvider W
> com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: Incident FFDC émis
> sur
> C:\IBM\SDP75\runtimes\base_v7\profiles\was70profile2\logs\ffdc\server1_48704870_11.04.04_11.24.39.8706071861720806063404.txt
> com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated 1341
> [04/04/11 11:24:39:933 CEST] 000a webappE
> com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E:
> Exception interceptée lors de l''initialisation du contexte : {0}
> java.lang.VerifyError:
> javax/servlet/jsp/JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V
> at
> org.apache.myfaces.webapp.Jsp21FacesInitializer.configureResolverForJSP(Jsp21FacesInitializer.java:123)
> at
> org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:77)
> at
> org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:126)
> at
> org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:111)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1681)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:374)
> at
> com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:299)
> at
> com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)
> at
> com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)
> at
> com.ibm.ws.webcontainer.WSWebContainer.addWe
