----- Original Message -----
Subject: Re: [Resin-interest] Override EL implementation (help us stay with Resin)
Date: Mon, 16 Apr 2012 13:12:15 -0700
From: Scott Ferguson <f...@caucho.com>
> Anyway, when javaee-16.jar/javax/el is replaced with Maven dep
> javax.el/el-api/2.2 the problems were gone, so therefore I assumed the
> repackaging was based on a pre 2.2 version and Resin was not to blame
> for the bugs per se.
> But what you are saying is, that our best bet is to report each
> separate bug against Resin, and hope to see them fixed in the next
> version?

Correct. Fixing those bugs are generally pretty simple, because they're
fairly small in functionality.

Well, I feel like a n00b after having realized the most severe problems we're actually caused by the fact that a team member (who is running JBoss locally) had set com.sun.faces.expressionFactory parameter to com.sun.el.ExpressionFactoryImpl. So there was a mixture of two implementations. Sorry for blaming Resin! *blush*

After changing the setting to com.caucho.el.ExpressionFactoryImpl (or rather a proxy using com.caucho.el.ExpressionFactoryImpl if present), the problems turning are much less severe.

I reported http://bugs.caucho.com/view.php?id=5034 (which has a very easy workaround) and http://bugs.caucho.com/view.php?id=5035 (which should be no problem in production, but make development much less effective; trivial to fix so I trust it to be in the next release)

I do want to ask, why Resin is using a custom EL implementation rather than the Sun implementation? Performance? Licensing? In case there is good reason to stick with custom implementation, and the above two bugs are fixed, I guess http://bugs.caucho.com/view.php?id=5011 can be closed.



resin-interest mailing list

Reply via email to