# Substituting Extended View Objects

Substituting extended View Objects allows the code in your application to work with the results returned by the queries over the new attributes and business logic added to the extended Entity Objects.

If you substitute an extended View Object you must also ensure that you substitute the extended Entity Object that it references. If the extended View Object is the source or destination end of an extended View Link you will also have to substitute the extended View Link.

## Using JDeveloper to Substitute Extended View Objects

Use the Substitutions panel of the Business Components Project wizard to substitute an extended View Object throughout your application. For the procedure to substitute a View Object, see To Substitute Business Components. The framework makes an addition to the to the `Substitutes` section of the project's `.jpx` file which identifies the name of the original View Object and the name of the extended View that should be used instead.

For example, if you use the Substitutions panel of the Business Components Project wizard to substitute the extended View Object `NewEmpViewEx` for the original View Object `EmpView` throughout your application, the framework adds a line to the `Substitutes` section of the project's XML file. A portion of the project's XML file is included below:

      <Substitutes>
      <Substitute OldName ="package27.DeptView" NewName ="Extender.NewDeptViewEx" />
      <Substitute OldName ="package27.EmpView" NewName ="Extender.NewEmpViewEx" />
      <Substitute OldName ="package27.Emp" NewName ="Extender.NewEmpEx" />
      <Substitute OldName ="package27.EmpForeignKeyAssoc" NewName ="Extender.NewFKAssocEx" />
      <Substitute OldName ="package27.Dept" NewName ="Extender.NewDeptEx" />
      </Substitutes>

Note that is is assumed that you have already substituted the extended Entity Objects `NewEmpEx` and `NewDeptEx` for the original Entities `Emp` and `Dept`, and the extended association `NewFKAssocEx`.