1. Choose Tools > Preferences.
2. Expand the Code Editor node.
3. Select the JSP/XML/HTML node.
4. On the Code Editor - JSP/XML/HTML page, select an option.
5. Click OK.

You can create an XML schema's attributes and set properties and facets from using the XSD Visual Editor. The figure contains an example XML schema in the Design tab of the XSD Visual Editor.

Figure 20-2 Schema in XSD Visual Editor

Description of "Figure 20-2 Schema in XSD Visual Editor"

You can edit attributes in attribute2 in the attribute editor, which is displayed in the figure as the union element. In this editor, you can:

• Display all available attributes under an element. To hide or display details, click the plus and minus signs next to the attribute.

• Display all facets and type details of an attribute display in the attribute node.

• Display the default "Insert Into" menu with the valid schema components (for example, union) when you right-click on an attribute node.

• Expand an attribute node within to display a subtler containing child nodes like list or union.

As you create an XML Schema in the XSD visual editor, JDeveloper automatically updates the XML source in the design tab, as well as updating the contents of the Structure window. The following is the source for the example.xsd file shown in Figure 20-2.

<?xml version="1.0" encoding="windows-1252" ?>
            xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"  xmlns="http://www.example.org"
            targetNamespace="http://www.example.org"    <elementFormDefault="qualified">
    <xsd:complexType name="UnionTest">
      <xsd:sequence>
      <xsd:element name="element1">
    <xsd:complexType>
       <xsd:attribute name="attribute1">
       </xsd:attribute>
    </xsd:complexType>
       </xsd:element>
       <xsd:element name="element2">
    <xsd:complexType>
       <xsd:attribute name="attribute2">
          <xsd:simpleType>
            <xsd:restriction>
              <xsd:simpleType>
                <xsd:union/>
              </xsd:simpleType>
              <xsd:pattern value="abcd"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
    </xsd:complexType>
   </xsd:element>
  </xsd:sequence>
</xsd:complexType>
</xsd:schema>

The selection of any component or attribute in the editor is indicated by highlighting the selected item in blue. In the figure, the selected simpleType component defines a simple type and specifies the constraints and information about the values of attributes or text-only components, in this case restricting the string type.

Figure 20-3 simpleType Component

Description of "Figure 20-3 simpleType Component"

The choice component allows only one of the components contained in the <choice> declaration to be present within the containing component, as shown in the figure. Set attribute maxOccurs to >1 to have more than one item from the choice in the parent.

Figure 20-4 Choice Component

Description of "Figure 20-4 Choice Component "

?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.example.org"
            targetNamespace="http://www.example.org" elementFormDefault="qualified">
  <xsd:element name="choice">
    <xsd:complexType>
      <xsd:choice>
        <xsd:element name="one"/>
        <xsd:element name="two"/>
      </xsd:choice>
    </xsd:complexType>
  </xsd:element>
</xsd:schema>

The all component shown in the figure specifies that the child components can appear in any order and that each child component can occur zero or one times.

Figure 20-5 All Component

Description of "Figure 20-5 All Component"

<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.example.org"
            targetNamespace="http://www.example.org" elementFormDefault="qualified">
  <xsd:element name="all">
    <xsd:complexType>
      <xsd:all>
        <xsd:element name="one"/>
        <xsd:element name="two"/>
      </xsd:all>
    </xsd:complexType>
  </xsd:element>
</xsd:schema>

The sequence component shown in the figure specifies that the child components must appear in a sequence. Each child component can occur from 0 to any number of times.

Figure 20-6 Sequence Component

Description of "Figure 20-6 Sequence Component"

<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.example.org"
            targetNamespace="http://www.example.org" elementFormDefault="qualified">
  <xsd:element name="all">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="one"/>
        <xsd:element name="two"/>
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>
</xsd:schema>

In the example of cardinality shown in the figure, components are displayed with the attributes shown in Table 20-4.

Figure 20-7 Cardinality Component

Description of "Figure 20-7 Cardinality Component"

In the figure, the complexType component extends a base type, and inherits an attribute and children from that base type. The yellow background represents a reference to the baseType defined elsewhere in the schema and illustrated below the complexType component. The component attributes are displayed as:

• Inherited, marked with a square.

• Optional, marked with a square.

• Required, marked with an orange asterisk.

• Prohibited, marked with an orange X.

Figure 20-8 complexType Component

Description of "Figure 20-8 complexType Component"

