Stephane, Thanks for all your help.
This meaningful error means that you have a jar that has the Class-Path > entry in it but the jar pointed by the classpath does not exists so this > wonderful and expensive application server crashes beautifully. > Yes. This is > unbelievable. I could not believe it myself... When you are doing > deployment > for the first time and encounters the dotted-jar and the manifest > class-path > problems, you ask yourself what will be next... > > Workaround: hack your jars to remove the class-path entry in its manifest. Will attempt this. > I would advise you to post these issues in the Weblogic newsgroups though > since there is not much to do with turbine though.... Well, I am only trying to deploy a stanard tdk build, so it does have something to do with turbine. At the very least I could write a how-to to help others trying to do this deployment. I will attempt to find the broken manifest and report back to this list if it is a jakarta related jar. Gareth -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
