Why Custom EL Functions are not supported in ADF Faces??

Question

Im using jdev 10.1.3
1.- I declare a java class, with a static function for concatenation purposes.
2.- I create my tld.
3.- I call the function in my jsp.
a) If I use the $ prefix, works PERFECT.
b) If I try to call this in an outputText (i.e)
- If I use the $ prefix, not compile.
- If I use the #, I just tell me that no function is maped to my call.
Is there a REALLY GOOD reason to disable this awesome functionality??
Frank? Steve? somebody? :(

Answer 1

Hi Alopez,
I'll take a stab at this one:
1) In JSF, you need to expose your managed bean by use of the faces-config.xml file, instead of using a TLD (Tag Library Descriptor). Here's an example of an entry in the faces-config.xml...
<manged-bean>
  <managed-bean-name>someBean</managed-bean-name>
  <managed-bean-class>com.company.yourmangedbeanhere</managed-bean-class>
  <managed-bean-scope>request</managed-bean-scope>
</managed-bean>Then your EL would be: #{someBean.yourresult}
2) the ${} is a JSP based expression language call, which is evaluated at page compile time, and is referred to as "Immediate Evaluation". This is good for JSP because your JSP tags are evaluated immediately. In JSF, this expression method is found mainly in the xxPageDef.xml file.
3) the #{} is a JSF based expression language call, which is evaluated at runtime, and is referred to as "Deferred Evaluation". This is necesarry for JSF because of the way the JSF request processing lifecycle works. It allows the expression to show the value and be the target.
If I take a guess, you may be mixing JSP concepts with JSF based development.
Chapter 4 in "The Complete Reference: JavaServer Faces" by Chris Schalk and Ed Burns explains this concept really well.
Hope this helps!
Kenton