The attribute group component groups a set of attribute declarations so that they can be incorporated as a group into complex type definition.

The figure displays three attribute groups.

Figure 20-9 Attribute Group Component

Description of "Figure 20-9 Attribute Group Component"

If you add an element to a schema that has multiple attributeGroups, you can add choose one or more attributeGroups for the element by clicking on the element's attribute and choosing from a drop-down list.

The union component defines a simple type as a collection (union) of values from specified simple data types. In the figure, the union represents all strings that begin with the letter "i".

Figure 20-10 Union Component

Description of "Figure 20-10 Union Component"

The list component defines a simple type component as a space separated list of values of a specified data type. In the figure, the component represents a series of short value objects.

Figure 20-11 List Component

Description of "Figure 20-11 List Component"

One element can substitute for another element in an XML Schema group. If you have a set of XML Schemas that use the substitution group feature, ensure that the XML Schema that defines the head of the substitution group is loaded before loading additional schemas that place elements into that substitution group.

For example, you might have an XML Schema named A.xsd that contains

<element name="A"/>

and another XML Schema named B.xsd that contains

<element name="B" substitutionGroup="namespaceForA:A" />

Ensure that one of the following is true:

• You call SchemaGrammarProvider.add(A.xsd) before calling SchemaGrammarProvider.add(B.xsd). Or,

• B.xsd contains an import or include statement with a schemaLocation attribute that contains a valid path to A.xsd.

1. In the Applications window, double click the .xsd file you want to display in the XSD Visual Editor.
2. Click the Design tab in the XSD Visual Editor.

   A design view of the .xsd file displays, similar to Developing Databound XML Pages with XSQL Servlet.

   Figure 20-12 Design Tab in XSD Visual Editor

   
   Description of "Figure 20-12 Design Tab in XSD Visual Editor"
3. Right-click anywhere on the Design tab and choose Publish Diagram.
4. Enter a name, the path where you want to save the diagram, and the image type.

   Note:

   If the diagram you are attempting to save is too large, a message displays to save in .svg format.

   If you right-click on a node in the XSD Visual Editor, only the current node and its child nodes are saved as an image.

1. In the XSD Visual Editor, press and hold down the spacebar.

   The pointer turns into an open hand cursor.

2. Press and hold down the left mouse button.

   The hand closes and grabs the XML Schema page.

3. Use your mouse to move the XML Schema page inside the editor window.
4. Release the XML Schema page by releasing the left mouse button.
5. Close grab scroll by releasing the spacebar.

One of the most common actions you perform in the editor is to select components. you will select components to:

• Edit properties

• Move components

• Delete components

• Choose a target position to insert another component

When you select a component in the XSD Visual Editor, the component displays in blue. When a container component is selected and any of its children, all are blue.

When selected in the Structure window, the component is highlighted. However, when you select any components with children, the children are also selected. If you delete or move the parent, all the children are deleted or moved.

Whenever you select an component, you are also selecting a position in which another component can be inserted. For more information, see How to Select Target Positions for XSD Components.

1. Select the XSD component you want to cut in the visual editor or the Structure window.
2. Do one of the following:

   • Press Ctrl+X.

   • Right-click and select Cut.

   • Choose Edit > Cut from the main menu.

1. Select the XSD component in the visual editor.
2. Do one of the following:

   • Press Ctrl+C.

   • Right-click and select Copy.

   • Choose Edit > Copy from the main menu.

   • Hold down the Ctrl key and drag a copy of the selected component to a target position.

1. Select one or more XSD components to delete in the visual editor.
2. Do one of the following:

   • Press the Delete key.

   • Press Ctrl+X.

   • Right-click and select Delete.

   • Choose Edit > Delete from the main menu.

1. Open the file.
2. Select the insertion point where you want to paste the element.
3. Do one of the following:

   • Press Ctrl+V.

   • Right-click and select Paste.

   • Choose Edit > Paste.

You can work in the visual editor or the Structure window to move components or work in both at once, moving components between the editors.

You can move one or multiple components at a time. However, selecting and moving multiple, non-adjacent components or multiple components from different levels in the schema hierarchy can lead to unexpected results.

1. With an XML Schema open, select a component.

   The Properties window displays the property values. If the Properties window is not in view, choose View > Properties window or use the shortcut Ctrl+Shift+I.

