|
All s ervers configured in Studio start in a separate virtual machine(VM) and do not share Studio classpath. The server classpath should be configured as the Studio classpath. The classpath is set separately for each configured server instance. These settings cannot be applied to remote servers. For example, Production WebLogic Server classpath cannot be set in Studio.
The build classpath of a web module is used by Studio Build Tool while compiling JSPs. This classpath is not available to the configured server instances or the Web application, until the application is organized.
This document discusses how to work with database drivers and external JARs, especially in the above scenarios.
To add drivers, select Tools > Configure JDBC Driver from the main menu.
In the Configure Drivers dialog, provide details. Read the sections on datasource for detailed information on database drivers. There is no need to add the driver JARs to the server classpath manually as all the valid resources in the current desk are added to that server at server start. Resources can be added, deleted or modified on the current server only and this information is persisted in the resource.xml file.
External JARs are third party libraries such as log4J, and are used by the application.
As the build classpath of web modules is not included in the server classpath, the external JARs are not available to the WAR and should be added to the WEB-INF/lib folder. Adding a JAR to the WEB-INF/lib folder automatically adds it to the classpath of the classloader used to load the specific WAR.
To add classes to the web module classpath, use the Include Files/Folders option available in the Deploy Tab of the Properties Panel.
| Pramati Technologies © Copyright |
   
|