ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I have a fairly dynamic UI where the views and subviews load their information from programatically changing backing beans. For example, I am trying to use the schedule like so:

Code:

 <ice-cc:schedule bean="#{scheduleLocation.viewBean.controller}" id="scheduleController"/>

Unfortunately, the current implementation REQUIRES that you define it EXACTLY like so:

Code:

 <ice-cc:schedule bean="#{calendarController}" id="scheduleController"/>

Because if you do not, you get this error:

SEVERE: javax.faces.event.AbortProcessingException: /file:/apache-tomcat-6.0.26/webapps/Pipeline3/WEB-INF/lib/icefaces-composite-comps.jar!/META-INF/facelet/schedule/navigation.xhtml @72,62 valueChangeListener="#{calendarController.viewableHoursValueChangeListener}": Target Unreachable, identifier 'calendarController' resolved to null
javax.faces.event.AbortProcessingException: /file:/apache-tomcat-6.0.26/webapps/Pipeline3/WEB-INF/lib/icefaces-composite-comps.jar!/META-INF/facelet/schedule/navigation.xhtml @72,62 valueChangeListener="#{calendarController.viewableHoursValueChangeListener}": Target Unreachable, identifier 'calendarController' resolved to null
at javax.faces.event.MethodExpressionValueChangeListener.processValueChange(MethodExpressionValueChangeListener.java:82)

Because the internal workings of the calendar requires the bean to be named exactly as defined. Is there a way to allow me to NOT have to have the controller tied so statically to that name?

I do this everywhere else for other icefaces components.. like tables, etc.