Posted on

getting current row of table in ADF

Requirment- Get the current row of table in ADF

         DCBindingContainer bindings = (DCBindingContainer)getBindings();                
        DCIteratorBinding dcIter = bindings.findIteratorBinding("IOOrderLinesVO4Iterator");
         RowSetIterator lineRSIter = dcIter.getRowSetIterator();
        Row r = lineRSIter.getCurrentRow();
Posted on

Java program to SORT MAP based on KEYS

Requirment- To sort MAP based on key using Java

following is the source code-

package techartifact; 

import java.util.*; 

class SortMaps 
{ 

public static void main(String args[]) 
{ 
Map m=new LinkedHashMap(); 

m.put(1,10); 
m.put(3,11); 
m.put(5,15); 
m.put(2,13); 
m.put(4,14); 

Collection c=m.keySet(); 
System.out.println(c); 


Object a[]; 
a = c.toArray(); 

Arrays.sort(a); 

for(int i=0;i<a.length;i++) 
{ 
System.out.println((Object)a[i]); 
} 



} 
}
Posted on

Access one Managed Bean from another in JSF 2.0 | Techartifact

Requirement- Access one Managed Bean from another in JSF

Solution- There are two ways-

Dependency Injection

We can use JSF 2 @ManagedProperty annotation

In the managed bean add a @ManagedProperty annotation to the related property 

@ManagedBean(name="currentBean")
@RequestScoped
public class CurrentBean 
{

    @ManagedProperty(value="#{requiredBean}")
    private RequiredBean requiredBean;

    public RequiredBean getRequiredBean()
    {
        return requiredBean;
    }

    public void setRequiredBean(RequiredBean requiredBean)
    {
        this.requiredBean= requiredBean;
    }

    // ....


}

Usingthrough faces-config.xml

<managed-bean>
   <managed-bean-name>requiredbBean</managed-bean-name>
   <managed-bean-class>vinay.common.RequiredBean</managed-bean-class>
   <managed-bean-scope>session</managed-bean-scope>
 </managed-bean>

 <managed-bean>
   <managed-bean-name>currentBean</managed-bean-name>
   <managed-bean-class>vinay.common.CurrentBean</managed-bean-class>
   <managed-bean-scope>request</managed-bean-scope>
   <managed-property>
     <property-name>requiredbBean</property-name>
     <value>#{requiredbBean}</value>
   </managed-property>
 </managed-bean>

Following are the constraints:

-> The current bean must have scope which is the same as or shorter than the required bean
-> The using bean must have a property-setter method which takes the required bean as a parameter
-> The beans cannot have managed dependencies on each other.