Hi Vyas ,
I am not sure if RIDC facade class is the right way to go because of the following input from Development team :
The RIDC based connection ( oracle.stellent.ridc.convenience.adf.connection.RidcConnection) looks to be associated with the deprecated RIDC connection management code that was created earlier ,http://docs.oracle.com/cd/E23943_01/doc.1111/e10807/c23_ridc.htm#sthref1487
This older technology did not follow the proper ADF connection code patterns and did not support MDS for customizations after deployment.
The customer should try and avoid using this older RIDC connection management framework code.
Thanks for the info. Asking purely from a coder's perspective -
If this is a recommendation from the Oracle RIDC Development team, how could the documentation has presented an example of JSP page verifying the RIDC Connection.
Also, While going through the pointer shared by the Dev team, I stumbled across another doubt - what is the difference between the Content Srever connection adn RIDC connection?
Irrespective of the usecase, does the recommendation mean that one should go with a db based or flat-file based cs connection info and not to follow the AdfConnectionFacade class? Please confirm.
Hi Vyas ,
Yes, that was the same question which I had put forward as well . Following is the reasoning for the current documentation examples and other samples related to ADF Facade class :
For lack of any current suitable replacement in the 11g JDeveloper stack from WebCenter Content, the jdeveloper design-time pieces, connection code, and associated documentation remain.
SSXA (Site Studio) had leveraged this connection mechanism. The code itself works, it just has many limitations.
The future (12c) release of RIDC will have no design-time jdeveloper integration - and the connection framework code in question is not packaged or built.
Hope this helps .