Servlet class loaders do not look for META-INF/Manifest.mf inside the WAR.
I believe you could place it WEB-INF/classes/META-INF/Manifest.mf.
From what you describe, I'm not sure that the manifest file is showing
up in the right place. I would not rely on the manifest approach for a web application, but instead rely on how T5 loads the "application module", as demonstrated in the quickstart Maven archetype. On 4/11/07, Leon Pennings <[EMAIL PROTECTED]> wrote:
Ok, I'm doing something wrong here. I'm working on a T5 project where I have a T5 module. I made a manifest file which is in the META-INF folder that is in the classpath (m2 resource folder, that is added as a source folder under eclipse). I'm running jettylauncher to test the project, but the module isn't loaded by Tapestry. What am I doing wrong? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
