tell me more icon Default Values for Deployment Profile Name and ADF Library JAR File Name

JDeveloper uses the following format to create a default deployment profile name for you:

adflib identifierN

...where N is a number starting from 1 and incrementing by one every time you create a new deployment profile without removing the existing profile in the project, and identifier is the name generated by JDeveloper using the following in order of precedence:

  • The name of the project (other than the name Model, ViewController, or Project)
  • The name of the application (other than the name Application)
  • A three-digit random number (when both the project and application name are not usable)

Whether you use the default deployment profile name or enter a new name, JDeveloper will use the profile name as the name of the generated ADF Library JAR file. In addition, JDeveloper will place the ADF Library JAR in the default deploy folder under your project folder in the file system. To change the name and location of the default folder for deployed JAR files, from the Tools menu choose Preferences . On the Deployment page, modify the relative or absolute project-level deployment output directory.

In the example you will accept all the default values in the Edit ADF Library JAR Deployment Profile Properties dialog. If you wish to change the location and file name of the ADF Library JAR, on the JAR Options page of the dialog, modify the file name and path of the JAR in the JAR File field.

ADF Library JAR Deployment Profile Properties dialog

The file name of the ADF Library JAR should follow any naming conventions your development team might have, and be descriptive of the content functionality. For instance, if you are creating an ADF Library JAR that contains only declarative components for the HR application, then you might use a name such as mycompany.HRApp.DeclComps.jar.

Copyright © 1997, 2009, Oracle. All rights reserved.

false ,,,,,,,,,,,,,,,