ADF Basics: Using f:attribute to pass parameter in ActionEvent

f:attribute tag (JSF Tag supported in ADF Faces) is used to pass some additional attribute value to associated component
Sometimes using f:attribute simplify a complex piece of code, this tag has very simple structure. It has two properties

name- Name of tag attribute
value- Value or an EL reference of value

Here in this post we will see how to use this tag with ADF Faces, I am using Departments table of HR Schema and requirement is to delete departments with attribute DepartmentId  greater than 100

Dynamic (parameterize) model level validation using message token -Oracle ADF

Hello all
This post falls under ADF Basics category (about a little trick in model layer) but about a common development requirement
How can we create dynamic ADF BC validation ? means it takes a parameter at run time and append it to validation message

Read previous post on model level validation-
Conditional Execution of Model (EO) level Validation- Oracle ADF
ViewObject Validation rules for transient attributes (Model level validation in ADF)

In this post I am using Departments table of oracle HR Schema

• First step is same , prepare model (EO,VO and AM) using Departments table






• Creating a business rule that DepartmentName can not be duplicate, for this created a alternate key in EntityObject 






• Nnow creating unique key business rule for this alternate key and message that appears on validation failure (this is how we apply EO level validations)









• Run AM and check in BC4J tester, create a new row and on entering duplicate DepartmentName this validation message appears -"Duplicate Department Name"





• now my requirement is this message should be like - Duplicate Department Name <Administration> , so for this i have to pass parameter in message that shows entered DepartmentName on run-time. ADF provides built in feature to pass tokens in message and on run time it is replace with groovy expression value



 On running see desired output






• to pass more than one parameter just add another token and set groovy for it, see the screens

 Output-

Thanks - Happy Learning :)

Passing parameter in XML Resource and Use it in Managed Bean, Using parameterised Resource Bundle in ADF

If we are developing an Fusion Web application and we are thinking about Multilingual application , then the best option i came to know is to use Resource Bundle properties of ADF . When we use resource bundle we have to use labels of Fields and Validation message or any kind of other custom message from a XML file as Resource.xml.
So first you should know that how to configure resource bundle in an ADF Application and there are plenty of posts about configuring Properties or List ResourceBundle.

In this post i will show you that how to pass parameter in XML or how to use Parametrized resource .

Suppose i  have a xml file for ResourceBundle reference Resource.xml--

1. <?xml version="1.0" encoding="windows-1252" ?>
2. <bundle>
3. <label>
4.     <key>MessageCheck</key>
5.     <value>Only %s %s %s %s %s allowed</value>
6.  </label>
7. </bundle>

and now i use it in managed bean to show a custom message and replace its parameters %s with any desired value then we code like this

1. //To get String from XML key, resolvElDC is a method to resolve expression language
2. String message = resolvElDC("#{bundle['MessageCheck']}").toString();
3. //here replace parameter(%s) in string message with your values
4. String saveMsg = message.format(message, ",", "/", "@", "_", "%");
5. //Show FacesMessage
6. FacesMessage msg = new FacesMessage(saveMsg);
7. msg.setSeverity(FacesMessage.SEVERITY_INFO);
8. FacesContext ctx = FacesContext.getCurrentInstance();
9. ctx.addMessage(null, msg);
12. // Code for resolvElDC method
14. public Object resolvElDC(String data) {
15.     FacesContext fc = FacesContext.getCurrentInstance();
16.     Application app = fc.getApplication();
17.     ExpressionFactory elFactory = app.getExpressionFactory();
18.     ELContext elContext = fc.getELContext();
19.     ValueExpression valueExp = elFactory.createValueExpression(elContext, data, Object.class);
20.     return valueExp.getValue(elContext);
21. }

Now run your code and see the updated message- Only %s %s %s %s%s allowed is now