Webcenter Framework :
1. Iterative development lets you see changes to these components almost instantly upon a browser refresh:
page definitions, navigation model, page hierarchy, existing JSPX files, page templates, resource catalog, addition of task flows to pages, addition of portlets to pages
2. When an application is deployed to the Integrated WebLogic Server, the org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION flag is automatically set to true in the web.xml file on the server. This setting causes the server to automatically check the modification time of your JSP and skinning CSS files, and discard saved state when they change. This configuration occurs whether or not the iterative development feature is enabled.
3. When consuming Oracle JSF Portlet Bridge Portlets in your application, ADF attempts to share the skin between the consumer and producer. Therefore, if you are disabling compression on the consumer, you should also do that on the producer. Otherwise, the producer will not generate the correct code to match the uncompressed IDs generated by the consumer.
4.The web.xml file is located in the /public_html/WEB-INF directory relative to the project in your Framework application.
5. The Faces Servlet entry inside <servlet></servlet> tags provides information about the JSF servlet, javax.faces.webapp.FacesServlet. This servlet manages the request processing life cycle for web applications that use JSF to construct the user interface.
6. By default, JDeveloper uses the path prefix /faces/*. That is, when a URL, for example, http://localhost:8080/SRDemo/faces/index.jsp, is issued, the URL activates the JSF servlet, which strips off the faces prefix and loads the file /SRDemo/index.jsp.
7. Use the faces-config.xml file to register a Framework application's resources, such as custom validators and managed beans, and to define all page-to-page navigation rules. The default name of this file is faces-config.xml, though this naming convention is not required.
Depending on how resources are packaged, an application can have one or multiple faces-config.xml files. For example, you can create individual JSF configuration files for:
Different areas of your application
Each library containing custom components or renderers
8. In addition to the skin family, you can define the following application values in the trinidad-config.xml file: Page animation, Level of page accessibility support, Time zone, Enhanced debugging output, Oracle Help for the Web (OHW) URL.
9. If you do not plan to use task flows in your Framework application, you can delete the adfc-config.xml file.
10. Portlets created using the Oracle JSF Portlet Bridge have the requireIFrame container runtime option set to true as these portlets are too complex to render directly on Oracle ADF pages due to JavaScript issues.
11. The Oracle JSF Portlet Bridge is based on and conforms to JSR 329. JSR 329 is the standards effort to define the functionality for the Portlet 2.0 Bridge for JavaServer Faces. Oracle is the specification lead for this standard.
12. The portlet.xml file can include multiple portlets and can have a combination of pages and task flows exposed as portlets.
13. Always create portal pages in JDeveloper as JSP documents (.jspx) rather than JSP pages (.jsp). For page customizations to be stored, the page must be represented in XML. By choosing to create an XML representation of the JSP document (.jspx), you ensure that customizations are always possible for the Framework application page.
14. CSS files used for skins must remain in the Framework application project. Do not attempt to place skin CSS files in the static application resources project.
15. The Search service uses WebCenter Portal search adapters to search each available service. However, large-scale implementations should be configured to use Oracle SES search for best performance.
Oracle SES searches applications for the following resources:
Documents, including wikis and blogs, Announcements and Discussions.
16. In a Framework application, to expose the new catalog in the runtime Resource Manager, you must create the catalog in the APPLICATION_ROOT/Portal/public_html/oracle/webcenter/portalapp directory.
17. If you are using a standalone version of Composer (that is, Composer without WebCenter Portal: Framework), you can add a resource to the catalog by directly adding a <resource> element to the source of the catalog definition file. For information about the Resource Catalog-specific configurations you can make in adf-config.xml.
18. To expose custom resources, such as task flows created in JDeveloper, that are not available in the deployed application, along with exporting the catalog you must also deploy the resource as a shared library.
19. When implementing the filter logic it is common to want information about the current user and current page. This information can be obtained from the FacesContext.
1. Iterative development lets you see changes to these components almost instantly upon a browser refresh:
page definitions, navigation model, page hierarchy, existing JSPX files, page templates, resource catalog, addition of task flows to pages, addition of portlets to pages
2. When an application is deployed to the Integrated WebLogic Server, the org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION flag is automatically set to true in the web.xml file on the server. This setting causes the server to automatically check the modification time of your JSP and skinning CSS files, and discard saved state when they change. This configuration occurs whether or not the iterative development feature is enabled.
3. When consuming Oracle JSF Portlet Bridge Portlets in your application, ADF attempts to share the skin between the consumer and producer. Therefore, if you are disabling compression on the consumer, you should also do that on the producer. Otherwise, the producer will not generate the correct code to match the uncompressed IDs generated by the consumer.
4.The web.xml file is located in the /public_html/WEB-INF directory relative to the project in your Framework application.
5. The Faces Servlet entry inside <servlet></servlet> tags provides information about the JSF servlet, javax.faces.webapp.FacesServlet. This servlet manages the request processing life cycle for web applications that use JSF to construct the user interface.
6. By default, JDeveloper uses the path prefix /faces/*. That is, when a URL, for example, http://localhost:8080/SRDemo/faces/index.jsp, is issued, the URL activates the JSF servlet, which strips off the faces prefix and loads the file /SRDemo/index.jsp.
7. Use the faces-config.xml file to register a Framework application's resources, such as custom validators and managed beans, and to define all page-to-page navigation rules. The default name of this file is faces-config.xml, though this naming convention is not required.
Depending on how resources are packaged, an application can have one or multiple faces-config.xml files. For example, you can create individual JSF configuration files for:
Different areas of your application
Each library containing custom components or renderers
8. In addition to the skin family, you can define the following application values in the trinidad-config.xml file: Page animation, Level of page accessibility support, Time zone, Enhanced debugging output, Oracle Help for the Web (OHW) URL.
9. If you do not plan to use task flows in your Framework application, you can delete the adfc-config.xml file.
10. Portlets created using the Oracle JSF Portlet Bridge have the requireIFrame container runtime option set to true as these portlets are too complex to render directly on Oracle ADF pages due to JavaScript issues.
11. The Oracle JSF Portlet Bridge is based on and conforms to JSR 329. JSR 329 is the standards effort to define the functionality for the Portlet 2.0 Bridge for JavaServer Faces. Oracle is the specification lead for this standard.
12. The portlet.xml file can include multiple portlets and can have a combination of pages and task flows exposed as portlets.
13. Always create portal pages in JDeveloper as JSP documents (.jspx) rather than JSP pages (.jsp). For page customizations to be stored, the page must be represented in XML. By choosing to create an XML representation of the JSP document (.jspx), you ensure that customizations are always possible for the Framework application page.
14. CSS files used for skins must remain in the Framework application project. Do not attempt to place skin CSS files in the static application resources project.
15. The Search service uses WebCenter Portal search adapters to search each available service. However, large-scale implementations should be configured to use Oracle SES search for best performance.
Oracle SES searches applications for the following resources:
Documents, including wikis and blogs, Announcements and Discussions.
16. In a Framework application, to expose the new catalog in the runtime Resource Manager, you must create the catalog in the APPLICATION_ROOT/Portal/public_html/oracle/webcenter/portalapp directory.
17. If you are using a standalone version of Composer (that is, Composer without WebCenter Portal: Framework), you can add a resource to the catalog by directly adding a <resource> element to the source of the catalog definition file. For information about the Resource Catalog-specific configurations you can make in adf-config.xml.
18. To expose custom resources, such as task flows created in JDeveloper, that are not available in the deployed application, along with exporting the catalog you must also deploy the resource as a shared library.
19. When implementing the filter logic it is common to want information about the current user and current page. This information can be obtained from the FacesContext.
Comments
Post a Comment