Many applications rely on third-party utility JARs for functionality. You may want to add more dependant JARs during your development process, and after you have assembled your development mode ear. In order for third-party JARs to be available to Nucleus components, they must be EAR-scoped, and should reside in the lib directory of your Enterprise Application. Your EJB project must also be aware of them.

Note: If you add dependent JARs to the ATG-Class-Path manifest attribute of your ATG module before generating the development EAR file, and the assembler distorts the names, causing errors in the WSAD task list.

To add dependant JARs to your ATG application:

loading table of contents...