Actually, the unified EL is available as a part of Tomcat 6. I think you can acquire it independently of Tomcat. You can also grab it as part of a facelets distribution.
Also, you could either switch to JSF 1.2 or switch to using Facelets since Facelets automatically uses the new unified EL, or change your expression language. I think changing the EL is a matter of specifying variable-resolver and property-resolver in your faces-config file, but I've never done it. I've seen postings of others who have done so, including a javascript el replacement. On 1/22/07, Bruno Aranda <[EMAIL PROTECTED]> wrote:
JSP 2.1 includes now the Unified EL (javax.el.*) in the spec, which is what jsf 1.2 uses. MyFaces 1.2 is not going to depend in apache commons el anymore, Cheers, Bruno On 22/01/07, Savitsky, Alex <[EMAIL PROTECTED]> wrote: > Sun JSF RI uses its own EL implementation from Glassfish... but MyFaces > has explicit code dependencies on Commons EL, so switching is not > trivial... > > Alex > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 21, 2007 9:13 PM > To: MyFaces Discussion > Subject: Re: Memory leak > > Good question... Anyone know a Commons EL substitution? Hopefully > something that is still in active development. > > Wayne > > On 1/19/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > What can you use instead of commons EL? > > > > > > On 1/19/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > Sounds like a bug for Apache Commons EL project... but it seems > > > pretty dead. 12 bugs posted since 2003 and only 2 fixed. > > > > > > Realistically, it seems like you'll need to patch the EL code to > > > eliminate this bug, as discussed in that Sun.com bug report. > > > > > > Wayne > > > > > > On 1/19/07, phtan <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > We have a memory leak problem when running MyFaces 1.1.3 on > > > > Websphere > > 6.1. We > > > > used a tool provided by IBM call Memory Dump Diagnostic to compare > > > > > 2 > > heap dumps > > > > or when we get a core dump due to out of memory. The leak > > > > candidate > > shown by > > > > the tool is almost always the BeanInfoManager in apache commons > EL. > > > > > > > > We googled and found similar reported cases albeit with different > > > > app > > server, > > > > see > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6390584 > > . > > > > > > > > Have anyone else faced the same issue and any resolution? Any > > > > help much appreciated as our system will go production soon. :-(. > > > > > > > > Thanks! > > > > > > > > Regards, > > > > ph tan > > > > > > > > > > > > > > > > > > > -- > > Thanks > > > > DJ MICK > > > > (Mick Knutson) > > http://www.djmick.com > > http://www.myspace.com/djmick_dot_com > > http://www.thumpradio.com > > > ******************** > NOTICE OF CONFIDENTIALITY > This communication including any information transmitted with it is > intended only for the use of the addressees and is confidential. > If you are not an intended recipient or responsible for delivering > the message to an intended recipient, any review, disclosure, > conversion to hard copy, dissemination, reproduction or other use > of any part of this communication is strictly prohibited, as is the > taking or omitting of any action in reliance upon this communication. > If you receive this communication in error or without authorization > please notify us immediately by return e-mail or otherwise and > permanently delete the entire communication from any computer, > disk drive, or other storage medium. > > If the above disclaimer is not properly readable, it can be found at > www.td.com/legal > > AVERTISSEMENT DE CONFIDENTIALITE > Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement > aux destinataires susmentionnés, est confidentiel. Si vous > n'êtes pas le destinataire prévu ou un agent responsable de la > livraison de ce courriel, tout examen, divulgation, copie, impression, > reproduction, distribution, ou autre utilisation d'une partie de ce > courriel est strictement interdit de même que toute intervention ou > abstraction à cet égard. Si vous avez reçu ce message par erreur ou > sans autorisation, veuillez en aviser immédiatement l'expéditeur par > retour de courriel ou par un autre moyen et supprimer immédiatement > cette communication entière de tout système électronique. > > Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous > pouvez le consulter à www.td.com/francais/legale >
