| Dynamic Web Project setup with new Deployment Assembly page [message #543209] |
Mon, 28 June 2010 13:11  |
 Matthew Hall
Messages: 4
Registered: June 2010 |
Junior Member |
|
|
So, like many, I seem to be having a bit of a problem working with the new Deployment Assembly page that has been added to the Dynamic Web Project Properties. Hopefully, you might be able to get me straightened out!
I have approximately 30 source folders that are in sub-directories all over the project that are added to the build path (such as "modules/core/src"). Most of these folders contain a java package hierarchy with source files, but a few simply contain a large number of configuration files (such as "modules/config/src"). Build and runtime libraries are scattered in a few different "lib" directories across the project as well.
Previously, in Galileo, setting up a new Dynamic Web Project was easy. Once all of the source folders and libraries were added to the build path, I simply had to go to the "Java EE Module Dependencies" preferences page and click "Select All". Publishing the project to a local Tomcat server after this worked like a charm.
In Helios, however, I seem to be having some issues getting Tomcat to see some of the configuration files once the project is published. In particular, I have a file called "default.loaders" that exists in the "modules/config/src" folder that one of my bootstrap servlets is having a hard time finding. The "modules/config/src" folder is a Java source folder and has been added to the "Deployment Assembly" page with its "Deploy Path" set to "/WEB-INF/classes". The "default.loaders" file exists in both the "modules/config/src" and "bin" folders, and yet my bootstrap servlet is still getting a FileNotFoundException when it attempts to open it.
Any ideas on what sort of configuration changes I might need to perform to make the files in my "modules/config/src" source folder visible to the webapp?
|
|
|
] 
Search
Help
Register
Login
Home
