Oracle WebCenter 11g 快速开发指南--翻译（三）

1.6.2 如何访问链接向导?

从New Gallery访问connection wizard:

1. File --->New.

2. 在New Gallery 对话框中, 展开Connections, 选择你想创建的connection类型, 点击OK.

   依赖你选择的类型, 创建该<Connection_Type> Connection 的对话框会打开.

3. 在该选项中创建链接，Application Resources 被设置成默认方式。

   你可以通过 Resource Palette-->IDE Connections 选择创建链接.

从 Application Navigator访问connection wizard :

1. 在 Application Resources 下右键点击 Connections 节点，选择 New Connection, 然后从内容目录中选择 connection type .

2. 依赖你选择的类型, 创建该<Connection_Type> Connection 的对话框会打开.

   在该选项中创建链接，Application Resources 被设置成默认方式。

 从Resource Palette访问链接connection wizard

1. 点击 Resource Palette中New 图标, 选择New Connection, 然后从内容目录中选择 connection type .

2. 依赖你选择的类型, 创建该<Connection_Type> Connection 的对话框会打开.

   在该选项中创建链接，IDE Connections 被设置成默认方式。

1.6.3 在什么地方能够学习到Connection的更多内容?

For information about creating and consuming connections, see:

 

     第26章节  "Configuring Content Repository Connections"
   

     第59章 "Consuming Portlets"

     Part IV "Integrating and Publishing Content"
    

     第64章  "Deploying and Testing Your WebCenter Portal Application"

 

 

1.7 规划Portal 布局

You can use page templates to control the layout of your portal. A page template is a JSPX file that specifies the look and feel of your portal's pages. The template defines header, footer, content, and navigation regions within the page. You can apply the template to any number of pages, resulting in a consistent look and feel.

WebCenter provides several default page templates to help you get started. For more information, see Chapter 8, "Understanding Pages, Page Templates, and the Portal Page Hierarchy."

 

 

1.8 皮肤加工

A skin is a CSS file that defines the overall look of a portal, including color schemes, fonts, and the display characteristics of ADF Faces components. WebCenter also provides a portal skin file that you can conveniently edit in JDeveloper. This file lets you override settings in the default skin. Just open the file, uncomment any components you wish to modify, and save the file when you are finished making changes. For details, see Chapter 14, "Creating and Managing Skins."

 

1.9 双向开发准备

Round-trip development refers to features and techniques that allow you to retrieve（重复得到） resources from a deployed, runtime portal back to JDeveloper for maintenance（维护） or enhancement（增强）. After modifying a resource in JDeveloper, you can use the Resource Manager to upload the resource back to the deployed portal. WebCenter's round-trip development features provide a simple, convenient（方便） way to modify portal resources without redeploying the entire application.

For more information on round-trip development, see Section 16.3, "Enabling Runtime Administration of Your Portal" and Section 16.4, "Enabling Round-Trip Development of Resources."

 

 

1.10 我们应该知道配置文件的那些内容?

A number of automatically generated configuration files are placed under the WEB-INF and Page Flows folders of a portal project when you create a WebCenter Portal application.

Tip:

For a complete listing of portal configuration files, see Appendix H, "Manually Migrating a WebCenter Portal Application."

This section briefly describes these file:

• Section 1.10.1, "The WebCenter Portal Application Template Default web.xml File"

• Section 1.10.2, "The WebCenter Portal Application Template Default faces-config.xml File"

• Section 1.10.3, "The WebCenter Application Template Default trinidad-config.xml File"

• Section 1.10.4, "The WebCenter Application Template Default adfc-config.xml File"

 

1.10.1 WebCenter Portal 应用模板默认配置文件web.xml

Part of WebCenter Portal application configuration is determined by the content of its J2EE application deployment descriptor file: web.xml. The web.xml file defines many application settings that are required by the application server.

Note:

Rather than being specified in web.xml, the context root path is assigned when the application is deployed.

Typical runtime settings include initialization parameters, custom tag library location, and security settings. Depending on the technology you use, other settings may be added to web.xml as appropriate.

Note:

For standard Java EE files like web.xml, there is usually a counterpart Oracle-specific file with additional Oracle-specific options, for example, weblogic.xml.

The web.xml file is located in the /public_html/WEB-INF directory relative to the project in your WebCenter Portal application.

When you first create your WebCenter application, configuration settings for JSF servlet and mapping and for resource servlet and mapping are automatically added to the starter web.xml file.

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. The configuration setting maps the JSF servlet to a symbolic name, Faces Servlet.

The resources entry inside <servlet></servlet> tags provides information about the ADF resource servlet used to serve up web application resources (images, style sheets, JavaScript libraries) by delegating to a ResourceLoader.

