Hi,
Can you elaborate further on this statement?
we deployed plugin dependency bundle of respective jars which export these packages.
Do you provide those jars as part of your plugin? How exactly do you do that?
Since you have problems with log4j, how do you satisfy this dependency? Do you ship some jar with your plugin? Do you use the one from the virgo repositories?
I am wondering why the similar code base of manifest and jars works fine till VCSA6.0 if the cause is version .
We have change the plugin deployment mechanism in 6.0 U1. This might have introduced a regression...
That means in virgo server there are two implementation for export package org.apache.log4j
In fact there are three of them. And that is fine since they are exported with different versions. This is one of the nice things about virgo.
The problem however occurs when you doesn't specify a version in your Import-Package. Then you cannot be sure which version will be used to satisfy your imports. And this is exactly why I suspect is happening...
Another thing that can be messed up is if you deploy another version of log4j with the same version as part of your plugin.
Please help me root-cause this issue. If there is a regression in this core functionality, it might affect other plugins too...