Tag Archives: MDS

persdef error


When you ever get this error

Then go to adf-config.xml and then remove the mdsC:adf-mds-config entry completely.

The content of the tag goes like this


<mdsC:adf-mds-config version="11.1.1.000">

<mds-config xmlns="http://xmlns.oracle.com/mds/config">

<persistence-config>

<metadata-namespaces>

persdef/"

metadata-store-usage="WebCenterFileMetadataStore"/>

</metadata-namespaces>

<metadata-store-usages>

<metadata-store-usage id="WebCenterFileMetadataStore"

default-cust-store="true" deploy-target="true">

<metadata-store class-name="oracle.mds.dt.persistence.stores.file.SrcControlFileMetadataStore">

<property name="metadata-path" value="../../mds"/>

</metadata-store>

</metadata-store-usage>

</metadata-store-usages>

</persistence-config>

<cust-config>

<match>

<customization-class name="oracle.adf.share.config.SiteCC"/>

</match>

</cust-config>

<cache-config>

<max-size-kb>100000</max-size-kb>

</cache-config>

</mds-config>

<!--<span class="hiddenSpellError" pre=""-->mdsC:adf-mds-config>

Iterative Development – Webcenter


Ho to enable Iterative Development in Web-center?

Iterative Development helps the developer to see the changes by just a refresh of the page in the integrated Server.

This makes the portal application development easy and rapid development.

Disadvantages of enabling this is that the application will run slowly as all the performance optimization settings will all be disabled. The ‘Delete Customization Before every run‘ is to be checked if we plan to enable the iterative Development option.

oracle.mds.exception.MDSRuntimeException: MDS-00168


Target URL -- http://127.0.0.1:7101/[Application_Name]-[Project_Name]-context-root/faces/[page_name].jspx
<22-03-2010 09:57:51 AM CLT>    <[ServletContext@27112686[app:[Application_Name] module:[Application_Name]-[Project_Name]-context-root path:/[Application_Name]-[Project_Name]-context-root spec-version:2.5]] Servlet failed with Exception
oracle.mds.exception.MDSRuntimeException: MDS-00168: MDS object oracle.mds.core.MDSInstance@160bf69 is being used after it or its MDSInstance or PManager has been released.
at oracle.mds.core.MDSInstance.checkNotReleased(MDSInstance.java:1078)
at oracle.mds.core.MDSInstance.getPersistenceManager(MDSInstance.java:638)
at oracle.mds.core.MDSSession.getPersistenceManager(MDSSession.java:1992)
at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:2769)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1188)
Truncated. see log file for complete stacktrace

The above mentioned error is due to a known issue for JDeveloper and ADF 11g.

This is related to the initialization of the ADFShare components in a web environment. the oracle.adf.share.http.ServletADFContext must be initialized per request. Normally, this is achieved because the jdev design time adds the ADFBindingFilter to the project web.xml when certain actions are taken

The ServletADFFilter must be used for correct use of ADFContext. ServletADFFilter specifically setup ServletADFContext properly at the start of the request.

<filter>
 <filter-name>ServletADFContextFilter</filter-name>
 <filter-class>oracle.adf.share.http.ServletADFFilter</filter-class>
 </filter>
 <filter-mapping>
 <filter-name>ServletADFContextFilter</filter-name>
 <url-pattern>/*</url-pattern>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 </filter-mapping>