2. Scroll until the property is visible, then select it with the mouse or arrow keys.

   A brief description of the property is displayed at the bottom of the Properties window.

   Tip:

   To quickly locate a property in a long list, click the search button in the Properties window toolbar. In the Find text field, enter the name of the property, then press Enter.

3. In the right column, enter one of the property values shown in Table 20-6.

   Table 20-6 Property Values

   Field	Description
   Text field	Enter the string value for that property, for example a text value or a number value, then press Enter.
   Value field with a down arrow	Click the down arrow and choose a value from the list, then press Enter
   Value field with an ellipsis (...)	Click the ellipsis to display an editor for that property. Set the values in the property editor, then press OK.

   Tips:

   Double-click an XSD component or right-click the component and choose Properties to display a property editor for the component.

   In the property editor select an attribute and view a brief description in the status area below the editor.

   Click Help in the property editor for a link to a component reference topic.

1. Hold down the Ctrl key and select each of the components.
2. Select and edit the desired property in the Properties window.

   If the value is shown in italic font, the selected components have differing values. Editing the value of a shared property will cause all selected components to have the same value.

The main elements in an XLIFF file are the trans-unit elements. These elements store localizable text and its translations. These elements represent segments (usually sentences in the source file that can be translated reasonably independently). The trans-unit elements contain source, target, alt-trans, and a handful of other elements.

There are also elements for review comments, the translation status of individual strings, and metrics such as word counts of the source sentences. The XLIFF file consists of one or more file elements. Each of these contains a header and a body section. The header contains project data, such as contact information, project phases, pointers to reference material, and information on the skeleton file.

JDeveloper uses Resource Bundles to hold all of the localization information, including the XLIFF files. When you create content in a JSF page, a resource bundle is automatically created for you in that project.

Support for XSQL Servlet includes the following:

• XSQL tags on the Components window

• Create XSQL pages automatically

• Includes XSQL libraries

• Provides XSQLConfig.xml on the classpath; you can modify it as needed

• Provides business component action handler tags so XSQL pages can use a business logic tier to access data

XSQL servlets offer a simple and productive way to get XML in and out of the database. Using simple scripts you can:

• Generate simple or complex XML documents

• Apply XSL style sheets to generate any text format

• Parse XML documents and store the data in the database

• Create complete dynamic web applications without programming a single line of code

For example, the emp.xsql file below:

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="emp.xsl"?> 
<FAQ xmlns:xsql="urn:oracle-xsql" connection = "scott">
  <xsql:query doc-element="EMPLOYEES" row-element="EMP"> 
     select e.ename, e.sal, d.dname as department 
     from dept d, emp e 
     where d.deptno = e.deptno
  </xsql:query> 
</FAQ> 

Generates the XML in below:

<EMPLOYEES>
  <EMP>
    <ENAME>Scott</ENAME> 
    <SAL>1000</SAL>
    <DEPARTMENT>Boston</DEPARTMENT>
  </EMP>
  <EMP>
...
  </EMP>
</EMPLOYEES> 

For more information on XSQL Servlet, see your Oracle10i documentation.

Using the wizard to create an XSQL file adds a skeleton file named untitled#.xsql to your project, which opens in the XML Editor. You can type code in this editor, add tags by selecting them from the Components window, and modify the file with your own style sheet information.

To create an XSQL file:

1. In the Applications window, select the project in which you want to create the new XSQL page.

2. Choose File > New > From Gallery.

3. In the Categories tree, expand General and select XML.

4. In the Items list, double-click XSQL File.

1. In the Applications window, double-click right-click an XSQL file.
2. Select the Source tab of the editor.
3. Choose View > Components window to open the Components window and select the XSQL tag page from the dropdown list in the window. You can then select XSQL tags from the window.
4. While you are typing, you can invoke Code Insight by pausing after typing the < (opening bracket) or by pressing Ctrl+Space (if you are using the default keymapping). Code Insight opens a list with valid tags.
5. After selecting a tag, enter a space and then either pause or press Ctrl+Space to open a list of valid attributes from which you can select. After you enter the opening quote for the attribute value, Tip Insight displays the type of value that is required.
6. While you are editing, or after you finish, you can right-click in the file and choose Auto Indent XML to correctly indent the file.
7. You can also right-click in any tag and choose Locate in Structure to highlight that tag in the Structure window.

1. Select a project in the Applications window and choose File > New > Gallery.
2. In the Categories list, select General and select XML.
3. In the Items list, double-click XSQL File.

   This adds a skeleton XSQL file named untitled#.xsql to your project.

