Re: Does MyFaces 1.2 require JSP 2.1?

[Jeroen Benckhuijsen]

Pior,

Both facelets and Tomcat itself come with an implementation of EL.
Remove the el-api and el-impl jars from your web-app.

Regards,

Jeroen

On Tue, 2007-09-18 at 01:02 -0700, Piotr wrote:
> I've upgraded MyFaces to 1.2 version, facelets to 1.1.12 ver and try to run
> my app on the Tomcat 6.0.14.
> During startup I receive following error msg:
> SEVERE: Exception sending context initialized event to listener instance of
> class org.apache.myfaces.webapp.StartupServletContextListener
> java.lang.LinkageError: loader constraint violation: when resolving
> interface method
> "javax.servlet.jsp.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V"
> the class loader (instance of org/apache/catalina/loader/WebappClassLoader)
> of the current class, org/apache/myfaces/webapp/DefaultFacesInitializer, and
> the class loader (instance of
> org/apache/catalina/loader/StandardClassLoader) for resolved class,
> javax/servlet/jsp/JspApplicationContext, have different Class objects for
> the type javax/el/ELResolver used in the signature
> 
> Any idea?
> 
> P.
> 
> 
> 
> Francisco Passos wrote:
> > 
> > Will the Myfaces team consider the possibility of providing similar
> > support
> > for non-JSP 2.1 containers using facelets?
> > 
> > That would be very welcome :)
> > 
> > On 7/19/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> >>
> >> nice!
> >>
> >> that's a cool feature.
> >>
> >> -M
> >>
> >> On 7/19/07, Jesse Alexander (KSFD 121)
> >> <[EMAIL PROTECTED]> wrote:
> >> > No..
> >> > RI just makes a test on the JSP-version and disables certain stuff,
> >> when
> >> > it detects
> >> > a J2EE 1.4 environment (as in TC 5 and WLS 9.2). It then relies on
> >> > facelets
> >> > to provide certain functionality...
> >> >
> >> > Sounds like MyFaces is a bit harsher on the user here than the RI.
> >> >
> >> > OK... JSF 1.2 officially needs JEE 5.
> >> > BUT... 1:0 for RI to allow for the gracefull degradation.
> >> >
> >> > Just set up a 1.2 RI-app in TC 5.x and watch the log when starting up.
> >> > You will notice some entries like
> >> > INFO: JSF1027: [null] The ELResolvers for JSF were not registered with
> >> > the JSP container.
> >> >
> >> > See what I mean?
> >> >
> >> > regards
> >> > Alexander
> >> >
> >> >
> >> > -----Original Message-----
> >> > From: Andrew Robinson [mailto:[EMAIL PROTECTED]
> >> > Sent: Thursday, July 19, 2007 7:24 PM
> >> > To: MyFaces Discussion
> >> > Subject: Re: Does MyFaces 1.2 require JSP 2.1?
> >> >
> >> > I would ask the facelets list then. According to the JSF
> >> > specification, JSP 2.1 and Servlet 2.5 support is required for JSF
> >> > 1.2.
> >> >
> >> > On 7/19/07, mraible <[EMAIL PROTECTED]> wrote:
> >> > >
> >> > > I am using Facelets - that's why I find it strange. I'm able to use
> >> > Sun's RI
> >> > > (the latest version) in place of MyFaces in the same application and
> >> > > everything works fine.
> >> > >
> >> > > Matt
> >> > >
> >> > >
> >> > > Andrew Robinson-5 wrote:
> >> > > >
> >> > > > JSF 1.2 requires JSP 2.1 unless you use facelets.
> >> > > >
> >> > > > I believe you have to run Tomcat 6 as a minimum version (servlet
> >> 2.5
> >> > > > support is required)
> >> > > >
> >> > > > On 7/19/07, mraible <[EMAIL PROTECTED]> wrote:
> >> > > >>
> >> > > >> I should mention: I get the error below on startup when deploying
> >> > on
> >> > > >> Tomcat
> >> > > >> 5.0.25. If I change from MyFaces to Sun's RI and deploy on Tomcat
> >> > 5.0.25
> >> > > >> again, no error.
> >> > > >>
> >> > > >> Matt
> >> > > >>
> >> > > >>
> >> > > >> mraible wrote:
> >> > > >> >
> >> > > >> > From what I can tell, MyFaces 1.2 requires JSP 2.1. I developed
> >> a
> >> > quick
> >> > > >> > prototype using MyFaces 1.2 + Facelets 1.1.13 and I get the
> >> > following
> >> > > >> > error on startup:
> >> > > >> >
> >> > > >> > Exception sending context initialized event to listener instance
> >> > of
> >> > > >> class
> >> > > >> > org.apache.myfaces.webapp.StartupServletContextListener
> >> > > >> > java.lang.NoSuchMethodError:
> >> > > >> >
> >> > > >>
> >> >
> >> javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/Ser
> >> > vletContext;)Ljavax/servlet/jsp/JspApplicationContext;
> >> > > >> >         at
> >> > > >> >
> >> > > >>
> >> >
> >> org.apache.myfaces.webapp.DefaultFacesInitializer.initFaces(DefaultFaces
> >> > Initializer.java:102)
> >> > > >> >         at
> >> > > >> >
> >> > > >>
> >> >
> >> org.apache.myfaces.webapp.StartupServletContextListener.contextInitializ
> >> > ed(StartupServletContextListener.java:57)
> >> > > >> >
> >> > > >> > If I deploy my app to Tomcat 6, this problem doesn't exist. If I
> >> > change
> >> > > >> > from MyFaces 1.2 to Sun's RI 1.2_04, this problem doesn't exist
> >> > either.
> >> > > >> > For this reason, it appears to me that MyFaces 1.2 requires JSP
> >> > 2.1.
> >> > > >> >
> >> > > >> > Cheers,
> >> > > >> >
> >> > > >> > Matt
> >> > > >> >
> >> > > >>
> >> > > >> --
> >> > > >> View this message in context:
> >> > > >>
> >> >
> >> http://www.nabble.com/Does-MyFaces-1.2-require-JSP-2.1--tf4112432.html#a
> >> > 11693503
> >> > > >> Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >> > > >>
> >> > > >>
> >> > > >
> >> > > >
> >> > >
> >> > > --
> >> > > View this message in context:
> >> >
> >> http://www.nabble.com/Does-MyFaces-1.2-require-JSP-2.1--tf4112432.html#a
> >> > 11693795
> >> > > Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >> > >
> >> > >
> >> >
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> further stuff:
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> mail: matzew-at-apache-dot-org
> >>
> > 
> > 
> 

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762