----------------------------

Component Controller has this code:

 

public class MedCompController
{       
    List<MedSensitivity> meds;
       
    private String cnId;
    private String medGrp;
               
    public void setCnId(String s)
    {
        cnId = s;
    }  
    public String getCnId()
    {
        return cnId;
    }
       
    public void setMedGrp(String s)
    {
        medGrp = s;
    }
    public String getMedGrp()
    {
        return medGrp;
    }
               
    public List<MedSensitivity> getMeds()
    {  
        if (meds == null )
        {
            meds = new List<MedSensitivity>();
           
            for(med__c medRow : [select trade__c, generic__c, sensitivity__c, sub_group_name__c, sub_group_sensitivity__c
                from med__c
                where
                drug_class__c = :medGrp AND cn_id__c = :cnId])
            {
                MedSensitivity medItem = new MedSensitivity();
                medItem.Setup( medRow);                                
                meds.Add( medItem);
            }      
        }
       
        return meds;
    }  
}

 

---------------------------------------------------------------

The CnID and Med groups are passed into the Component through the Attributes at the top of the component.  We have set the {assignTo} attributes, so they should call the Setter methods on the Controller, and the values should be stored on the Component.

 

The problem is that it appears as though the apex:dataTable is accessing the {meds} attribute on the Controller prior to the setter values from the attributes being set.  

 

How can we pass data into the Component Controller from the calling page, and have it availble for the building of the Data table?   There appears to be no way for this to work.

 

All the examples for the SQL in the Controller show using the Current Page parameters.  However, we will have mutliple instances of the Components on a page, and need to send different values to each one.

 

This appears to be a bug in Visual Force.

 

Thanks,

Steve