Peter,
Thanks, but that patch didn't solve the problem. Even mentioning
framework in the
Extension list throws an error. The error changed to:

2002-11-07 20:48:01 StandardHost[localhost]: ContainerBase.addChild: start:
LifecycleException: Missing optional package Extension[avalon-framework]
at
org.apache.catalina.loader.WebappLoader.validatePackages(WebappLoader.java:1244)
at org.apache.catalina.loader.WebappLoader.start(WebappLoader.java:645)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1100)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3371)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
...

I made the change and committed it. Seems like it should have worked as
you changed
it though.

Cheers,
Leif

Peter Donald wrote:

>On Thu, 7 Nov 2002 15:29, Leif Mortenson wrote:
>  
>
>>I just updated my application to the latest versions of jars from CVS.
>>Due to a change in
>>the component package, the container jar is now required. That is fine
>>but when I deployed
>>my app and tried to start Tomcat, I get the following exception:
>>
>>LifecycleException: Missing optional package Extension[avalon-framework,
>>implementationVersion=4.1.2, specificationVersion=1.0]
>>    
>>
>
>The specificationVersion is not specified in the avalon-framework.jar which is 
>your problem. Catalina tries to match it and fails. The implementation 
>version is also screwy as it requires the exact version 4.1.2 when it should 
>require interface version 4.1.2 or above. I removed these from container 
>package and should be able to work now.
>
>  
>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


Reply via email to