4. In the Applications window, double click the new XSQL file to open the editor.
5. Place your cursor in the blank line after the <page xmlns:xsql="urn:oracle-xsql"> tag.
6. Choose View > Components window to open the Components window if it is not displayed.
7. Select XSQL Tags from the dropdown list in the Components window if it is not displayed.
8. Select the Query tag from the Components window.

   The Query tag executes a SQL statement and includes its result set in XML format

9. In the dialog that displays, you can enter values and change default values for the attributes. Press F1 or click Help in the dialog to get help on the tag and its attributes.
10. After entering attributes, click Next.
11. In the Connection Selection dialog, select your connection if it is not selected, then click Next.
12. In the Query dialog, type the SQL statement that you want to execute, then click Next.

    For example, you might type select * from customer to display all the records in the customer database, based on the attributes you entered.

13. Click Finish.

    Notice that the Query tag and attributes you entered appear in the XSQL page.

14. Choose File > Save All to save your work thus far.
15. Right-click the XSQL file in the Applications window, and choose Run <filename>.xsql to view the raw XML data in your web browser.

1. Select a project in the Applications window and choose File > New > From Gallery to open the New Gallery.
2. In the Categories tree, expand General and select Projects.
3. In the Items list, double-click Empty Project to open the New Project dialog.
4. Complete the New Project dialog and click OK to add the empty project to your application.
5. Select the new project in the Applications window and choose File > New.
6. In the Categories list, select General and select XML.
7. In the Items list, double-click XSQL Page.

   This adds a skeleton XSQL file named untitled#.xsql to your project.

8. In the Applications window, right-click the new XSQL file, and choose XML Editor to open the source file if it is not open.
9. Place your cursor in the blank line after the <page xmlns:xsql="urn:oracle-xsql"> tag.
10. Choose View > Components window to open the Components window if it is not displayed.
11. Select XSQL tags from the dropdown list in the Components window if it is not displayed.
12. Select the ViewObject Show tag from the Components window.

    The ViewObject Show tag shows the view object's data in XML format. The ViewObject Update processes inserts, updates, and deletes to a view object based on an optionally transformed XML document.

13. In the View Object Selection dialog, select the appropriate view object, then click Next.
14. Change or accept the default values for the attributes. After entering attributes, click Next.
15. Click Finish.

    Notice that the tag and attributes you entered appear in the XSQL page.

16. Choose File > Save All to save your work.
17. Right-click the XSQL file in the Applications window, and choose Run <filename>.xsql to view the raw XML data in your web browser.

You may get the XSQL error JBO-27122 while querying view objects with circular ViewLink accessors.