The <servlet-mapping></servlet-mapping> tags map the URL pattern to a servlet's symbolic name. You can use either a path prefix or an extension suffix pattern.

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.

Note:

If you prefer to use the extension jsf for web pages instead of jsp or jspx, then you must set the javax.faces.DEFAULT_SUFFIX context parameter to jsf, for example:

<context-param>
  <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
  <param-value>.jsf</param-value>
</context-param>

Then add a servlet mapping in web.xml that invokes the JSP servlet for files with the extension jsf.

To edit web.xml in Oracle JDeveloper, right-click web.xml in the Application Navigator and choose Open from the context menu. This opens web.xml in the Web Application Deployment Descriptor editor, in Overview mode. If you are familiar with configuration element names, then you can also use the XML editor to modify web.xml.

For information about the configuration elements you can use in the web.xml file, see "Oracle ADF XML Files" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

 

 

1.10.2 The WebCenter Portal 应用模板默认配置文件 faces-config.xml

Use the faces-config.xml file to register a WebCenter Portal 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（提供者）

For more information about creating multiple faces-config.xml files, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

Example 1-1 illustrates the default faces-config.xml file provided through the WebCenter Portal Application template. This file is located in the /public_html/WEB-INF directory relative to the project in your WebCenter Portal application.

Example 1-1 Default faces-config.xml File Provided Through the WebCenter Portal Application Template

<?xml version="1.0" encoding="US-ASCII"?>
<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
  <application>
    <default-render-kit-id>oracle.adf.rich</default-render-kit-id>
    <view-handler>oracle.webcenter.portalframework.sitestructure.handler.CustomViewHandler
    </view-handler>
  </application>
  <managed-bean>
    <managed-bean-name>preferenceBean</managed-bean-name>
    <managed-bean-class>oracle.webcenter.portalframework.sitestructure.PreferencesBean
    </managed-bean-class>
    <managed-bean-scope>application</managed-bean-scope>
  </managed-bean>
</faces-config>

To edit the faces-config.xml file, double-click it in the Application Navigator. By default, the file is opened in the Editor window in Diagram mode, as indicated by the active Diagram tab at the bottom of the Editor window. When creating or modifying JSF navigation rules, Diagram mode enables you to visually create and manage page flows. For more information, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

To create or modify configuration elements other than navigation rules, use the Editor's Overview mode. Enter this mode by clicking the Overview tab at the bottom of the Editor window.

JSF allows multiple <application> elements in a single faces-config.xml file. When you use the JSF Configuration Editor, you can edit only the first instance. For any other <application> elements, you must edit the file directly using the XML editor. To use the XML editor, open the faces-config.xml file and go to the Source tab in the Editor window.

For reference information about the configuration elements you can use in the faces-config.xml file, see "ADF Faces Configuration" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

 

 

1.10.3 WebCenter 应用模板默认配置文件trinidad-config.xml

The default trinidad-config.xml file, available when you create an application, contains information about the application skin family. Additionally, it can contain information about the level of page accessibility support, page animation（动画）, time zone, enhanced debugging output, and the URL for Oracle Help for the Web (OHW). Like faces-config.xml, the trinidad-config.xml file has a simple XML structure that enables you to define element properties using JSF Expression Language (EL) or static values.

Example 1-2 illustrates（图例说明） the default trinidad-config.xml file provided through the WebCenter Portal Application template. This file is located in the /public_html/WEB-INF directory relative to the project in your WebCenter Portal application.

Example 1-2 Default trinidad-config.xml File Provided Through the WebCenter Application Template

<?xml version="1.0" encoding="US-ASCII"?>
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config">
 
  <skin-family>fusion</skin-family>
 
</trinidad-config>

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

For reference information about the trinidad-config.xml file, see "ADF Faces Configuration" in the Oracle Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework.

 

1.10.4 WebCenter 应用模板默认配置文件adfc-config.xml

The adfc-config.xml file is the configuration file for an ADF unbounded（不受控制的、无限的） task flow. This file contains metadata about the activities and control flows contained in the unbounded task flow. The default name for this file is adfc-config.xml, though this naming convention is not required.

If ADF Page Flow is specified as a Selected Technology on the Technology Scope page of the Project Properties dialog, a new adfc-config.xml source file is automatically created within the project. The adfc-config.xml file is the main source file for an unbounded task flow.

The adfc-config.xml file is located in the /public_html/WEB-INF directory relative to the project in your WebCenter Portal application.

Note:

If you do not plan to use task flows in your application, you can delete the adfc-config.xml file.

For more information about task flows and the adfc-config.xml file, see "Oracle ADF XML Files" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

 

1.11 Installing Database Schemas（方案、提纲、图解）

Certain Oracle WebCenter components require schemas that must be installed in a supported database. For details, see Section 3.4, "Installing Database Schemas."