Question on ComponentRef

[Dominico Francisco <do...@yahoo.com>]

I am in the process of migrating an ADF application to Trinidad.�The application uses ADF Regions quite a lot because�this has been a good way of re-using components across several�pages.� 
�
I saw the document on migrating ADF regions to Trinidad: http://wiki.apache.org/myfaces/from_ADF_to_Trinidad#region�and I followed the� steps� 
but this�was problematic�because of the use of jsp-include.�The jsp-includes were preventing the dataTables from paginating, for some reason.�also there's a lot more work involved because you need to create managed bean for each region.
�
The working solution that I found is the�use of Trinidad's componentRef and the region-metadata.xml, as suggested in this forum:
http://forums.oracle.com/forums/thread.jspa?messageID=2153863
�
I found this componentRef�approach�to be a�lot cleaner for re-using components and migrating ADF regions.� But I read somewhere in the thread above that this might be desupported or dropped in the future.� What's the verdict on this and what's the rational?� I need to find out if i can rely on this approach for re-using components going forward.� It works like a charm so far, but need to find out if there are any known issues with this approach.
�
thanks.


      

[Trinidad] Question on ComponentRef

[Dominico Francisco <do...@yahoo.com>]

Labeling as Trinidad question

--- On Tue, 7/1/08, Dominico Francisco <do...@yahoo.com> wrote:

From: Dominico Francisco <do...@yahoo.com>
Subject: Question on ComponentRef
To: users@myfaces.apache.org
Date: Tuesday, July 1, 2008, 5:27 PM










I am in the process of migrating an ADF application to Trinidad.�The application uses ADF Regions quite a lot because�this has been a good way of re-using components across several�pages.� 
�
I saw the document on migrating ADF regions to Trinidad: http://wiki.apache.org/myfaces/from_ADF_to_Trinidad#region�and I followed the� steps� 
but this�was problematic�because of the use of jsp-include.�The jsp-includes were preventing the dataTables from paginating, for some reason.�also there's a lot more work involved because you need to create managed bean for each region.
�
The working solution that I found is the�use of Trinidad's componentRef and the region-metadata.xml, as suggested in this forum:
http://forums.oracle.com/forums/thread.jspa?messageID=2153863
�
I found this componentRef�approach�to be a�lot cleaner for re-using components and migrating ADF regions.� But I read somewhere in the thread above that this might be desupported or dropped in the future.� What's the verdict on this and what's the rational?� I need to find out if i can rely on this approach for re-using components going forward.� It works like a charm so far, but need to find out if there are any known issues with this approach.
�
thanks.