Consider a scenario in which there are foreign key relationships between multiple tables. For example, in the HR schema in the Oracle 10i Release 2 database samples, there is such a relationship between countries, departments, employees and locations tables. If you created a simple Business Components project on top of these tables and further created an XSQL client in which you access the view object called CountriesView1, you will get an error such as the one displayed in [the example below.

<?xml version="1.0" encoding="windows-1252" ?> 
- <!-- 
| Uncomment the following processing instruction and replace
| the stylesheet name to transform output of your XSQL Page using XSLT
<?xml-stylesheet type="text/xsl" href="YourStylesheet.xsl" ?>
 
 
--> 
- <page>
- <xsql-error action="xsql:action">
  <message>JBO-27122: SQL error during statement preparation. Statement: SELECT Employees.EMPLOYEE_ID, Employees.FIRST_NAME, Employees.LAST_NAME, Employees.EMAIL, Employees.PHONE_NUMBER, Employees.HIRE_DATE, Employees.JOB_ID, Employees.SALARY, Employees.COMMISSION_PCT, Employees.MANAGER_ID, Employees.DEPARTMENT_ID, Employees.DN FROM EMPLOYEES Employees WHERE (Employees.DEPARTMENT_ID = :1)</message> 
  </xsql-error>
  </page> 

The reason you are getting this error is because of the way the underlying writeXML() method works in combination with the fact that you are using the default values for the max-levels parameter. This causes an infinite loop because of the circular references created by the foreign keys as mentioned above - internally causing an ORA-1000 MaxOpenCursors exceeded error.

The way to work around this is to modify your code as shown below:

<xsql:action handler="oracle.jbo.xsql.ViewObject"
      name="YourViewUsageName"
      appmodule="a.b.c.YourModuleName"
      configname="YourModuleNameLocal">
   <view-attribute-list viewdefname="a.b.c.YourViewName"
         include-only"Attr1 Attr2 Attr3"
       :
</xsql:action>

You can have multiple <view-attribute-list> elements for each view definition that you want to control the attribute list for. As soon as you have one <view-attribute-list> element, then use the new API for writeXML() that will only include the attributes that are listed in the <view-attribute-list> elements.

In order to show the details for a VO, you need to include the name of the view link accessory attribute in the list of attribute names in the "include-only" list for that view definition. The following example contains a working example based on the CountriesView.

<?xml version="1.0" encoding='windows-1252'?>
<!--
| Uncomment the following processing instruction and replace
| the stylesheet name to transform output of your XSQL Page using XSLT
<?xml-stylesheet type="text/xsl" href="YourStylesheet.xsl" ?>
-->
<page xmlns:xsql="urn:oracle-xsql">
    <xsql:action 
    handler="oracle.jbo.xsql.ViewObject" 
    name="CountriesView1"
    configname="HrModuleLocal" 
    appmodule="hr.HrModule">
    <view-attribute-list viewdefname="hr.HrModule.CountriesView"
    include-only="CountryId CountryName CurrencyName" /> 
    </xsql:action>
 
</page>

1. Add the XSQL configuration file to your project.
2. In the XSQL configuration file, register the new action handler by specifying the element name and handler class.
3. In the XSQL file, add the new element and its attributes.
4. In the XSQL file, add connection information to the <page> tag.
5. Add a Java file to the project.
6. In the Java file, create a class that extends the XSQLActionHandlerImpl class.

// Copyright (c) 2000, 2009, Oracle and/or its affiliates. All 
 rights reserved. import oracle.xml.xsql.*; 
import org.w3c.dom.Node; 
import java.util.Date;
/**
 * A Class class. 
 * <P> 
 * @author Pas Apicella 
public class JavaDate extends XSQLActionHandlerImpl 
{
 public void handleAction (Node root) 
   {
    addResultElement(root, "CURRENTDATE", (new Date()).toString()); 
    }
}

1. If necessary, create a new application and project.

   For more information, see Creating Applications and Projects.

2. If the XSQL file is not already open in the source editor, in the Applications window, double-click the name of the XSQL file you just created to open it.
3. Open the New Gallery by choosing File > New.
4. In the New Gallery, in the Categories tree, under General, select XML.
5. In the Items list, double-click XSQL File.
6. In the Components window, drag and drop Query (XSQL) onto the page. This opens a Query wizard, with information about the db connection and enter the SQL query. When you finish the wizard, it adds a <xsql:query> tag to the XSQL file.
7. Click Next. On the second page of the wizard, if you have not already created a database connection, create a new one. Otherwise choose the existing database connection to use.

   The schema and tables you plan to query should be in the database. For more information about setting up a database connection, see Configuring Database Connections. Click Next.

8. Add a SQL query to the file, for example, the query shown below:

   SELECT DISTINCT d.department_id as h_deptno, department_name as "Department_name"
   FROM departments d, employees e
   WHERE d.department_id = e.department_id
   ORDER BY d. department_name
   

9. Click Finish. The query and associated XSQL tags are entered in the XSQL file.
10. Now you can test the XSQL query by running it in Integrated WebLogic Server, which provides everything you need to develop, test and debug web applications from within the IDE. For more information, see Running Java EE Applications in the Integrated Application Server.
11. In the context menu of the XSQL file in the Applications window or in the source editor, click Run. If necessary, the Integrated WebLogic Server will create the default domain and start. The first time you start Integrated WebLogic Server, a dialog is displayed where you have to enter a password for the default user weblogic on the default domain. You only need to do this once.

    When you click OK in the dialog the default domain is created. This may take a few minutes and you can follow the progress in the Log window.

    When the XSQL file runs in Integrated WebLogic Server, the default browser displays the results of the SQL query.

12. Once you have tested the XSQL file successfully in Integrated WebLogic Server, the next step is to deploy and run the application in an application server.
13. The syntax used by JDeveloper and Oracle WebLogic Server to run XSQL is different, so in your XSQL source file you have to change the connection information as follows:

    connection="java:comp/env/jdbc/database-connection-nameDS"
    

    with

    connection="jdbc/database-connection-nameDS"
    

    Note:

    If you want to run the application in the Integrated WebLogic Server, you need to change the connection information back again.

14. In order to deploy the application, you first have to create a deployment profile and deploy the application to it. In the Applications window, right-click the project containing your XSQL servlet, then choose New. In the New Gallery, expand General and select Deployment Profiles.
15. Choose a profile, for example, a WAR deployment profile and click OK and continue to create the deployment profile. For more information, see How to Create and Edit Deployment Profiles.
16. To deploy the application to the deployment profile, right-click on the project containing your XSQL servlet files and choose Deploy > profile where profile is the name of the deployment profile you just created.

    In the Deployment dialog, choose Deploy to WAR (or the appropriate option if you have chosen a different type of deployment profile) and click Finish.

17. The application is now ready to deploy to an application server, for example, Oracle WebLogic Server. The steps you need to perform are:

    • Create a data source on the target application server using the connection information in the XSQL file. For more information, see Setting Up JDBC Data Sources on .

    • Create a connection to the application server. For more information, see How to Create a Connection to the Target Application Server.

    • Deploy the application by right-clicking on the project containing your XSQL servlet files and choosing Deploy > profile where profile is the name of the deployment profile.

      In the Deployment dialog, choose Deploy to application server and on the next page choose the application server connection and click Finish.

    Once the application is deployed, you can view the results of the query in a browser window by navigating to http://targethost:port/web-context-root/filename.xsql.

1. In the Applications window, select the project in which you want to create the new XSL file.
2. Choose File > New > From Gallery.
3. In the Categories tree, expand General and select XML.
4. In the Items list, double-click XSL Style Sheet.
5. In the File Name field, enter the name of the file you want to generate.
6. Leave the Directory Name field unchanged to save your work in the directory where JDeveloper expects to find web application files.

   A skeleton XSL file is generated and appears in your active project.

   You can edit it in the XML Editor to create your own custom style sheet. An example of an XSL style sheet that transforms XML data into wireless markup language (WML) is provided below. When you are finished, you can specify the style sheet name in your XSQL file to format the raw XML data.

   The style sheet in the example below demonstrates the conversion of XML to WML. It uses the default DeptView in a BC4J application.

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<!-- Root template -->
<xsl:output type="wml" media-type="text/x-wap.wml"
doctype-public="-//WAPFORUM//DTD WML 1.1//EN"
doctype-system="http://www.wapforum.org/DTD/wml_1.1.xml"
indent="yes" />

<xsl:template match="* >/"><xsl:apply-templates/></xsl:template>
<xsl:template match="text()>@*"><xsl:value-of select="."/></xsl:template>
<xsl:template match="/">

<wml>
   <card id="C1">
   <p mode="nowrap">
   <big>DEPTLIST</big>
   </p>
   <xsl:for-each select="page/DeptView/DeptViewRow">
   <p>
   <strong><xsl:value-of select="Deptno"/>&nbsp;</strong>
   xsl:value-of select="Dname"/>&nbsp;
   <xsl:value-of select="Loc"/>
   </p>
   </xsl:for-each>
   </card>
</wml>

</xsl:template>
</xsl:stylesheet>

1. In the Applications window, double-click the XSQL file to which you want to add a style sheet.
2. In the source file, locate the xml-stylesheet line and comment, which looks like this:

   <!--
   Uncomment the following processing instruction and replace
   the stylesheet name to transform output of your XSQL Page using XSLT
   <?xml-stylesheet type="text/xsl" href="YourStylesheet.xsl" ?>
   -->
   

3. Uncomment the <?xml-stylesheet?> line by moving it below the --> closing comment bracket.
4. In this line, replace YourStyleSheet.xsl with the name of your style sheet; for example, your style sheet could be named stylesheet1.xsl.

   Next, add the file that you just specified to your project, if you used one created outside of this project.

5. In the Applications window, select the project and choose Project > Add to Project project name.

   In the Add to Project dialog, navigate to the directory and select the style sheet file you specified.

6. Click Open.
7. Choose File > Save All to save all your changes.

   The file you added displays in the Applications window and opens in the XML Editor. You can close the open files.

8. Right-click the XSQL file in the Applications window and choose Run to open the file in your web browser.

   You can see the formatted XML data in the browser.

1. With the project selected in the Applications window, choose Project > Add to Project <project name>.
2. Navigate to the system directory in your JDeveloper installation directory, select XSQLConfig.xml and click Open.
3. Make any changes or additions in the XML Editor.
4. Choose File > Save to save your revised file.